Windows doesn't send passwords to Samba

This is really a Windows question, but I figure an expert on Samba ought to know the answer.  

Samba rejects attempts by my Windows machine to connect.  Hours of studying and investigation shows that the reason is that Windows is not sending a password with the userid.  It sends the expected userid, but the "password length" fields in the packet are zero.  This in spite of the fact that I type in a real password when "NET USE" prompts me for one.  I also type one into the "network login" box when I log in to Windows.

Any idea how I persuade Windows to send a password?

It's Windows ME.


LVL 5
bryanhAsked:
Who is Participating?
 
jlevieConnect With a Mentor Commented:
I think that ME will only send an SMB encrypted password to the server and it may be that the only one it sends is the one assocaiated with the user you logged in to ME with. So far as I know ME, 95, and 98 are alike in this regard and those OS's don't use the username/password themselves, but hang on to it for authentication to servers.

Try this. On the Samba server create an SMB password for the Linux username that you'll be using on the ME box using the same password as you use on ME. Also check your smb.conf file to be sure that it contains "encrypt passords = yes" and if you have to add or uncomment that line restart Samba. Then log onto the ME box and see if you can access tings on the Samba server.
0
 
jlevieCommented:
Do you have Samba configured to use encrypted passwords and does this user have an SMB encrypted password (meaning that you created an SMB password with sbmpassed)? Also take note of the fact that the windows user name must be the same as the Linux user name and that case matters for both the username and password.
0
 
jlevieCommented:
Oh yes, have you configured the ME box to require a a logon before accessing windows?
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
bryanhAuthor Commented:
No, there's no smbpasswd file and the smb.conf file is the simple one from the "installing on unix" instructions.

The ME box puts up a window when it boots asking for a network userid and password.  It doesn't seem to care at that point what I type for password, but if it isn't right a later box comes up asking me to log on to windows and type the correct password.  In all cases permutations of passwords entere/required, the packets set by NET USE contain zero length passwords, according to the Samba-enhanced Tcpdump.

0
 
bryanhAuthor Commented:
After I read about encrypted passwords in the Samba documentation, I could see that you're exactly right.  One can enable unencrypted passwords in the registry, but all modern Windows variations have it disabled by default.  Of course, Windows doesn't have the courtesy to issue a message saying, "the server will accept only unencrypted passwords and you have disabled those so I sent a null password instead and guess what?  the server didn't accept it."  Instead, the error message is "invalid password.  Enter the correct one."

I set up encrypted passwords and all is well.

Hard to believe the Samba "getting started" documentation still leads you through this unencrypted password dead end.  I will see if I can get that fixed.
0
 
jlevieCommented:
I'd have to agree with you about the ambiguity in the Samba doucmentation. It should say that anything since win95 w/service pack ? (don't remember which) requires encrypted passwords. This is a problem that has existed for a very long time and it ought to be emphasized that you pretty much need SMB encrypted passwords for things to work.
0
All Courses

From novice to tech pro — start learning today.