On Wed, 11 Jun 2008 17:59:35 -0500, "Dallas"
wrote:


"Bob Shuman" wrote in message
What is the round trip latency you measured to the test site being used
(lower is better)?

Pinging 2wire.com [216.52.29.100] with 32 bytes of data:
Reply from 216.52.29.100: bytes=32 time=71ms TTL=243
Reply from 216.52.29.100: bytes=32 time=51ms TTL=243
Reply from 216.52.29.100: bytes=32 time=51ms TTL=243
Reply from 216.52.29.100: bytes=32 time=50ms TTL=243
Ping statistics for 216.52.29.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 71ms, Average = 55ms

-- Pings look pretty good... (FYI 2Wire.com is in San Jose, CA)


What is your TCP window set to in the registry on your computer (should be
#FFFF to maximize throughput)?

Hum.. I don't know.. and don't know how to check.. how do I do that?


FYI, as in the reply to Rich Webb, here are my DSLreports.com tweak test
results:

http://img.photobucket.com/albums/v1...estresults.jpg


They show a transfer rate of 2021 Kbps which seems miserable considering I'm
expecting 5000ish.

One tool that may give a hint of what's happening is the "DU Meter"
which gives you a graph of transfer speed vs time (and does a much
better job of it than the Windows built-in monitor). If you're getting
a full-speed connection then the graph will show a steady rate, but if
you're suffering from variable choke-points between you and the remote
machine it's pretty obvious. http://www.dumeter.com/

--
Rich Webb Norfolk, VA