Hello, I just upgraded to samba 2.0.4b from 1.9.18 on OSF/1 V 4.0 Everything used to work fine in 1.9, and everything works fine now, except that one of our users can't connect to anything from Windows NT. I've also tried to use smbclient from her Unix account, and get the error:>smbclient \\\\clang\\public >Added interface ip=128.104.25.251 bcast=128.104.25.255 nmask=255.255.255.128 >Password: >session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pairin a Tree Connect or Session Setup are invalid.) Every other user can get to the share public this way from UNIX. This user belongs to the same group (and has the same privileges) as many other users who can access samba. Is there anything any of you can think of that would cause a specific user to not have access? (Her yp password entry is not different than any of the others) (her password works on logging into UNIX and logging into our NT servers). I think I've seen mention of a similar problem upon this upgrade, but no solution. Any help would be appreciated. Oguz Yetkin
On 20 Jun 99, Oguz Yetkin <oyetkin@students.wisc.edu> had questions about password problems on upgrade to 2.0.4:> Is there anything any of you can think of that would cause a > specific user to not have access?Is her account disabled in the smbpasswd file? ************************************************************* Steve Arnold sarnold@earthling.net http://www.rain.org/~sarnold This message composed of 100% recycled electrons. You should also recycle yourself. Become an organ donor 8-)
> I just upgraded to samba 2.0.4b from 1.9.18 on OSF/1 V 4.0> Everything used to work fine in 1.9, and everything works fine now, except > that one of our users can't connect to anything from Windows NT. I've also > tried to use smbclient from her Unix account, and get the error: > > >smbclient \\\\clang\\public > >Added interface ip=128.104.25.251 bcast=128.104.25.255 nmask=255.255.255.128 > >Password: > >session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair > in a Tree Connect or Session Setup are invalid.)I think you need to specify the username with -U now - by default smclient in the new release converts it to uppercase. The man page from smbclient now read: If no username is supplied, it will default to an upper- case version of the environment variable USER or LOGNAME in that order. If no username is supplied and neither environment variable exists the user name will be empty. I would rather have it leave the case alone....