It never rains but it pours: I've had four Samba call in the past two days. A couple of things to keep in mind as a result of helping those folks:
You NEED to set "encrypted passwords = Yes" in smb.conf (or Swat if you prefer to use that to configure Samba). If you don't, Samba is going to refuse modern Windows clients.
If using Swat, you can't just fill in a name and password if the user doesn't already exist. You have to ADD the user. If you just put in a name and password, Swat doesn't complain, but nothing gets added to smbpassword.
User names added to Samba MUST be Unix users already.
This seems to confuse folks: you can have a file that maps Windows names to Unix/Samb logins. For example:
root = administrator
linda = lfrench
If you do that, you probably want to set the samba passwords to match what they are being mapped from. So in this case, we'd probably set root's samba password to match the Windows "administrator", and linda's password would be set to match her Windows "lfrench" password. You don't HAVE to do that (you can use "connect as a different user") but it may make things less confusing.
If you are having confusing trouble, set "log level = 2" and check the logs. Where are the logs? Wherever smb.conf says they are.
*Originally published at APLawrence.com
A.P. Lawrence provides SCO Unix and Linux consulting services http://www.pcunix.com
Running Samba on the Mac OS X ServerGoogle Brings Samba, CC Early GiftsSamba's Allison Dumps Novell For GoogleNetwork Neighborhood, Visionfs, Samba Authentication and all thatCounterpoint on Red Hat LinuxMake a Linux Home Data Server of an Old PCSCO Openserver release 5.0.7A Linux Fax Server for a Windows NetworkSMB CachingUnix Permissions
Comments
Post new comment