Network Drives still disconnecting

Using Windows Server 2003 Small Business for 1.5 years - no probs thus far.
This past week (2 - 3 time each day), ending up with the desktop loosing
their network drive connections - this also affects their ability to print.

I have tried the command line recommended in other posts (net config server
/autodisconnect:-1) which didn't seem to help. The only "fix" we have
discovered is to reboot the desktops and re-log on..... and even then, it
takes about 10 minutes after reboot to actually get into the drives again
(and it takes forever for the logon script to complete). After 1.5 years of
no problems, why is this starting up now.

What is gonna fix this issue (not band-aid it).
Gratitude for anyone who can help.

Daryl

sounds like something basic has changed. i would start by testing the
network itself, if you don't have a good network analyzer try pinging the
server from the client and vice versa... and ping the gateway router from
each of them also to see if its the computers or network or router/switch
that is causing slowdowns. run the pings continuously for a long time to
see if there are intermittant outages or slowdowns. also monitor the cpu
and network traffic on both the server and client to see if there is
something causing them to slowdown. and of course run full virus scans on
everything. scandisk and defrag the server also. i would bet on something
simple though, like a bad port on the router or switch, failing nic on the
server, or a virus... remember, the virus doesn't have to be on the server,
it could be on any client and take up enough bandwidth to hose the whole
network.

"DC in CGY" <DC in (E-Mail Removed)> wrote in message
news:BD3459E5-38EF-4330-A129-(E-Mail Removed)...
> Using Windows Server 2003 Small Business for 1.5 years - no probs thus
> far.
> This past week (2 - 3 time each day), ending up with the desktop loosing
> their network drive connections - this also affects their ability to
> print.
>
> I have tried the command line recommended in other posts (net config
> server
> /autodisconnect:-1) which didn't seem to help. The only "fix" we have
> discovered is to reboot the desktops and re-log on..... and even then, it
> takes about 10 minutes after reboot to actually get into the drives again
> (and it takes forever for the logon script to complete). After 1.5 years
> of
> no problems, why is this starting up now.
>
> What is gonna fix this issue (not band-aid it).
> Gratitude for anyone who can help.
>
> Daryl

This may seem an overly simplistic response, but it sounds to me like a dns
issue.

Micah A. Norman