The Network is Busy

  • Thread starter Thread starter Franker
  • Start date Start date
F

Franker

Hello,

I am setting up a new Windows Server 2003 System for the
company. There is only one server in this network. DNS
and WINS are enabled and appear to be functioning
properly. We have several Win95 and Win98Se workstations
that have DSCLIENT installed on them.

The problem that I am running into is at the workstation
level. Users are able to logon to the server but, after a
period of inactivity, they:

1. are unable to access their mapped shares. The message
received at the wkstn is "G: \\server\sharename is not
accessible",

2. are unable to browse the NT server via Network
Neighborhood. The message received is "The Network is
Busy",

3. are unable to log out and log back in (without
rebooting). The message received is "The domain password
you supplied is not correct, or access to your logon
server has been denied".

So far, rebooting the wkstn has allowed them to logon to
the server again, but then the above scenario repeats with
regularity.

Several reviews of the Event Viewer logs have revealed no
significant warnings or errors with respect to this
problem.

Any assistance with this problem would be greatly
appreciated. Thank you in advance.

Frank
 
Does the server have options 044 and 046 (0x8) in DHCP-server, Scope
options? Does the ipconfig/all from the W9x show that everything is pointing
to the server-IP?
 
Hello Marina,

I appreciate your response. But I still need your help.

I am not using DHCP. I am using all Static IPs and WINS.
There is only one server which is the DC. ipconfig /all
DOES indicate that all is pointing to the server-IP.

I have tried several workarounds such as setting the
autodisconnect to -1 at the cmd prompt (KB 138365),
setting a Group and Computer policy to ensure pointing to
the ntserver computer on the network (KB 814598) and
setting the following at the server:
Default Domain Policy: Account Lockout Threshold,
increase to 15 or more.
Default Domain Policy: Microsoft Network Clients ..
Digitally Sign Communication Always - Set to Disabled.

Even though I lose access on the Windows 95 wkstns, I can
wait a minute and get reconnected without rebooting.
However, I have had no such luck with the Windows 98
workstations. I am going to try KB 278558.

Any other assistance that you can provide would be greatly
appreciated.

Frank

Microsoft's security issues are a real kick in the pants.
 
Why aren't you using DHCP? It really is a no-brainer and it will push all
necessary settings to your clients.
How many nics in your server?
 
Back
Top