How Do I Troubleshoot Latency on a Corporate Network?
How do I troubleshoot latency on a corporate network?
How do I determine the route cause of latency on a business network?
Solution:
To troubleshooting latency for customers on a corporate network:
- Check for VPN client connections - VPN connections will add a large amount of overhead to the connection and can cause latency. In a command prompt, type the command ipconfig and press enter. If two IP addresses are displayed, this may indicate that a VPN is being used.
- Recommendation: Disable the VPN connection if you are experiencing a latency problem.
- Recommendation: Disable the VPN connection if you are experiencing a latency problem.
- Optimizing Proxy Servers - Some proxy servers can also add latency depending on their configuration. In a command prompt, the command netSH WinHTTP Show Proxy (Windows 7) will determine if there is a proxy in use on the network.
- Recommendation: Advise your IT department to create exceptions for the Webex.com domain to avoid caching of Webex content on the proxy.
- Recommendation: Advise your IT department to create exceptions for the Webex.com domain to avoid caching of Webex content on the proxy.
- Gateway Load - This can be caused by an overloaded gateway on the corporate network. Running multiple traceroutes (traces) while the latency is occurring may identify the source. This could be worse at peak usage times on the enterprise network.
- Recommendation: Speak with IT to understand the type of connection the network is using (T1, T3, OC3, etc.), number of users on the network & typical peek usage periods to understand if an overloaded gateway could be a concern.
Gather the information below:
- Three forward traces to the client's Webex site.
- Capture at least three speed test results from a site such as http://www.speedtest.net. It is recommended that the client run a trace to the server closest to them, and then a trace to the server closest to their Webex site location.
Was this article helpful?
