Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Users are reporting that it's taking a long time to access files on the network, browse intranet sites, etc. What should I check?

share|improve this question
up vote 7 down vote accepted

To check the latency on a network:

Run a continuous ping from the command line:

ping -t [destination IP DNS or hostname]

Do this:

  • From your PC to the users PC
  • Your PC to the file server
  • Your PC to Internet sites
  • etc.

If any of these are slow, then run:

tracert [destination IP DNS or hostname]

to see where the issue is.

To check the bandwidth of a network:

You will need to install bandwidth monitoring software, look at your network switches (if they support monitoring), look at router logs, etc. has some good tips.

share|improve this answer

Check the duplex settings on the network ports.

If one end of a network link is set to 100baseT full duplex, and the other is set to auto-negotiate, the auto-negotiating end will always go half-duplex.

This wouldn't reveal itself with simple ping tests, but any substantial traffic over the link will be a lot slower than it should be.

share|improve this answer

first tools I would use would be ping and tracert. These will let you know right away if packets are being dropped and where. Routing issues will also bubble up.

I've also seen it where proxies, configured incorrectly, can cause problems on a local network.

share|improve this answer

Incorrectly setup DNS server/settings can also slow things down.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.