Samba gives Couldn't set gid -24 error

[Ian Lochray]

I use Samba to map HP-UX file systems onto PCs running various flavours of Windows O/S. One PC has recently been upgraded from Windows 95 to Windows 2000. Now, when the PC's user tries to map a HP file system which was previously OK, she gets an invalid username/password error in Windows and the samba log shows the errors:-
Couldn't set gid -24 currently set to (0,0)
Can't become connected user!
What is going on?

[John Poff]

Hello,

Sounds like a mismatch on the user name. Did their account name change when they upgraded?

I've seen similar complaints when the 'nobody' account is set to have a GID of -2. Which version of Samba are you running?

JP

[ricky_1]

try changing smb.conf file entry from "user" to "share" and then check if it works?
if it works then something wrongwith user id
mind U not a sleek answer!!,

best of luck

[Ian Lochray]

There is something wrong with the way the userid is getting passed in. The username has not been changed since the upgrade but the name of the PC has. The reason for the -24 message is that samba is trying to user nobodu/nogroup and the GID of nogroup is -24. I can get round this by using a different UNIX id for the guest user but I want to know why the correct user is not being passed in.

[Russell Campbell]

I have just solved this problem See Attachment.