UNC Bld-201 NDT server
via http://ndt.itcc.unc.edu:7123/
TCP/Web100 Network Diagnostic Tool v5.2.1e
running 10s outbound test (client to server) . . . . . 375.97Kb/s
running 10s inbound test (server to client) . . . . . . 3.50Mb/s
running 10s outbound test (client to server) . . . . . 375.97Kb/s
running 10s inbound test (server to client) . . . . . . 3.74Mb/s
For the record, abridged results of two tests of our Comcast throughput on a Monday evening, thanks to the University of North Carolina.
running 10s outbound test (client to server) . . . . . 378.21Kb/s
running 10s inbound test (server to client) . . . . . . 11.23Mb/s
running 10s outbound test (client to server) . . . . . 375.97Kb/s
running 10s inbound test (server to client) . . . . . . 10.90Mb/s
Alright, that's more like it. The August test was suspect, as our wireless system was acting up. This one is a wired connection.
running 10s outbound test (client-to-server [C2S]) . . . . . 5.77Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 266.37kb/s
Reset cable modem and router. Presto!
running 10s outbound test (client-to-server [C2S]) . . . . . 5.77Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 10.93Mb/s
Last night and this afternoon, the outbound test came back at 0kb/s. A call to Comcast suggests a problem with the line or modem and a tech is scheduled. Oddly, the next test comes up with this:
running 10s outbound test (client-to-server [C2S]) . . . . . 1.29Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 12.25Mb/s
...but it still makes mention of packet queuing. We'll see how the next couple of days go, but for now at least we're not virtually dead in the water.
running 10s outbound test (client-to-server [C2S]) . . . . . 5.13Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 193.55kb/s
The slowest link in the end-to-end path is a a 622 Mbps OC-12 subnet
Information: Other network traffic is congesting the link
[S2C]: Packet queuing detected
*modem reboot*
running 10s outbound test (client-to-server [C2S]) . . . . . 5.76Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 12.65Mb/s
The slowest link in the end-to-end path is a a 622 Mbps OC-12 subnet
[S2C]: Packet queuing detected
running 10s outbound test (client to server) . . . . . 369.85Kb/s
running 10s inbound test (server to client) . . . . . . 98.89kb/s
running 10s outbound test (client to server) . . . . . 376.34Kb/s
running 10s inbound test (server to client) . . . . . . 137.90kb/s
Need some work on that download rate, clearly.