I am having a problem with Terminal Services connection. One of my clients has a Terminal Server which a remote office connects too. They have been getting disconnected from the Terminal Services connection for a few weeks now. I ran pingplotter over several days and noticed some pretty severe packet loss.
http://img50.imageshack.us/img50/9788/671298043rdslktccombh1.png

After tracking for several days and logging disconnect times. When the client recieved packet loss they would get disconnected from their Terminal Services Session. I sent the ISP images of pingplotter results. The ISP had me run several ping and tracerts and send the log to them ping showed zero packet loss over a 45 minute period. Tracert worked without problem as well.

Ping statistics for 67.129.80.43:
Packets: Sent = 1507, Received = 1507, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 180ms, Average = 94ms

I know packet loss is happening and causing the disconnects from Terminal Services as I temporarily hosted another terminal server on a different ISP and had no disconnection problems. It seems to be the particular route that the information is taking that is causing the problem. Any route involving level3.net seems to cause disconnections. The ISP claims there is no problem with the circuit.

The interesting thing is if I do a Pingplotter from the Server to the clients static ip they have a few high spikes but NO packet loss. The ISP is trying to tell me its my router. Any ideas on further steps I could take before just switching ISP's for the whole organization?
http://img50.imageshack.us/img50/8654/mnsfinalwe8.png