Basically, I'm gonna post a bunch of info here and I want some people to give me some advice on what exactly to say to these thick-headed techs.
TRACERT :
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\adam>tracert http://www.yahoo.com
Tracing route to http://www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:
1 36 ms 33 ms 7 ms 10.0.99.1
2 * 41 ms 41 ms 66.186.180.209
3 62 ms 12 ms 13 ms 66.186.173.37
4 47 ms 63 ms 16 ms pwn-pi-mont-core.pwless.net [66.186.173.43]
5 33 ms 19 ms 60 ms pi-rtr-wt.mainewireless.net [64.89.247.242]
6 29 ms 17 ms 69 ms 64.89.249.97
7 43 ms 79 ms 18 ms 74.221.67.130
8 28 ms 22 ms 28 ms 74.221.67.134
9 29 ms 27 ms 48 ms 198.164.27.13
10 32 ms 69 ms 29 ms stjhnbsu22w-ge-15-1.aliant.net [142.166.211.145]
11 45 ms 40 ms 44 ms rtp629045rts [64.230.203.25]
12 43 ms 38 ms 41 ms core2-saintjohnnb_pos5-0.net.bell.ca [64.230.167
.73]
13 41 ms 39 ms 40 ms core2-saintjohnnb_pos0-0.net.bell.ca [64.230.167
.89]
14 40 ms 37 ms 44 ms bx4-montreal02_so-1-0-0.net.bell.ca [64.230.170.
178]
15 44 ms 61 ms 39 ms if-6-0-0.mcore4.mtt-montreal.teleglobe.net [216.
6.115.29]
16 101 ms 49 ms 46 ms pos-channel1.mcore3.nyy-newyork.teleglobe.net [2
16.6.81.17]
17 90 ms 90 ms 55 ms if-12-0-0-723.core4.aeq-ashburn.teleglobe.net [2
16.6.42.61]
18 57 ms 84 ms 53 ms ix-14-2.core4.aeq-ashburn.teleglobe.net [209.58.
27.54]
19 60 ms 65 ms 107 ms ge-3-1-0-p151.msr2.re1.yahoo.com [216.115.108.63
]
20 60 ms * 59 ms gi1-23.bas-a2.re3.yahoo.com [66.196.112.55]
21 47 ms 49 ms 47 ms f1.http://www.vip.re3.yahoo.com [69.147.114.210]
Trace complete.
C:\Documents and Settings\adam>
NDT :
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 597.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 243.51kb/s
------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_01
------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 193.61 msec; the Packet size = 1460 Bytes; and
There were 8 packets retransmitted, 52 duplicate acks received, and 38 SACK blocks received
The connection stalled 1 times due to packet loss
C2S throughput test: Packet queuing detected: 1.28%
S2C throughput test: Packet queuing detected: 11.12%
This connection is network limited 99.91% of the time.
Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is not behind a firewall. [Connection to the ephemeral port was successful]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End
Power Levels:
Downstream Channel
Lock Status Operational
Modulation 64QAM
Channel ID 0
Provisioned Rate 4096 kbps
Symbol Rate 5056.941 Ksym/sec
Downstream Power 10.5 dBmV
SNR 40.7 dB
Upstream Channel
Lock Status Operational
Modulation QPSK
Channel ID 2
Provisioned Rate 1024 kbps
Symbol Rate 2560 Ksym/sec
Upstream Power 52.0 dBmV
Speedtest:



