adiace Posted February 3, 2006 CID Share Posted February 3, 2006 Hello first I'd like to say that I'm glad to be part of this forum and absolutely love this site. The reason I'm posting is because I've been having horrible download speeds lately, I even upgraded my package from 3/384 to 6/800 but no change in speeds, still really bad. Here are my test results (highest download speed i've gotten today): :::.. Download Stats ..::: Connection is:: 939 Kbps about 0.9 Mbps (tested with 1496 kB) Download Speed is:: 115 kB/s Tested From:: https://testmy.net (server2) Test Time:: Thu Feb 2 23:47:54 PST 2006 Bottom Line:: 17X faster than 56K 1MB download in 8.9 sec Diagnosis: May need help : running at only 31.92 % of your hosts average (rogers.com) Validation Link:: https://testmy.net/stats/id-JYHP57O6W ------------------------------------------------------------------------------------------ TCP options string = 020405b401010402 MTU = 1500 MTU is fully optimized for broadband. MSS = 1460 Maximum useful data in each packet = 1460, which equals MSS. Default Receive Window (RWIN) = 17520 RWIN Scaling (RFC1323) = 0 bits Unscaled Receive Window = 17520 RWIN is a multiple of MSS Other values for RWIN that might work well with your current MTU/MSS: 513920 (MSS x 44 * scale factor of 256960 (MSS x 44 * scale factor of 4) 128480 (MSS x 44 * scale factor of 2) 64240 (MSS x 44) bandwidth * delay product (Note this is not a speed test): Your RcvWindow limits you to: 700.8 kbps (87.6 KBytes/s) @ 200ms Your RcvWindow limits you to: 280.32 kbps (35.04 KBytes/s) @ 500ms Consider increasing your RWIN value to optimize TCP/IP for broadband. MTU Discovery (RFC1191) = ON Time to live left = 120 hops TTL value is ok. Timestamps (RFC1323) = OFF Selective Acknowledgements (RFC2018) = ON IP type of service field (RFC1349) = 00000000 (0) ---------------------------------------------------------------------------------------------- TCP/Web100 Network Diagnostic Tool v5.3.3d click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 724.19Kb/s running 10s inbound test (server to client) . . . . . . 308.00kb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link Information: The receive buffer should be 56.46 Kbytes to maximize throughput Any help would be greatly appreciated, thanks! Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Hi, Welcome to this forum. Try the ccs file 1500-128480-64240.ccs that I had loaded in this thread: http://www.testmy.net/forum/index.php?topic=11588.0 Then retest at this link and post the results of STATISTICS and last 2 paragraphs of MORE DETAILS. Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Link to test site: http://nitro.ucsc.edu/ Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 This is using the ccs file you suggested: TCP/Web100 Network Diagnostic Tool v5.3.3d click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 830.31kB/s running 10s inbound test (server to client) . . . . . . 1.18Mb/s Your PC is connected to a Cable/DSL modem ---------------------------------------------------------------------- WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 830.31kB/s running 10s inbound test (server to client) . . . . . . 1.18Mb/s ------ Client System Details ------ OS data: Name = Windows 2000, Architecture = x86, Version = 5.0 Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06 ------ 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 = 160.54 msec; the Packet size = 1460 Bytes; and There were 6 packets retransmitted, 208 duplicate acks received, and 106 SACK blocks received The connection was idle 0 seconds (0%) of the time This connection is receiver limited 9.96% of the time. This connection is network limited 90.0% 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: 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 Server says [24.42.42.218] but Client says [192.168.1.100] -------------------------------------------------------------- The theoretical network limit is 1.12 Mbps The NDT server has a 101.0 KByte buffer which limits the throughput to 4.91 Mbps Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 3.05 Mbps The network based flow control limits the throughput to 3.12 Mbps Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is '10 Gig', Server Acks report link is 'Ethernet' Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Your orignal RWIN was set at - Default Receive Window (RWIN) = 17520 The ccs file has set RWIN setting of 128480 and it is still too small for you: PC throughput limit 3+ Mpbs and Network throughput also 3+ Mbps. Let's double the RWIN. Try this ccs file. Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 Once I restart with the new settings, should I run the same test again and post results? Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Yes. I am try to balance your PC throughput limit with your Network throughput limit and making sure both are above 6 Mbps. Also keeping an eye on excess packet loss. Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 New results: TCP/Web100 Network Diagnostic Tool v5.3.3d click START to begin Another client is currently being served, your test will begin within 45 seconds Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 828.57Kb/s running 10s inbound test (server to client) . . . . . . 720.86kb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link --------------------------------------------- WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 831.79Kb/s running 10s inbound test (server to client) . . . . . . 771.01kb/s ------ Client System Details ------ OS data: Name = Windows 2000, Architecture = x86, Version = 5.0 Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06 ------ 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 = 148.61 msec; the Packet size = 1460 Bytes; and There were 2 packets retransmitted, 88 duplicate acks received, and 24 SACK blocks received The connection was idle 0 seconds (0%) of the time This connection is network limited 99.97% 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: 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 Server says [24.42.42.218] but Client says [192.168.1.100] -------------------------------------------------- The theoretical network limit is 1.35 Mbps The NDT server has a 101.0 KByte buffer which limits the throughput to 5.30 Mbps Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 3.29 Mbps The network based flow control limits the throughput to 1.19 Mbps Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is '10 Gig', Server Acks report link is 'T1' Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Something is not right! Your RWIN setting for both ccs files have not changed. "Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 3.05 Mbps" "Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 3.29 Mbps" Try this test and post results: https://www.speedguide.net/analyzer.php Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 TCP options string = 020405b40103030001010402 MTU = 1500 MTU is fully optimized for broadband. MSS = 1460 Maximum useful data in each packet = 1460, which equals MSS. Default TCP Receive Window (RWIN) = 64240 RWIN Scaling (RFC1323) = 0 bits Unscaled TCP Receive Window = 64240 RWIN is a multiple of MSS Other values for RWIN that might work well with your current MTU/MSS: 513920 (MSS x 44 * scale factor of 256960 (MSS x 44 * scale factor of 4) 128480 (MSS x 44 * scale factor of 2) bandwidth * delay product (Note this is not a speed test): Your TCP Window limits you to: 2569.6 kbps (321.2 KBytes/s) @ 200ms Your TCP Window limits you to: 1027.84 kbps (128.48 KBytes/s) @ 500ms MTU Discovery (RFC1191) = ON Time to live left = 56 hops TTL value is ok. Timestamps (RFC1323) = OFF Selective Acknowledgements (RFC2018) = ON IP type of service field (RFC1349) = 00000000 (0) Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Load the 1500-128480-64240 ccs file into your Cablenut Adjuster, save to resgistry and then reboot your comp. Then test and post results with: https://www.speedguide.net/analyzer.php http://nitro.ucsc.edu/ Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted February 3, 2006 CID Share Posted February 3, 2006 Try this and post results: http://www.testmy.net/forum/index.php?action=dlattach;topic=6415.0;attach=9950 Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 Results with the 1500-128..file: TCP options string = 020405b40103030001010402 MTU = 1500 MTU is fully optimized for broadband. MSS = 1460 Maximum useful data in each packet = 1460, which equals MSS. Default TCP Receive Window (RWIN) = 64240 RWIN Scaling (RFC1323) = 0 bits Unscaled TCP Receive Window = 64240 RWIN is a multiple of MSS Other values for RWIN that might work well with your current MTU/MSS: 513920 (MSS x 44 * scale factor of 256960 (MSS x 44 * scale factor of 4) 128480 (MSS x 44 * scale factor of 2) bandwidth * delay product (Note this is not a speed test): Your TCP Window limits you to: 2569.6 kbps (321.2 KBytes/s) @ 200ms Your TCP Window limits you to: 1027.84 kbps (128.48 KBytes/s) @ 500ms MTU Discovery (RFC1191) = ON Time to live left = 56 hops TTL value is ok. Timestamps (RFC1323) = OFF Selective Acknowledgements (RFC2018) = ON IP type of service field (RFC1349) = 00000000 (0) -------------------------- TCP/Web100 Network Diagnostic Tool v5.3.3d click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 818.79Kb/s running 10s inbound test (server to client) . . . . . . 508.17kb/s Your PC is connected to a Cable/DSL modem Information: Other network traffic is congesting the link WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 818.79Kb/s running 10s inbound test (server to client) . . . . . . 508.17kb/s ------ Client System Details ------ OS data: Name = Windows 2000, Architecture = x86, Version = 5.0 Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06 ------ 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 = 155.62 msec; the Packet size = 1460 Bytes; and There were 8 packets retransmitted, 81 duplicate acks received, and 48 SACK blocks received The connection was idle 0 seconds (0%) of the time This connection is network limited 99.97% 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: 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 Server says [24.42.x.x] but Client says [192.168.1.100] The theoretical network limit is 0.61 Mbps The NDT server has a 101.0 KByte buffer which limits the throughput to 5.07 Mbps Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 3.14 Mbps The network based flow control limits the throughput to 0.71 Mbps Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is '10 Gig', Server Acks report link is 'T1' ----------------------------------- The current date is: Fri 02/03/2006 The current time is: 0:54:50.39 Microsoft Windows 2000 [Version 5.00.2195] Pinging testmy.net [67.18.179.85] with 32 bytes of data: Reply from 67.18.179.85: bytes=32 time=60ms TTL=43 Reply from 67.18.179.85: bytes=32 time=70ms TTL=43 Reply from 67.18.179.85: bytes=32 time=81ms TTL=43 Reply from 67.18.179.85: bytes=32 time=70ms TTL=43 Reply from 67.18.179.85: bytes=32 time=70ms TTL=43 Reply from 67.18.179.85: bytes=32 time=70ms TTL=43 Reply from 67.18.179.85: bytes=32 time=90ms TTL=43 Reply from 67.18.179.85: bytes=32 time=120ms TTL=43 Reply from 67.18.179.85: bytes=32 time=110ms TTL=43 Reply from 67.18.179.85: bytes=32 time=60ms TTL=43 Reply from 67.18.179.85: bytes=32 time=60ms TTL=43 Reply from 67.18.179.85: bytes=32 time=61ms TTL=43 Ping statistics for 67.18.179.85: Packets: Sent = 12, Received = 12, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 60ms, Maximum = 120ms, Average = 76ms Ping Complete. Tracing route to testmy.net [67.18.179.85] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85] 2 30 ms 30 ms 20 ms 10.91.156.1 3 20 ms 10 ms 10 ms gw03.ym.phub.net.cable.rogers.com [66.185.90.17] 4 20 ms 20 ms 60 ms gw01.ym.phub.net.cable.rogers.com [66.185.93.9] 5 20 ms 20 ms 30 ms gw02.ym.phub.net.cable.rogers.com [66.185.80.214] 6 30 ms 20 ms 50 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.49] 7 30 ms 50 ms 40 ms igw01.vaash.phub.net.cable.rogers.com [66.185.80.190] 8 40 ms 40 ms 30 ms 216.200.56.1.has.no.reverse [216.200.56.1] 9 30 ms 60 ms 41 ms so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118] 10 60 ms 40 ms 40 ms so-4-0-0.mpr2.iad1.us.above.net [64.125.29.133] 11 20 ms 40 ms 30 ms so-1-0-0.cr2.dca2.us.above.net [64.125.28.129] 12 60 ms 81 ms 60 ms so-6-0-0.cr2.dfw2.us.above.net [64.125.28.70] 13 70 ms 60 ms 50 ms 216.200.6.237.theplanet.com [216.200.6.237] 14 60 ms 270 ms 211 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30] 15 80 ms 60 ms 90 ms vl42.dsr02.dllstx4.theplanet.com [70.85.127.91] 16 50 ms 70 ms 80 ms gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.69] 17 70 ms 80 ms 70 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85] Trace complete. <edit> hid IP<br>-FE Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 You still got "Default TCP Receive Window (RWIN) = 64240 RWIN Scaling (RFC1323) = 0 bits Unscaled TCP Receive Window = 64240" If my ccs file made changes to your registry you should get this: Default TCP Receive Window (RWIN) = 128480 RWIN Scaling (RFC1323) = 0 bits Unscaled TCP Receive Window = 64240 Are you running some security software protecting against registry changes? Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 Nothing that I know is running that would protect against registry changes. When I first posted I got these results: Default Receive Window (RWIN) = 17520 RWIN Scaling (RFC1323) = 0 bits Unscaled Receive Window = 17520 and now they are (with using the ccs files) Default TCP Receive Window (RWIN) = 64240 RWIN Scaling (RFC1323) = 0 bits Unscaled TCP Receive Window = 64240 is there any way I can check if the values really are in the registry? Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Click to open the Cablenut Adjuster and it will display the existing settings in your registry. In the first item on top left, it should read DefaultReceiveWindow - 128480 If not, change the value to 128480, save to registry exit the Cablenut Adjuster and then reopen Cablenut Adjuster to check if values have bben changed. If yes, reboot comp. Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 Ok well the DefaultReceiveWindow was 128480, but just to see if it makes any difference to the registry once I reboot I changed TcpWindowSize, GlobalMaxTcpWindowSize and DefaultSendWindow to 128480 and this is the result I got now: TCP options string = 020405b40103030101010402 MTU = 1500 MTU is fully optimized for broadband. MSS = 1460 Maximum useful data in each packet = 1460, which equals MSS. Default TCP Receive Window (RWIN) = 128480 RWIN Scaling (RFC1323) = 1 bits (scale factor of 2) Unscaled TCP Receive Window = 64240 RWIN is a multiple of MSS Other values for RWIN that might work well with your current MTU/MSS: 513920 (MSS x 44 * scale factor of 256960 (MSS x 44 * scale factor of 4) 64240 (MSS x 44) bandwidth * delay product (Note this is not a speed test): Your TCP Window limits you to: 5139.2 Kbps (642.4 KBytes/s) @ 200ms Your TCP Window limits you to: 2055.68 Kbps (256.96 KBytes/s) @ 500ms MTU Discovery (RFC1191) = ON Time to live left = 56 hops TTL value is ok. Timestamps (RFC1323) = OFF Selective Acknowledgements (RFC2018) = ON IP type of service field (RFC1349) = 00000000 (0) Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Change the other values back to 64240. Just let RWIN remain at 128480. Reboot comp and do this test again: http://nitro.ucsc.edu/ And also the speedtest for both down and up using the LARGEST file 2992 kB Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 :::.. Download Stats ..::: Connection is:: 1790 Kbps about 1.8 Mbps (tested with 2992 kB) Download Speed is:: 219 kB/s Tested From:: https://testmy.net (server1) Test Time:: Fri Feb 3 01:30:49 PST 2006 Bottom Line:: 32X faster than 56K 1MB download in 4.68 sec Diagnosis: May need help : running at only 60.88 % of your hosts average (rogers.com) Validation Link:: https://testmy.net/stats/id-PZ7KE8H24 :::.. Upload Stats ..::: Connection is:: 757 Kbps about 0.8 Mbps (tested with 2992 kB) Upload Speed is:: 92 kB/s Tested From:: https://testmy.net (server2) Test Time:: Fri Feb 3 01:31:58 PST 2006 Bottom Line:: 14X faster than 56K 1MB upload in 11.13 sec Diagnosis: Awesome! 20% + : 116.29 % faster than the average for host (rogers.com) Validation Link:: https://testmy.net/stats/id-3KQPFW8MN --------------------------------------------------- WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 829.48Kb/s running 10s inbound test (server to client) . . . . . . 1.30Mb/s ------ Client System Details ------ OS data: Name = Windows 2000, Architecture = x86, Version = 5.0 Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06 ------ 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 = 133.07 msec; the Packet size = 1460 Bytes; and There were 5 packets retransmitted, 197 duplicate acks received, and 89 SACK blocks received The connection was idle 0 seconds (0%) of the time This connection is network limited 99.97% 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: 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 Server says [24.42.x.x] but Client says [192.168.1.100] The theoretical network limit is 1.61 Mbps The NDT server has a 101.0 KByte buffer which limits the throughput to 5.92 Mbps Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 3.68 Mbps The network based flow control limits the throughput to 2.92 Mbps Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is '10 Gig', Server Acks report link is 'Ethernet' <edit>hid IP<br>-FE Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 Result from the Analyzer test: TCP options string = 020405b40103030001010402 MTU = 1500 MTU is fully optimized for broadband. MSS = 1460 Maximum useful data in each packet = 1460, which equals MSS. Default TCP Receive Window (RWIN) = 64240 RWIN Scaling (RFC1323) = 0 bits Unscaled TCP Receive Window = 64240 RWIN is a multiple of MSS Other values for RWIN that might work well with your current MTU/MSS: 513920 (MSS x 44 * scale factor of 256960 (MSS x 44 * scale factor of 4) 128480 (MSS x 44 * scale factor of 2) bandwidth * delay product (Note this is not a speed test): Your TCP Window limits you to: 2569.6 kbps (321.2 KBytes/s) @ 200ms Your TCP Window limits you to: 1027.84 kbps (128.48 KBytes/s) @ 500ms MTU Discovery (RFC1191) = ON Time to live left = 56 hops TTL value is ok. Timestamps (RFC1323) = OFF Selective Acknowledgements (RFC2018) = ON IP type of service field (RFC1349) = 00000000 (0) Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Still the same setting of RWIN 64240 and that is why "62.0 KByte buffer which limits the throughput to 3.68 Mbps" With RWIN at 128480, Window Scaling should be turned on In Cablenut Adjuster, the 4th item from top right Tcp13230pts - 1 If Cablenut cannot make adjustments that will retains in your registry, please go to this site and download the TCP Optimizer v203 and I will help you make adjustments with it: www.speedguide.net RFC 1323 Window Scaling: OFF Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 3.68 Mbps The network based flow control limits the throughput to 2.92 Mbps Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted February 3, 2006 CID Share Posted February 3, 2006 Could the router possibly disable window scaling on throughput? Quote Link to comment Share on other sites More sharing options...
adiace Posted February 3, 2006 Author CID Share Posted February 3, 2006 The settings are just like in the ccs file and yep the Tcp13230pts = "1" in Cablenut, I guess I will give TCP Optimizer a go. Quote Link to comment Share on other sites More sharing options...
trogers Posted February 3, 2006 CID Share Posted February 3, 2006 Hi FallowEarth, I am not good with hardware. Perhaps you can work with adiace to see if that is the problem. Quote Link to comment Share on other sites More sharing options...
FallowEarth Posted February 3, 2006 CID Share Posted February 3, 2006 adiace, are you connecting to a router? is it wireless? have you tried making a direct connection to the modem with your PC, resetting modem and PC, and trying your speed test again? Also, if you could provide a screenshot of your cablenut settings? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.