March 31, 2008 Update

I've not tried Comcast Modem for a few days and have not heard ANYTHING from Comcast - either the Corporate person nor the Illinos leadership team.

Last message was March 25, 2008 telling me the Ilinois team would reach out to me about my experience.

I realized that corporate did not say they would fix it, just that they would reach out.

So I sent an email asking about the status of my problem. Guess the response.

Here's a few speed tests.









And my favorite test - screen one:
=========================================
TCP/Web100 Network Diagnostic Tool v5.5.1
click START to begin
Connected to: miranda.ctd.anl.gov -- Using IPv4 address
Another client is currently being served, your test will begin within 90 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 517.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 333.06kb/s
The slowest link in the end-to-end path is a 10 Mbps Ethernet subnet
Information: Other network traffic is congesting the link
[S2C]: Packet queuing detected

click START to re-test
=========================================



And the statistics screen:
=========================================
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 517.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 333.06kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_03

------ Web100 Detailed Analysis ------
10 Mbps Ethernet 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 = 42.61 msec; the Packet size = 1380 Bytes; and
There were 5 packets retransmitted, 14 duplicate acks received, and 0 SACK blocks received
The connection stalled 1 times due to packet loss
The connection was idle 0.25 seconds (2.27%) of the time
C2S throughput test: Packet queuing detected: 0.92%
S2C throughput test: Packet queuing detected: 50.14%
This connection is sender limited 1.58% of the time.
This connection is network limited 98.42% of the time.

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 'miranda.ctd.anl.gov' is probably behind a firewall. [Connection to the ephemeral port failed]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End
=========================================


Latency looks good - I'm getting pings in the 20-40 for the most part but still losing packets - especially where local servers attached to Chicago servers.

I started writing this at 5:43 pm. I tried to get to my Yahoo mail account. The screen showed loading and still does. I hit reload twice and clicked the bookmark a second time.

Draft autosave had failed two or three times since I started this post.

So I'll go back to Xanadoo at 256k - it is plenty fast for me.

If my DVR would quit acting up I'd be even happier - it failed to record the race yesterday and last night I got the dreaded 100% full message when a recording was due to start. It's been 3 years I've been getting that message and two different DVRs. I figure that is probably how long it'll take to get my high speed account fixed.

So things have not changed.