Paul G. Allen said:
> We have an UltraSparc running an older version of Solaris (not sure
> what version - I'm not the admin) and running a 3.x version of Samba.
> We seem to be having two issues with Windows<->Samba connections. We
> use *plain text passwords* and I have set every reference to
> enableplaintextpasswords on my desktop to '1'. My account worked
> twice, on two different occasions.
>
> 1. W2K machines will not log in to the Samba server. They give the
> message "Invalid user name or password". Win98 machines work fine. We
> have no XP machines.
Have these machines been set up with trust accounts on the Samba
server? To find out check for HOSTNAME$ entries in the smbpasswd file.
Are the users logging in to the domain or the local machine? Is the
samba server the PDC for the domain?
> 2. Using smbclient on my RHEL WS 3 laptop works fine.
That says that the Samba server is working. It doesn't however tell us
anything about the trust relationship between Win2K and Samba.
> 3. It seems copying files and getting directory listings takes longer
> than it should: 10 seconds for a directory listing (even a short
> dir.), more than 30 min. now for me to copy 23MB of files (using my
> laptop) from my home dir on the Samba server to my local drive. This
> happens with multiple users and on Win98 as well.
This may have something to do with the WINS service.
> It seems the login issue started around the time of some W2K patches a
> couple months ago, but since I had not been using the Samba server
> much before that, I can't verify it.
Perhaps a local firewall change took place with the patches? Microsoft
has been changing default configurations along with patch installs for
"security". It's causing no end of grief for some administrators.
> I've also had connection issues at home (Samba on RH 9.0), but
> restarting the Samba services always fixes the problem. Again, this
> started AFTER a W2K update, and this I have verified (since they are
> both my machines and I have full control over them). Also, I use
> encrypted passwords at home as well as LDAP for authentication.
>
Hopefully some of the above will help you debug the problem.
--
Neil Schneider pacneil_at_linuxgeek_dot_net
http://www.paccomp.com
Key fingerprint = 67F0 E493 FCC0 0A8C 769B 8209 32D7 1DB1 8460 C47D
Sometimes I wonder whether the world is being run by smart people who
are putting us on, or by imbeciles who really mean it - Mark Twain
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
