Carroll Kong > Aha, this is an interesting angle I haven't thought of! I tried it, > here's what > happens; I get the error message of: > > ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree Connect or > Session > Setup are invalid.) > Ok. If you got an error running smbclient to your own box.... check to see if you did it properly? smbclient -L hostname -U username? And try your password. If you did this properly... from linux to samba... and it failed. Odds are you have encrypted passwords enabled in /usr/local/samba/lib/smb.conf?
This is a guess of mine.. or you do not have security = user but ... you seem to have that setup. Or... it was not a valid user? Ok... assuming you can get yourself connected to samba... you can enable encrypted passwords, which I do suggest, both ways are insecure but if this network you are describing has relatively good security and is more LAN than WAN, having encrypted passwords is not such a bad thing. You should read the /samba-1.9.1.8p4/docs/ENCRYPTION.TXT. run the cat /etc/passwd | ./mksambapass.sh or what not... there is a line in the .txt file. After you run that though, you should run ./smbpasswd <username> for each user. I could NOT find a way around this at all. I do not think the /./mksambapasswd successfully ports the unix hashed passwords since the unix hashed passwords cannot be converted to the smb hashed passwords. (sorry for the bad terminology.. heheh). So in essense, the "smb password" will be different from their telnet login password. Once again, double check the linux smbclient to linux samba. If you cannot do that successfully, I cannot imagine you getting the Win 95 logging in successfully before your own linux smbclient to samba. > > And how do you setup "plain text passwords" through NetBios in windows 95? > > Perhaps plain text is the wrong terminology, I just meant unencrypted. > It's done > by adding a registry key and is documented in /usr/doc/samba's Win95.txt. > Randy | / /__ / / / \// //_// \ \/ / Ah.. a registry add on. That is what I meant... "plain text" passwords is the right terminology, I believe, I did not know it was a registry key fix. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
