Network Slowness
Network slowness is a huge problem, perceived problem, and overall high percentage of reason for opening a trouble ticket.
One such problem that I ran in to actually had a simple resolution. I however did not have eyes in the right place to find it fast.
The users reports general network slowness and application disconnects. Checking the for common simple items that could cause theses issues brought me no closer to a resolution.
I checked the circuits for errors, I checked the router logs for any indications. I checked the router interfaces for any indication of bandwidth issues. None of these led to any thing that I could follow up. I checked the remote devices in the data center. they were clean, the local devices at the affected site were clean. We had a sniffer running at the data center, and it showed no reason for the slowness or disconnects
I eventually had run pings to the users IP addresses and found that when they complained of the problem, the pings became non-responsive. At first I thought that this was their PC CPU or NIC causing the non-responsiveness.
Alternate user, came in from another branch, and he works with all the same applications from the other branch completely free of issues. However at the site in question, he has slowness and disconnects. running out of things that are within my responsibility I requested that the user run a ping to the gateway IP. I gave them this IP address. when they had a disconnect, they were to check the window that was pinging the Gateway of the Router. and I was sending pings to their machine IP from the router (Sourced from the interface of the circuit. The next Occurrence my router pings were dropped and the users was still able to ping the gateway????
I then knew we did not have a NIC problem and the Probability of the CPU had dropped considerably. I asked that they send me a copy of the IPCONFIG and Route Print from a MS-DOS window.
The Solution then revealed itself. The PC had two default gateways, one was legitimate and one was not, and as far as I could tell from documentation it was not ever valid. I had the folk that control DHCP verify what they were giving to the users in this subnet, sure enough they were suppling the extra gateway address. I requested that they remove it and all of the issues for slowness and disconnects disappeared with it.
One such problem that I ran in to actually had a simple resolution. I however did not have eyes in the right place to find it fast.
The users reports general network slowness and application disconnects. Checking the for common simple items that could cause theses issues brought me no closer to a resolution.
I checked the circuits for errors, I checked the router logs for any indications. I checked the router interfaces for any indication of bandwidth issues. None of these led to any thing that I could follow up. I checked the remote devices in the data center. they were clean, the local devices at the affected site were clean. We had a sniffer running at the data center, and it showed no reason for the slowness or disconnects
I eventually had run pings to the users IP addresses and found that when they complained of the problem, the pings became non-responsive. At first I thought that this was their PC CPU or NIC causing the non-responsiveness.
Alternate user, came in from another branch, and he works with all the same applications from the other branch completely free of issues. However at the site in question, he has slowness and disconnects. running out of things that are within my responsibility I requested that the user run a ping to the gateway IP. I gave them this IP address. when they had a disconnect, they were to check the window that was pinging the Gateway of the Router. and I was sending pings to their machine IP from the router (Sourced from the interface of the circuit. The next Occurrence my router pings were dropped and the users was still able to ping the gateway????
I then knew we did not have a NIC problem and the Probability of the CPU had dropped considerably. I asked that they send me a copy of the IPCONFIG and Route Print from a MS-DOS window.
The Solution then revealed itself. The PC had two default gateways, one was legitimate and one was not, and as far as I could tell from documentation it was not ever valid. I had the folk that control DHCP verify what they were giving to the users in this subnet, sure enough they were suppling the extra gateway address. I requested that they remove it and all of the issues for slowness and disconnects disappeared with it.
