Troubleshooting an OC3 connection With A Watchguard Firewall

Hi.

We have a shared OC3 with an allocation of 100mbps. We do not use nearly that much pipe :-)

Our cio thinks the performance is not as good as it should be. The 1st results below indicate a 1.4% packet loss before the gateway, 2.7% after the first hop. Cogent (the provider) says this is patterned packet loss and is to be expected with the firewall. I find myself wondering about the latency. I was hoping to get some feedback on what these numbers should be, what kind of performance I should expect, and of course any tips. Some good windows testing ideas that don't involve ethereal would be great. Ethereals a little too much for me yet.

I cannot currently run tracert or pathping. This may have to do with the fact I am connecting by VPN at the moment, or some configuration we did on the firewall involving ICMP.

Thx
Steve

1. 10.2.2.1                                                                                      1.4%    74   10.9   5.6   1.7  64.0   7.9
 2. fa0-20.na01.b001353-0.jfk01.atlas.cogentco.com                                                2.7%    73    4.8   6.1   2.0  24.9   4.5
 3. gi1-46.3806.mpd01.jfk01.atlas.cogentco.com                                                    1.4%    73    3.8  18.6   1.9 211.6  43.0
 4. te2-1.ccr01.jfk02.atlas.cogentco.com                                                          1.4%    73  151.2  21.7   1.9 226.0  45.9
 5. te4-2.mpd01.jfk05.atlas.cogentco.com                                                          2.7%    73  182.1  49.4   2.1 239.4  77.1
 6. te2-1.ccr02.jfk05.atlas.cogentco.com                                                          0.0%    73    2.8  16.9   2.1 197.8  36.5
 7. core1-0-0-8.lga.net.google.com                                                                0.0%    73    4.4  11.1   2.1  69.6  13.8

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\slastoe>ping 10.2.2.1

Pinging 10.2.2.1 with 32 bytes of data:
Reply from 10.2.2.1: bytes=32 time<1ms TTL=64
Reply from 10.2.2.1: bytes=32 time=8ms TTL=64
Reply from 10.2.2.1: bytes=32 time<1ms TTL=64
Reply from 10.2.2.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.2.2.1: (gateway)
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 8ms, Average = 2ms


Pinging google.com [74.125.67.100] with 32 bytes of data:
Reply from 74.125.67.100: bytes=32 time=27ms TTL=243
Reply from 74.125.67.100: bytes=32 time=19ms TTL=243
Reply from 74.125.67.100: bytes=32 time=21ms TTL=243
Reply from 74.125.67.100: bytes=32 time=19ms TTL=243

Ping statistics for 74.125.67.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 27ms, Average = 21ms