Slow network drive access if XP left on overnight

Hello All,
     I have a funky one that I can't figure out.  I have a server that is a standalone SBS 2000 server with a little lan (4 computers), and I get this funked out problem.  After about 12 hours or so, the network connections are reduced to a crawling pace.  A network drive that would normally take 1-2 seconds to pop open will take about 90 seconds.  I have checked that system does NOT go into hibernate or standby.  System network controller is also set at 100 / Full as opposed to auto.  Network cards are 3c90b 3com 100 ethernet on server - linksys 8 port fast ethernet switch - broadcom 100 mbps integrated dell chip.  Everything else works at regular speed however, AKA internet, accessing shares on other computers.  
     The only thing that seems to fix the problem is rebooting the workstation, at which point it is happy to talk with the server.
     I hope someone has the solution, I've searched the site and gone through a couple of beers over the last few months trying to fix this one off and on!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Well the first thing we have to do is crack open another beer.  Then we need to know if it's one workstation or all of the workstations.  Is the connection between the workstation(s) and server the same as a connection from workstation to workstation?  I know on some Linksys switches or hubs, if you're using one of the ports as an uplink port, say port 1, then port 2 will not work right.  
pkillurAuthor Commented:
Hmmm.  AFAIK, (I'm not there right now) the connections are (on the switch)
1 = DSL router,
2= Server,
3=Workstation (98, no problems [at least with slowdown!]),
7=workstation 1 (xp), slowdown issues after12 hours, micron mfg'd system, 3com network card,
8=workstation 2 (xp), slowdown issues after 12ish hours, dell inspiron, broadcom 100mbit built in port.

Snap goes beer top number one (if at least in my head)...
Instead of rebooting the servers have you tried rebooting the switch?  The computers are nothing alike and they're having the same problem.  Maybe it's the switch?
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

What are your client machines pointing to for DNS? They should be pointing to the server and the server should be pointing to itself, then the ISP DNS server as secondary.

Also, check the users account and see if the account is set to disconnect the session after XX amount of time and what the reconnect rules are.

pkillurAuthor Commented:
I did check that out, and it has no values for the user logon/off timeout or session timeout.  There are no reconnect rules that I could find.  The place I checked was Active Domain Users and Computers.  Is that the right place to look?

Also, DNS is the following:

Users:  Server

Server: Itself (.10)
            SBC 1
            SBC 2
In AD Users and Computers you will select the user account in question and right click then select properties.

Once in the user properties, you will then select the sessions tab. If it is in the default mode, it will read "never" X3/disconnect/from any computer.

If these are the settings you have then the users account shouldn't time out unless you have a group policy set elsewhere.

You can also open a MMC and load the RSoP snap in. This will allow you to see if you have a policy set that you might have missed.

I'll keep thinking on this one.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pkillurAuthor Commented:
Found out that it was a screwed up forwarder in the DNS settings.  Thanks for all the help!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.