In Windows users and groups share the same ID (SID) space which means any SID can be assigned as a file's owner or group because a SID doesn't have any user/group association.
This is not the case in Solaris.
Currently CIFS service doesn't check this so a file might endup with a gid in its uid slot. This could be considered a security issue. A proper solution will involve the idmap service. For the time being an option would be to reject such requests that try to set a group as owner or a user as the primary group.