Ok, I've gone through the list archives, and there's a bunch of questions, but no answers. I'm referring to the Error: Network is busy when logging in from both Win95 (a and b versions) and Win98. It seems to never give this message unless the Windoze machine has been rebooted forcefully - it seems as if the samba server hasn't realized that the client has left, and is locking the connection somehow. After a short time (a few seconds to a few minutes) the connection rights itself. There doesn't seem to be any correlation between cpu usage for smbd and this error.. I've seen it when there hasn't been anyone else connected to the machine. Any ideas? J.
hello, thanks for the replies about restarting samba... here is another one .... on a few pc's (2 so far win95-b) when I try to map a network drive to \\server\apps I get the message "network is busy".. I currently have one samba server and one advance file and print server ie(nt 3.51) running on an sco box. my security mode is share and I have a few people logged in as guest... any clues why the "network is busy"?? ps I just upgraded to 1.9.18p10 yesterday.. still same message. ps ps. it seems to happen when I remove the novell stuff from the clients ie ipx compatable protocol... and just have tcp and microsoft stuff loaded.. (could be a coicidence).. thanks in advance.. Robert
You have a DNS setup problem on the server running SAMBA. Make sure that resolv.conf, etc is setup so that it does NOT take a long time for it to decide that a client's ip does not have a host name attached. Apparantly it takes to long if say, the first ip# in the resolv.conf is not available, even though the second one is available, and you get Network Is Busy, I had this happen to me, had resolv.conf pointed to NS over a modem link. Modem went down, suddenly no one could print... :) I went nuts, (even deleted and re-installed thinking corruption?) but, have now setup BIND/NAMED on a local box, and have all local machines pointed to that instead. Problem went away after then rebooting unix box (FreeBSD btw) -Mike PC Systems Administrator Edward Waters College 1658 Kings Road Jacksonville, FL 32209 mjoyner@ewc.edu
I'm afraid I won't be much help resolving this problem, I only wanted to point out the we seem to be experiencing exactly the same problem. We were connected to Samba on an HP3000 server running 1.9.?, without any problem, but when we upgraded the server to 2.04 our Win95 and Win98 clients all get a Network is busy error whenever we try to connect. A Windows NT client seems to connect fine, however we have noticed that there is a long delay (20-30 seconds) when we first connect. One other thing that we noticed is that when we start samba on the HP3000 it seems to be doing some sort of polling which is causing our proxy server (on the NT machine) to dial out to the internet as if it is looking for an IP address that isn't on our local network. I have been able to track it down yet, but this polling is keeping our internet connection open all the time that Samba is running. Does anybody have any idea what it's doing, and where I can find the IP address that it's trying to poll?>Date: Wed, 19 May 1999 12:43:04 -0400 >From: "W. Bryan Caudle" <bcaudle@ctsi.net> >To: samba@samba.org >Subject: Network is busy... >Message-ID: <3.0.6.32.19990519124304.0144b100@ctsi.net>>I have decided to post this message again in hopes that someone might have >a clue as to what is going on. Since the original post, we have also tried >Samba 2.0.4 on the production machine with the same result. Samba 2.0.3 >contunues to run on the identically configured test system with no problems >at all.---------------------------------------------------------------------------- ----------------- Bruce Collins <bruce_collins@ibm.net> Technical Specialist Phone : (416) 868-6550 Ext 24 Lee Merrick & Assoc. Fax : (416) 868-6174 ---------------------------------------------------------------------------- -----------------