Reviewing PingPlotter data for problems
When you review PingPlotter data, set your Samples to include to 1. This will show each ping individually rather than averaging the data together. Look for periods of sustained packet loss on the end host. Packet loss shows up as a red vertical bar along the graph on the bottom of the window.
A few seconds of packet loss may be sufficient to cause the Citrix client to drop connection. When you find sustained packet loss, double-click within the red bar at the bottom and find the last host that responds in the top section. If you frequently see this host as the last responder, it may be causing the connectivity problems. Often it is with a third-party Internet backbone router. These problems may be difficult to resolve, as neither Thomson Reuters nor you hold a business relationship with the company that controls the problem router.
Additionally, look for high latency (in this context, the delay for the ping to reach a specific hop, which is measured in milliseconds), which can also translate to disconnections and general performance issues as well. Latency for most high-speed Internet connections is typically under 100ms, with 40ms or less being ideal. Anything higher than a sustaining latency of over 100ms could be potentially cause performance issues, and points of latency reaching 200ms and higher (which will show in the PingPlotter graphs as yellow and red) will often have a significant impact.
If you do indeed see any packet loss or high latency, work with your qualified IT professional and ISP to determine the cause and resolution. If the issues are occurring outside of your ISP's network, they often have existing relationships with the other provider and can work with them to resolve the issue. In rare circumstances where your ISP is unable to work with a provider that manages a hop closer to our data center, Thomson Reuters' network technicians may be able to assist.