Rick Flower
1998-Mar-13 22:04 UTC
smbclient (1.9.18p3) kills WinNT 4 (SP3) Networking subsystem..
I was wondering if anyone else has seen the problem that I'm seeing with the latest version of Samba (1.9.18p3) under Solaris 2.6. I'm using it in part to backup about 15 PC clients (all but two are running NT 4) with the Amanda backup program. Anyway, the problem is that on occasion when doing a backup of one of these machines, the networking subsystem in NT just gives up and dies. Once this happens, NOTHING via the network neighborhood is available, all network connections just timeout, etc.. The only fix is to reboot the system. I've noticed that smbclient NEVER appears to timeout and just give up! I just looked, and smbclient is still waiting for something to happen, even though my machine went "south" about 2 hours ago! Perhaps a timeout mechanism should be put into smbclient? Anyway, I have noticed that IF I revert back to running 1.9.17p5 then the apparent problem appears to go away -- at least so far! When the problem does happen, I've seen it happen on SP3 and also on SP2 Win-NT machines. Any ideas on this would be appreciated.. Meanwhile I'll be once again switching back to 1.9.17p5 -- Rick ;======================= Global Settings ====================================[global] debuglevel = 3 workgroup = dh comment = Justice Samba Server admin users = root load printers = no printing = sysv log file = /usr/local/samba/var/log.%m username map = /usr/local/samba/lib/users.map max log size = 50 hide dot files = yes browseable = yes preserve case = yes short preserve case = yes guest account = guest encrypt passwords = yes status = yes dead time = 10 lock directory = /usr/local/samba/var/locks locking = yes domain master = no local master = yes preferred master = yes os level = 65 share modes = yes wins support = no wins server = 129.193.108.22 socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=16384 SO_RCVBUF=16384 security = user
Simon Hyde
1998-Mar-15 22:18 UTC
smbclient (1.9.18p3) kills WinNT 4 (SP3) Networking subsystem..
On Sat, 14 Mar 1998 14:40:28 +1100, you wrote:>I was wondering if anyone else has seen the problem that I'm seeing with >the latest version of Samba (1.9.18p3) under Solaris 2.6. I'm using it in >part to backup about 15 PC clients (all but two are running NT 4) with >the Amanda backup program. Anyway, the problem is that on occasion >when doing a backup of one of these machines, the networking subsystem >in NT just gives up and dies. Once this happens, NOTHING via the network >neighborhood is available, all network connections just timeout, etc.. The >only fix is to reboot the system. > >I've noticed that smbclient NEVER appears to timeout and just give up! >I just looked, and smbclient is still waiting for something to happen, even >though my machine went "south" about 2 hours ago! Perhaps a timeout >mechanism should be put into smbclient? > >Anyway, I have noticed that IF I revert back to running 1.9.17p5 then the >apparent problem appears to go away -- at least so far! > >When the problem does happen, I've seen it happen on SP3 and also on >SP2 Win-NT machines. > >Any ideas on this would be appreciated.. Meanwhile I'll be once again >switching back to 1.9.17p5 >I've seen exactly the same problem on a WinNT (SP0 if I recall correctly) system with using the smbclient in Samba 1.9.17p1 through smbtar to run a backup (on an SGI running IRIX 6.2 if it makes any difference). We run backups overnight and just found that smbclient seemed to stop halfway through the backup and all the networking in the NT system went down (I think I found out it was all the TCP/IP networking and not just SMB by running trying to ping another machine, but I can't be sure about this one). This was the only NT machine we had and was dual booting with windows 95 so for now we've fixed this by simply making sure that the machine is running windows 95 at the time of the backup. Simon Hyde ----------------------------------------------------------- With a PC, I always felt limited by the software available. On Unix, I am limited only by my knowledge.