ates

qwest has the 256/256 and the 1.5/896 services. But they use interleaving. Not good for gaming.

allright cool I'd rather keep the rwin big and have more re-transmissions Thanks for the help!!!

OK Van Buren I found that setting the RWIN to 29200 resulted in: WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 373.55Kb/s running 10s inbound test (server to client) . . . . . . 4.03Mb/s ------ Client System Details ------ OS data: Name = Windows XP, Architecture = x86, Version = 5.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2_04 ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Half Duplex mode No network congestion discovered. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 53.58 msec; the Packet size = 1460 Bytes; and There were 2 packets retransmitted, 37 duplicate acks received, and 38 SACK blocks received The connection was idle 0 seconds (0%) of the time This connection is receiver limited 70.62% of the time. Increasing the current receive buffer (28.0 KB) will improve performance This connection is network limited 29.32% of the time. Contact your local network administrator to report a network problem 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: OFF Packet size is preserved End-to-End Server IP addresses are preserved End-to-End Information: Network Address Translation (NAT) box is modifying the Client's IP address But my download speeds suffer bigtime with the lower rwin. Shouldn't it be quicker with less re-transmitted packets? Is having low re-transmission a trade off for higher d/l speeds? :::.. Download Stats ..::: Connection is:: 2791 Kbps about 2.8 Mbps (tested with 2992 KB) Download Speed is:: 341 KB/s Tested From:: http://www.testmy.net/ Test Time:: Sun Jan 30 2005 13:36:58 GMT-0800 (Pacific Standard Time) Bottom Line:: 50X faster than 56K 1MB download in 3 sec Validation Link:: https://testmy.net/id-NTY53EZHU thanks!

allright will do Thanks

WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 373.55Kb/s running 10s inbound test (server to client) . . . . . . 4.09Mb/s ------ Client System Details ------ OS data: Name = Windows XP, Architecture = x86, Version = 5.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2_04 ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Full Duplex mode No network congestion discovered. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 53.11 msec; the Packet size = 1460 Bytes; and There were 55 packets retransmitted, 236 duplicate acks received, and 259 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.24 seconds (2.4%) of the time This connection is receiver limited 4.44% of the time. Increasing the current receive buffer (62.0 KB) will improve performance This connection is network limited 95.51% of the time. Contact your local network administrator to report a network problem 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: OFF Packet size is preserved End-to-End Server IP addresses are preserved End-to-End

Could you help lower re-transmitted packets? 1.Winxp sp2 2.Comcast 4mb/384kbps 3.I use DRTCP http://ttester.broadbandreports.com/tweak/block:3b89c93?service=cable&speed=4000&os=winXP&via=normal 5. :::.. Download Stats ..::: Connection is:: 3798 Kbps about 3.8 Mbps (tested with 2992 KB) Download Speed is:: 464 KB/s Tested From:: http://www.testmy.net/ Test Time:: Sun Jan 30 2005 12:08:42 GMT-0800 (Pacific Standard Time) Bottom Line:: 68X faster than 56K 1MB download in 2.21 sec Validation Link:: https://testmy.net/id-BV5LGN63T Tracing route to testmy.net [67.19.36.6] over a maximum of 30 hops: 1 1 ms 2 ms 2 ms 192.168.1.1 2 * * * Request timed out. 3 15 ms 9 ms 10 ms 12.244.22.225 4 11 ms 11 ms 9 ms 12.244.64.154 5 14 ms 14 ms 14 ms 12.119.199.25 6 19 ms 16 ms 17 ms gbr1-p20.st6wa.ip.att.net [12.123.44.146] 7 29 ms 32 ms 30 ms tbr2-cl1.sffca.ip.att.net [12.122.12.113] 8 38 ms 42 ms 40 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26] 9 73 ms 75 ms 74 ms tbr1-cl2.dlstx.ip.att.net [12.122.10.49] 10 74 ms 74 ms 75 ms gar1-p360.dlrtx.ip.att.net [12.123.196.101] 11 75 ms 74 ms 74 ms 12.119.136.14 12 74 ms 76 ms 74 ms dist-vlan31.dsr3-2.dllstx3.theplanet.com [70.85. 127.30] 13 75 ms 73 ms 74 ms dist-vlan22.dsr1-2.dllstx2.theplanet.com [70.85. 127.76] 14 75 ms 74 ms 79 ms dsr2-2-v2.dllstx4.theplanet.com [12.96.160.40] 15 80 ms 94 ms 77 ms gig1-0-2.tp-car9-2.dllstx4.theplanet.com [67.18. 116.86] 16 83 ms 76 ms 78 ms 6.67-19-36.reverse.theplanet.com [67.19.36.6] Trace complete. WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 368.39Kb/s running 10s inbound test (server to client) . . . . . . 4.14Mb/s ------ Client System Details ------ OS data: Name = Windows XP, Architecture = x86, Version = 5.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2_04 ------ 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 = 54.73 msec; the Packet size = 1460 Bytes; and There were 37 packets retransmitted, 159 duplicate acks received, and 186 SACK blocks received The connection was idle 0 seconds (0%) of the time This connection is network limited 99.95% of the time. Contact your local network administrator to report a network problem 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: OFF Packet size is preserved End-to-End Server IP addresses are preserved End-to-End Thanks!