trogers

Carry out the download and upload speed tests in www.testmy.net and post your results. Carry out the TCP/IP Analyzer test at https://www.speedguide.net/analyzer.php and post your results. I can then provide you a ccs file to tweak.

Good morning, My last ccs file has worked for you. I use the following test results as a gauge. "There were 15 packets retransmitted, 120 duplicate acks received, and 126 SACK blocks received" Percentage of retransmitted. "The NDT server has a 101.0 KByte buffer which limits the throughput to 3.84 Mbps Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 2.38 Mbps The network based flow control limits the throughput to 2.44 Mbps" Matching your PC throughput limit with network based flow limit, both above your advertised speed of 1.5 Mbps. Cablenut has tweaked your comp to max efficiency. Some other factors are slowing you down. Could be your modem/router setup as you are getting timed out in the first 2 paths of your trace route test.

Your ISP's network is busy and the high throughput of my earlier ccs file is creating excessive packet losses. There were 10 packets retransmitted, 56 duplicate acks received, and 66 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.57 seconds (5.69%) of the time This connection is network limited 99.98% of the time. Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch Your PC/Workstation has a 125.0 KByte buffer which limits the throughput to 5.77 Mbps The network based flow control limits the throughput to 0.72 Mbps This css file will reduce throughput but still higher than your 1.5 Mbps. Check and see if it can reduce excessive packet losses.

Your present RWIN is set at 17424 and DefaultSendWindow is 16304, MTU 1492 Latency to test site is 609 ms. Your PC/Workstation has a 17.0 KByte buffer which limits the throughput to 0.21 Mbps The network based flow control limits the throughput to 0.14 Mbps. You are from overseas and speedtest results from USA websites may not be indicative of your comp's real performance due to 2 reasons: High latency (> 300 ms) High traffic (network based flow control limits the throughput to 0.14 Mbps) Please do some speedtest in your country's websites and note your results. Then use this ccs file and do the speedtest again to compare.

What are the speeds you pay your ISP for? Carry out this test and post your results: https://www.speedguide.net/analyzer.php

Check your network connection for problems thru this test and post your results (Statistics and last 2 paragraphs of More Details): http://nitro.ucsc.edu/ Then install this ccs file and retest network connection and post new results.

I guess there is a first and perhaps more exceptions in everything...LOL

If my ccs file makes little change, then I am puzzled. A few questions come to my mind: Are you using ADSL PPPoE? Or perhaps something else? Are you running some kind of speed software like DSL Speed (http://www.dsl-speed.org/)? Was Cablenut able to modify your registry values? Maybe you would like to try registry tweaks of TCP Optimizer (www.speedguide.net) first and then use Cablenut for fine tuning and saving the changes in a ccs file.

Web site of my ISP download test: http://www.hispeedworld.com/main/speedtest.html

Here is my ccs file with throughput set to 4 Mbps.

If your RWIN has been set to 12 kBtyes, then your download speed from Microsoft server reflected your setting.

Try my ccs file setting and download from Microsoft again. If you like to check download speed for a site with latency of 250 ms, here is the link to my ISP test site: http://wow.asianet.co.th/16M.inc

Since you started from scratch, you will also have to carry out all the performance tests in www.testmy.net, TCP/IP Analyzer and trace route and post your results. By the way, your dad didn't cut the power cable to your comp to 'make it better', did he? ...LOL

I do not know if you have had monitored consistently and drew the conclusion of having lower download speed to sites with less latency. You have to take into considerations traffic loads to those sites at different time of the day too. With higher traffic, the site server will allocate a smaller bandwidth to service you irrespective of your large bandwidth. The download speed you record is then a limit imposed by the site server, not your comp setting. This is why the use of a server from Microsoft (with very large bandwidth) can make a good benchmark for more precise measurements to compare tweak settings.

Tweaking seeks to achieve at least 90% speed of both download and upload speeds. Since the latency for sites that you surf to varies less than 50 ms, you have little worries about excessive loss packets (unless line quality is poor). You should maximise your throughput for both receive and send windows. Try this ccs file and test it on this site: http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=049C9DBE-3B8E-4F30-8245-9E368D3CDB5A&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f1%2f6%2f5%2f165b076b-aaa9-443d-84f0-73cf11fdcdf8%2fWindowsXP-KB835935-SP2-ENU.exe

1 * * * Request timed out. 2 * * * Request timed out. There is something wrong with your modem/router setup. You need to correct this before tweaking with Cablenut.

Try this ccs file.

Speed testing over the internet can give varied results due to factors which we have no control. Here is a link which I think give good advice in setting out a specific benchmark to gauge your comp's performance: http://www.askmarvin.ca/testing.html I have ask you to carry out the TCP/IP Analyzer test because your ccs file has left blanks some values. namely the RWIN and DefaultSendWindow values. By leaving these values blank will not reset them to default but may give you some unexpected results. From the test results above, your RWIN is set to 12 KByte, compared to XP's default vaue of 8 KByte. As to desired settings to control packet losses, retransmissions, and throughputs, it is like a balancing act and the final results depend much on where we most often surf to and the traffic conditions we likely will face. I found that in heavy traffic condition and high latency, I get better speeds having less packet losses and retransmission than to have higher throughput. In medium traffic, I can achieve better speed by accepting some packet losses and with have a larger throughput. I actually have 3 settings that I use when surfing the net depending on traffic conditions. Here is a link to another forum that I had posted: http://forums.speedguide.net/showthread.php?t=192650

Take note that the Cablenut adjuster for 98SE is different for WIN 2K and XP. I am not familiar with settings for 98SE. For assistance in cablenut settings for 98SE, go to this link http://www.j79zlr.com/cablenutME98.php

I cannot really give comments on the settings of your ccs file until I have performance test results and your advertised speeds. What are your advertised speed and are you using cable or DSL? Speed test reults in www.testmy.net Post test results of https://www.speedguide.net/analyzer.php http://nitro.ucsc.edu/ Post the results for Statistcs and the last two paragraphs of More Details. Examples: WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 455.87kB/s running 10s inbound test (server to client) . . . . . . 750.79kB/s ------ Client System Details ------ OS data: Name = Windows XP, Architecture = x86, Version = 5.1 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 = 243.9 msec; the Packet size = 1444 Bytes; and There were 31 packets retransmitted, 69 duplicate acks received, and 74 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.47 seconds (4.7%) of the time This connection is receiver limited 11.19% of the time. This connection is network limited 88.78% 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 Information: Network Middlebox is modifying MSS variable Server IP addresses are preserved End-to-End Client IP addresses are preserved End-to-End estimate = 0.68 based on packet size = 11Kbits, RTT = 243.9msec, and loss = 0.004418262 The theoretical network limit is 0.68 Mbps The NDT server has a 101.0 KByte buffer which limits the throughput to 3.23 Mbps Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 1.99 Mbps The network based flow control limits the throughput to 2.03 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'

DefaultReceiveWindow (or RWIN) setting affects the throughput limit of your comp and should be adjusted to suit your bandwidth and latency - not about distant or local sites. You may get the impression that there is some relationship. The real relationship is that your latency to local sites usually is less than 100 ms and latency to international sites can be 300 ms. You can see this by doing a tracert test. So a small (RWIN) will not affect speed to local sites but will slow download time for distance sites. As a rule of thumb, DefaultReceiveWindow(RWIN) = bandwidth x latency TcpWindowSize affects efficiency of your signal transmission. Too large will cause excessive packet losses and many retransmissions. You can experiment changing the values of these values and carry out a network diagnostic test to see results on throughput, speeds, packet losses at this site: http://nitro.ucsc.edu/

So sorry, I am not good with hardware configurations. Perhaps you can start a new topic and ask the more senior members.

Try this ccs file.

Then it is this router connection that is imposing a throughput limit of 0.44 Mbps. You need adjust your connection back to standard and retest your network. The ccs file has adjusted your throughput to more than 4 Mbps.

Try this ccs file. The test report shows 2 possible causes for your slow download speed: Information: Network Address Translation (NAT) box is modifying the Client's IP address Server says [***********] but Client says [***********] The network based flow control limits the throughput to 0.44 Mbps Are you using a proxy server?