CompassClient debug procedures

There is a potential issue with the client, and some software on user machines that may also be running at the same time.  To pinpoint this, we need to know the timing difference between the network and the application.

YOU *MUST* have Compass Client 1.74 or newer for this to work.

There is Compas Client tool to help you figure this out.  After connected, if you click on 'Connection' in the cpclient menu bar (the Logon screen menu bar), and then select 'debugTimings'  A new window will popup, and show you the different timings.

When open, the debugTimings window will show you both network and application level Round Trip Times(RTT) as well as the difference between the 2(with yellow background).  The network layer is not a ICMP ping (because they normally are delayed/ignored by routers along the way), but based on how long it takes to open a socket connection with the server.

The Application layer is the RTT time to send a 13-byte TCP packet thru the secure tunnel, to the server, and return, much like the traffic does for Display.

The Network layer is identical to Application Layer, except it's not going thru the secure tunnel.

The delay shouldn't be more then 1ms on average between the two, as you can see in the Debug Info screenshot above.

Also you will notice the Current Times and 1min avg labels are highlighted blue, while 5min avg is not.  They are highlighted blue when there is more than current, 1min or 5 min values to display.  i.e. if you wait 5 minutes after starting up Debug Info screen, then the 5min avg will be blue, and you know that the value there really is a 5 minute average.

The procedure for using this timing info is such:

1.  Launch the debug timings window
2. wait at least 1 minute for the timing avg to be accurate
3. Close or terminate 1 process/service.
4. Check the difference in the Debug Timings window.

Repeat steps 2-4 until you get less than 1ms difference between network and application level ping times.

Please let the Compass dev team know what the results of this testing is, so we can continue to troubleshoot and fix the problem.

In case you don't have this information handy, here is a (mostly complete) list of programs/processes/services you should not kill:

• 'System Idle Process',
• 'System',
• 'explorer.exe',
• 'taskmgr.exe',
• 'spoolsv.exe',
• 'lsass.exe',
• 'csrss.exe',
• 'smss.exe',
• 'winlogon.exe',
• 'svchost.exe',
• 'services.exe',
• 'Xming.exe', #xming (part of cpclient)
• 'python.exe', #python (part of cpclient)
• 'plink.exe', #ssh connection (part of cpclient)
• 'window.exe', #main cpclient application (part of cpclient)
• 'pingtcp.exe', #part of the debugTimings window (part of cpclient)
• 'dwm.exe', #Desktop Window Manager (>win7)
• 'wininit.exe',  #Windows Initialize (>xp)
• 'conhost.exe',  #console Host >vista
• 'taskhost.exe', #Windows Host Task starter (?)