SUMMARY: Samba 2.0 and passwords

[Paul Crittenden]

I would like to see those of us who send an inquiry to this list also send
a summary of what fixed the problem so that someone in the future could
find the answer.  I searched archives for an answer and only found
questions.  Since a lot of folks reply ot individuals then even the replies
don't end up in the archives and so it would be nice if summaries were sent
to the list.  Anyway, enough of my soapbox for a Monday.  Here is what I
figures out.


I spent several hours on my computer at home over the weekend and figured
out the answer.  Since I am not a programmer I will try to explain it as
best I can and perhaps someone who is a programmer can explain why this is
the answer.
Anyway, on the system that everything worked on C2 security subsets were
not installed.  On the two that didn't work C2 security subsets were
installed.
I uninstalled the C2 security subsets from the two which didn't work and
voila everything works great, SWAT included.  It appears to me that C2
support is compiled into Samba automatically now and if those subset are on
the system then it assumes you are using enhanced security and that screws
thing up.  Like I said I am not a programmer so this could be a wrong
assumption.  I looked at the configure script and it has a section in it
for OSF and HPUX which tlaks about C2 security.  Let me know if this is a
correct interpretation.



Original Message:
I have one Dec Alpha running v4.0d.  I am running 2.0.2 and have run 2.0.0
with no problems.  SWAT works fine on it also.  I have 2 other systems, one
running v4.0d and the other running v4.0b.  On those systems I can connect
to guest volumes just fine but anything that requires a password fails with
a "Bad Password" error.  SWAT will not let me connect either and fails with
a "Bad Password" error.  I have run through the suggestions in the file
DIAGNOSIS.txt.  Tests 1 - 6 and 8 work fine, tests 7 & 9.  My PC's are
running Windows95.  I have tried running with security set to SHARE and to
USER and get the same result.  I have tried to move the compiled software
from the system that works to the ones that don't and still no luck.  I
have even used the smb.conf file, which I will include in this message, and
things don't work.  If I try to connect to my share using the smbclient
command I get "Bad Password" errors.  I have tried everything I can think
of and am at a loss to explain this.  It doesn't make sense to me that
things work on the one system but not on the other two.  I am not running
shadow passwords and passwords are not encrypted.  Please HELP!!!!

Here is my smb.conf file which works on one system just fine but not on the
other two.

# Global parameters
	interfaces = 198.206.243.1/255.255.255.0
	security = SHARE
	log file = /usr/local/samba/logs/log.%m
	max log size = 500
	socket options = TCP_NODELAY
	printcap name = /etc/printcap
	guest account = guest
	printing = bsd

[homes]
	comment = Home Directories
	read only = No
	create mask = 0750
	browseable = No

Paul Crittenden
Computer System Manager
Simpson College
e-mail: crittend at simpson.edu

Y2K?  Why not 3?