I do have a DNS server that resolves the hostname of the server correctly. (For example pinging the samba server by name works correctly and quickly.)
I should point out that if I have two network connections to the linux box that are restored on login BOTH connection attempts are slow. Furthermore later attempts to map/browse other shares on this machine also experience the same kind of delay. This problem isn't just the first one (otherwise I wouldn't have posted, knowing there are name resolution delays).
I checked log.<client machine> to see if there were any clues there, and here's what I found:
...
[2002/11/01 16:10:23, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User val !
[2002/11/01 16:10:25, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User val !
[2002/11/01 16:10:28, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User nobody !
[2002/11/01 16:10:30, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User nobody !
[2002/11/01 16:10:32, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User fred !
[2002/11/01 16:10:35, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User fred !
[2002/11/01 16:10:37, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User val !
[2002/11/01 16:10:39, 0] passdb/pampass.c:smb_pam_passcheck(827)
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User val !
This is what resulted from mapping a drive as user val to her home share. It successfully connected but what the heck is it doing? Needless to say, the log is filled with similar...
Any help?
FjK
Collins, Kevin wrote:
Fred:
I don't know if this is it, but do you have a DNS server or a HOSTS file
on the Windows machine(s) pointing to the IP of the Linux box? If not,
here is what (I think) is happening: Windows 98 will try to contact a
DNS server to locate the network machine and fail with a time out (which
takes several seconds). Then it will revert to the WINS service and
find the Linux box. Windows cache's WINS resolutions and that's why
subsequent connections are "peppy".
My forward look-up zone was "fubar"ed on my DNS server here at work and
my Windows machines exhibited the exact same symptoms as you describe.
I fixed the zone file and everything began to operate properly.
If this isn't it, I'm sorry for feeding you bad information. :-)
Kevin L. Collins
-----Original Message-----
From: Fred Kuipers [mailto:fred@;kuipers.dhs.org]
Sent: Friday, November 01, 2002 3:12 PM
To: [EMAIL PROTECTED]
Subject: [Samba] SLOW connections
Hi everyone,
I have a small home network with a Samba 2.2.3 server on Linux serving up my files and printers. However, from windows machines (win 98) connecting to a share takes an annoyingly long time (in the order of 10s of seconds) Connecting from a linux box is very quick. I have configured Windows 98 to fully reconnect the share on logon. If I don't, Windows Explorer hangs all over the place (even when simply loading it and it hits the network). After the initial connection, everything is pretty quick. I have run through all the diagnostics and I have no clue why Windows could be so slow connecting.
Note on hardware: 10 Mbit network, 1.2 GHz and 350 Mhz windows machines connecting to a 500 mhz linux machine (with 2 eth interfaces)... No CPU usage issues on linux server and full network availability during connections. I have no connectivity troubles with the network.
Any thots?? Is this a silly little configuration problem?
Thanks in advance.
FjK
Please Reply All - I'm not on the list.
> grep -v "^[;#]" /etc/samba/smb.conf | grep -v "^$"
[global]
workgroup = KUIPERS_HOME
server string = Samba Server %v
printcap name = lpstat
load printers = yes
printing = cups
log file = /var/log/samba/log.%m
max log size = 50
security = share
encrypt passwords = no
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
unix password sync = no
map to guest = never
password level = 0
null passwords = no
allow hosts = 192.168.0.
os level = 33
preferred master = yes
wins support = yes
interfaces = eth1 lo
dead time = 0
debug level = 0
status = yes
[homes]
comment = Home Directories
browseable = no
writable = yes
available = yes
public = no
user = fred val
only user = no
preexec close = no
root preexec close = no
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
public = yes
writable = no
printable = yes
create mode = 0700
print command = lpr-cups -P %p -o raw %s -r # using client side printer dr
ivers.
available = yes
[print$]
path = /var/lib/samba/printers
browseable = yes
read only = yes
write list = @adm root
[archive]
available = yes
browseable = yes
path = /home/archive
public = no
guest only = no
writable = yes
user = fred val
only user = no
preexec close = no
root preexec close = no
valid users = fred val
force group = users
create mask = 775
[MyDocuments]
available = yes
browseable = yes
path = /home/MyDocuments
public = no
guest only = no
writable = yes
user = fred val
only user = no
preexec close = no
root preexec close = no
valid users = fred val
force group = users
create mask = 775
[web]
available = yes
browseable = yes
path = /home/httpd
public = no
guest only = no
writable = no
allow hosts = 192.168.0.
user = fred val
only user = no
preexec close = no
root preexec close = no
force group = users
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
-- wily: something horrible happened:: Success [1]+ Aborted wily
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
