Discussion Locked

network delay

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are running 5 desktop computers with XP Pro and running a dell server. we have Gig NIC's and a gig switch. In explorer, when you access the network drives, it delays for about 10 second (on everyones computer). Also, when going on the internet, it delays also for about 10 seconds then it flies! once the connection is "made", then we a re fine but if it idles for a few mins, the same problem happens again. The power saver option is turned off also. I hope someone can help me out.

Thanks everyone ( in advance!)

3 replies

by mgonzales

Sounds like some type of name resolution issue. Are you running dns and wins on this network?

If you are then maybe you should consider telling the DNS server to use WINS for host name resolution. Also make sure under the wins tab the check box is NOT checked to use lmhosts.

Good Luck!

by curlergirl

What operating system is the server running? Is it Win2K or Win2K3 server? Or is it an XP Pro machine acting as a server in a peer-to-peer network? If the latter is the case, then there is probably nothing you can do about the delays - it is a browsing issue that you're just going to have to live with. If it's Win2K or Win2K3, I agree with the above comments.

Also, you might want to look at whether you are using a network hub or switch. Because of increased traffic caused by the methods of authentication and response used by Win2K and Win2K3 server, even in a small network like yours using a switch rather than a hub will increase your network response time by a noticeable, although small, margin.

Hope this helps!

by djbrown62

I agree - both issues sound like name resolution.

For the network drive problem:
Use the DOS "Net Use" utility to see if you have any invalid drive connections.

Also right-click on Network Places > Disconnect Network Drive... and disconnect any that are invalid.

For the Internet problem:
This sounds like it's doing a lookup with one method, failing then moving on to the correct method. That address is cached, then times out in a few minutes and the process starts over again.
Check to see if your DNS search order is correct on the workstations.

Or if you have an intermittent internet connection (ISDN Dial-up) that would explain it too.

This discussion is closed to new replies.