"Network is busy" --- Help!

Post #2,861 by jbrabeck 7/26/01 8:13:30 AM Reply	"Network is busy" --- Help! I switched boxes that housed my firewall. New box is Celeron 500, 128mb RAM, 4gb hd, 3COM nic to the cable modem and built-in nic to my internal network. OS is RH 7.0 w/Samba. I moved the netscape profiles to the firewall box (from local computers). All the workstations are running Windows 9x. My problem is: No one can reach the profiles. When connecting to the firewall computer, Windows returns the message "Network is busy". I tried again this morning with nobody on the system except me. Still got the same message. I can reach the internet when I use either a local profile or a profile from a different server. This is a home system. Where do I look or what do I check? Joe
Post #3,010 by static 7/30/01 7:45:34 AM Reply	SMB Problem. And it's probably Windows' fault. Some things I'd do: Check that you're using NetBIOS on TCP/IP. How have you done the user verification in Samba? How are you doing the login setting in Windows? I had this problem with ME and a RH6.2 box some while ago. It was ME chucking a fit and it got over it all by itself after a few days. shrug Wade. "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #3,013 by jbrabeck 7/30/01 8:03:13 AM Reply	Re: SMB Problem. I'll check, but here is some more background. I moved the firewall to a new computer. The old server was always accessible. And the other server on the network is readily accessible. I did a fresh install of RH7.0 on the new server (same version on other two servers). Everything ran fine for the first few days, then we (family) started getting the "Network is busy" error. FWIW I do have a switch and a hub installed. But again, the other server and the old firewall worked without a problem. That leads me to believe I've set something incorrectly when I installed RH/Samba.
Post #3,016 by static 7/30/01 8:44:21 AM Reply	How long has it been failing? It really does sound like Windows has got its knickers in a knot for no good reason - it should fix itself in a day or so, though with Windows 95 you may have to nuke and then rebuild the networking stack. Though I aill admit I'm a bit concerned as to why all the machines are failing. Yes, comparing the two Samba settings and files would be a good thing. Wade. "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #3,388 by jbrabeck 8/1/01 9:31:30 AM Reply	Two weeks now..... Compared Samba files. Switched main server from master browser YES to NO. Same for any setting that would indicate preference for main. Then set preferences on firewall to yes. Still nothing. Added a new computer to the network last night (Win98). Connected to main server without a problem, Network is busy when attempting to connect to the firewall server. All computers can get to the internet through the firewall server, just cannot access any files on the server. I can telnet into the firewall server. My guesses..... Since everyone can access the internet through the firewall server, and I can telnet into the firewall server, the problem cannot be the NIC (mb built in) Since it happens with each ws, it's not the ws config. Since other servers on the hub are accessible, it's not the wiring. Which just leaves the firewall server, but where???? Joe
Post #6,628 by jbrabeck 8/24/01 2:07:59 PM Reply	Got it back up and running. Temporary solution was to use other box. Then... I pretended it was a Windoze box and did the RRR. Reinstalled Linux, same settings as before, and now everything works correctly. Of course, this is what it did originally, worked then became "busy". I'll continue to monitor the box, and if I start getting the 'network is busy' error message again, I'll be back for any additional suggestions. Thanks for all the previous suggestions. [link\|mailto:jbrabeck@mn.mediaone.net\|Joe]

Welcome to IWETHEY!