trogers

Also, you have to reconfig your modem to 'auto' duplex sensing - "Alarm: Duplex mismatch condition exists: Host set to Full and Switch set to Half duplex" This is the cause of your 'request times out' in the 1st hop?

Try this ccs file.

You can choose to use any of these 2 ccs files: 32120-32120 this is good for RTT = 500-700 ms 32120-16060 this is good for RTT = 400-500 ms RTT means round trip time. It is the time for a signal to leave your computer until the info from the website reach you. Cablenut settings in these 2 files makes your computer optimum. You have to contact your ISP to ask why upload speed is too bad. The problem is not with your computer. It is with the network of the ISP.

Speed and also the Big test. I have to use the info to design the ccs file for you.

Try this ccs file. Do your speed test and then this link again: http://farnsworth.uhnet.net:7123/

Go to this site. A smaller window will appear . Click 'START' button and the test will begin. When test is completed, 2 buttons appear at the bottom of the small window. Click "STATISTICS' and a report will come out. Copy report and save to Wordpad. Click 'MORE DETAILS' and another report will come out. Copy report and save with first report inside Wordpad. Then copy the report in Wordpad and post to this forum.

Do this test for me and post results of STATISTICS abd MORE DETAILS: http://farnsworth.uhnet.net:7123/

I do not think your line is 256/256 Kbps as you can test faster than that. Maybe it is 512/512 like your friend. Check the two cable connections in the white box to see if they are ok. Also make sure there is no electrical devices close to the white box. If yes, move the electrical devices a few feet away from the white box. Try this ccs file.

When you have solved your problem, say "Hi" to mccoffee for me...LOL

Do some diagnostic check on your NIC first before replacing it. Refer to the user manual or manufacurer's webite. Or send it to a tech to check for you. The problem may not be in the hardware but in the settings.

yes

RTT = 50.75msec Your fast connection has this latency. Your slow connection has this: RTT = 2023.33msec If you are using the same cable connection (modem/router) to test, then the problem may lie in the NIC inside the slow laptop.

Your have a serious problem in your connection. Signals are facing huge latency and this is causing the slowdown. "Web100 reports the Round trip time = 2023.33 msec; the Packet size = 1460 Bytes; and No packet loss was observed. This connection is receiver limited 37.47% of the time. Increasing the the client's receive buffer (196.0 KB) will improve performance This connection is network limited 62.51% of the time." RTT = 2023.33msec This high latency is limiting your throughput to only 0.75 Mbps. Check the condition of your connection; cables, loose plug/socket, modem/router, any nearby electrcial devices emitting electromagnetic interference, etc...

Post up load speed too. Test here and post: https://www.speedguide.net/analyzer.php

Give us the speeds you pay your ISP to provide you. Do a tracert test to check your signals. Go to this link to check your preset setting: https://www.speedguide.net/analyzer.php We need the reports and info in order to help you.

Need to know your present MTU and RWIN setting. Do this test and post results: https://www.speedguide.net/analyzer.php

For what MTU and latency?

Do this network diagnostic check. Post the report sections STATISTICS and MORE DETAILS: http://nitro.ucsc.edu/

When upload speed is slow it can mean one of 2 things: window registry for Tcp Stack is not config right, or trouble in the modem. We have tweaked your window registry and the problem still exists.Then your modem may be the problem. I cannot do a diagnostic check on your modem for you but here is a guide on how to check your modem: http://homepage.ntlworld.com/robin.d.h.walker/cmtips/signal.html

Now I understand why you have high latency. You need to use this ccs file instead.

Did you test speed with anti-virus software turned on? If yes, turn it off and then test again.

Yes...if you frequently download from overseas, set RWIN to 128480. If you can solve the slowdown problem and get download speed of 850-900 Kbps, reset RWIN back to 64240.

It is "netstat -b" and not "netstat-b". There is a space before '-b'.

RWIN set at 64240 for your 1 Mbps throughput is ok if you are surfing within your country as latency is 100-150 ms range. RWIN set at 128480 will be good for you if you surf to overseas as your latency will go 200-300 ms range. But remember, higher latency and higher RWIN gives higher packet losses. My suspicion on the cause of your slowdown is either line quality or hitches in your ISP's network. As FallowEarth has guided you to scan for possible spyware and none was found, i would conclude that your comp is clean. But one unusual point was raised by you: difficulty to get into DOS and your inability to do the "netstat -b" command. Something may still be hidden in your comp? The Forum section on Security may be a good place to seek assistance in this area.

This is from webROCKET (a speed software) and it talks about the different settings, pay attention to the RWIN setting information. ""What is MTU? When you download a file, it is broken into many packets of data before it is sent over the World Wide Web to your computer (where it is then reassembled). The size of these packets is called your MTU value, or the Maximum Transfer Unit. Setting your computer's MTU value too low would make downloading less efficient. This is because a greater percentage of the packet is taken up by a packet header. Each data packet header contains a variety of information about the packet itself, such as source, size, ID, and destination. However, setting the MTU too high can also decrease efficiency. Other computers on the Internet might not be able to handle MTU values of a certain size. If you set your computer's MTU value too high, some computers along the delivery path would be required to break these packets into smaller pieces before accepting them and passing them to the next computer. This "Stop. Break. Go." processing of packets can dramatically slow down data transfers. It is usually best to select the settings Ascentive has researched by using the QuickOptimization panel in webROCKET. However, expert users and experienced network engineers may make their own adjustments to the MTU value by using the Detailed Optimization panel in webROCKET. How should RWIN be set? RWIN stands for Receive WINdow. This "window" is a buffer, or holding area, that your computer uses to sort the packets of data received when something is downloaded. Each packet of data that your computer receives needs to be accepted in a certain order before the file you are downloading can be "put back together" on your end. Although these packets of data are sent out in the correct order, sometimes the packets can take different paths and arrive out of order, or get lost altogether. When the next packet of data your computer receives is not the right one (according to its order), your computer has to stop and send a request back to ask for the missing packet. This request takes time. However, because of the RWIN buffer, your computer downloads the data packets to a storage area first. This storage area can hold more than one packet at a time (usually four to six). If the data is received out of order, your computer will continue to download the data packets to this holding area, waiting for the packet that is supposed to come next. Your computer will only have to send a request for the missing packet if your RWIN fills before the needed data packet arrives. It takes significantly less time for the data packets to pass from your RWIN buffer to your application's memory than it takes for your computer to make a request for a needed data packet. However, setting your RWIN size too large would result in a slower download process. Your computer's RWIN buffer would have to fill completely before it realized that a packet of data was missing (rather than just out of order) and request a retransmission of the packet. Custom RWIN settings may have an adverse effect and should only be used by expert users and network engineers. How should TTL be set? When you download a file, it is broken into many packets of data before it is sent to your computer (where it is then reassembled). Not all of these data packets use the same path along the Internet to your computer. Some packets may not arrive in a reasonable length of time and some may even become lost. An arrangement of incorrect routing tables could cause a packet to loop in the network endlessly and congest the network. Because of this, packets of data are set with an "expiration date" and will be discarded after a certain number of hops (a hop occurs every time a packet is sent from one computer to the next along a path). TTL stands for Time To Live. After a packet is discarded, your computer will have to request the missing packet(s) again from the originator. Setting your TTL too low would make it impossible for some packets to reach their destination. Setting it too high would cause the network to become congested. This value is set automatically by the QuickOptimization feature, although expert users and network engineers are free to make their own adjustments on the Detailed Optimization tab. How should PMTU be set? The PMTU settings can be selected, however they are rarely used. Black Hole Detection detects troublesome routers and attempts to choose another one -- so if you are having connection trouble, you should select this PMTU option. Automatic Discovery means that your system will attempt to come to an agreement with the server or router, regarding the packet size. However, this agreement may not always be the optimal size. We recommend using the QuickOptimization settings in webROCKET. However, expert users and network engineers may make their own adjustments on the Detailed Optimization tab.""