+ Post New Thread
Results 1 to 5 of 5
Wireless Networks Thread, If your network suddenly goes slow..... in Technical; Where do you look? Has happened twice today - enough that the phone has gone hot.... I've checked event logs ...
  1. #1
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31

    If your network suddenly goes slow.....

    Where do you look?

    Has happened twice today - enough that the phone has gone hot....

    I've checked event logs for every server and nothing to suggest a problem.
    I've checked the VMWare stuff and performance graphs suggest nothing either.

    I've set a pc in my office to ping and output to a file for the 3 core switches and one of the servers and will analyse the results in the morning.

    What other tools could I use to monitor what happens?

    Hate these random, can't replicate issues....

  2. #2

    tmcd35's Avatar
    Join Date
    Jul 2005
    Location
    Norfolk
    Posts
    5,760
    Thank Post
    860
    Thanked 908 Times in 753 Posts
    Blog Entries
    9
    Rep Power
    330
    Sudden complete slowdowns of the entire network is usually a sign of a network storm caused by loop - lan cable between two sockets. When it happens it's usually a case of wandering around the school until you find the culprit. Harder to find are faulty nics that can cause the same problem. Setting up spanning tree on your switches can help alleviate the problem.

    Of course it's not the only cause, just the most likely (from experience). This term we've had major network slow down issues here that where caused by bad profiles.

    We retired a couple of old file servers and of course every ones profiles contained 'recent document' links to files on the old servers. Now we did anticipate the problem and deleted all the profiles stored on the server in order to get new ones created. We didn't take in to account that instead of creating fresh profiles Windows would just upload the old copies of the profiles from staff laptops back on to the server. So everyone has been complaining their computers are running very very slow because they are searching for files that don't exist.

  3. Thanks to tmcd35 from:

    diggory (17th September 2010)

  4. #3

    Join Date
    Mar 2007
    Posts
    1,802
    Thank Post
    85
    Thanked 296 Times in 227 Posts
    Rep Power
    87
    I'd set machines pinging each other to see if its a data transfer problem, but it also might be a multitude of single instance problems, for instance if your new anti virus is doing a scan at the same time.

  5. #4
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    Pings to my core switch look pretty solid...
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=8ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=20ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=8ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=29ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=14ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=6ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=30ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=5ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=4ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=3ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=32ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=2ms TTL=255
    Reply from 10.7.43.171: bytes=32 time=1ms TTL=255

    Have checked the SOPHOS console and nothing there looks out of the ordinary...

  6. #5


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,658
    Thank Post
    276
    Thanked 780 Times in 607 Posts
    Rep Power
    224
    I don't need to look - Nagios is texting me about what's wrong and Cacti is creating pretty graphs to cross-reference that.

    Network monitoring is your friend - it greatly decreases the amount of problems that can't be fixed before end-users experience the effects, it increases your confidence in the kit (or points out poor performing kit) and it means you have solid baseline figures of how it should be to compare against the current status,

    To accomplish this there are loads of tools, some trickier than others, but all free (or they have a free, limited version):

    Nagios: Shows a snapshot of what's happening and available Right Now, with some historical logging.
    Cacti: Historical trends to identify bottlenecks/wierdness at certain times of day.
    Zenoss or Zabbix: Which combine the functions of Cacti and Nagios.
    OSSIM: provides Nagios, Ntop and a bunch of security tools (Snort, Ossec, Nessus etc).
    There's also The Dude or Spiceworks if you must run monitoring software on Windows.

    This takes time to setup, but it repays the effort quickly. I'd rather do without vim than lose monitoring,
    Last edited by pete; 10th September 2010 at 09:10 AM.

SHARE:
+ Post New Thread

Similar Threads

  1. Help - Slow network
    By bodminman in forum Wireless Networks
    Replies: 9
    Last Post: 1st October 2009, 08:44 PM
  2. Slow Network
    By dyoung5 in forum Windows 7
    Replies: 13
    Last Post: 15th May 2009, 12:32 PM
  3. Network Slow Down in One Classroom
    By FragglePete in forum Wireless Networks
    Replies: 10
    Last Post: 4th October 2008, 01:54 PM
  4. Sudden Slow Network
    By binky in forum Windows
    Replies: 7
    Last Post: 28th February 2008, 08:12 PM
  5. Slow copying over the network
    By zag in forum Windows Vista
    Replies: 1
    Last Post: 16th November 2007, 08:43 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •