New computer with w7. Problems downloading from internet. Download starts ok and runs at full speed for a few meg and then slows to a halt. then might start again after a few minutes and then usually stops again. Sometimes data seems to download in short bursts with gaps in between.
Short speed test is good.
Can download same file with older xp machine with no trouble.
Both machines on same network with same antivirus
Any clues?
john
p s Same happens with different browsers. No problem with torrents
Disconnect the PC from the network, and then try downloading. Update your router's firmware too. You can also try disabling the antivirus on that PC temporarily.
I tried downloading a large file with firefox and the download failed after about 5 minutes.
I then tried downloading the same file using Orbit Downloader. The download stopped after about 5 minutes and then after a few more minutes the download continued. This stopping and starting happened a few more times until the download was complete.
I have now downloaded freedownloadmanager so will try with that and see what happens.
I would recommend using the Windows 7 tweaks listed at: www.speedguide.net
If you use the "cmd" windows be sure to "Run As Administrator" by right-clicking on it. You can access the command or cmd window by typing "cmd" in the search bar at the Start Orb.
I have personally used these tweaks and can vouch for the improvements I have noticed. Faster browsing, snappier internet response and downloads. They won't increase the download speed but allow downloads to maintain a steady speed with not many fluctuations. I highly recommend these tweaks.
Here I have listed them from their page for the tweaks:
Windows Vista introduces a number of new features to the TCP/IP stack, including CTCP, and TCP Window Auto-Tuning. This new implementation works much better by default than previous Windows versions with broadband internet connections, and is able to adjust the RWIN value on the fly, depending on the BDP (bandwidth-delay product). This, however, introduces some problems with older routers and restricts the user from tweaking some of the TCP/IP parameters. Still, there is always some room for improvement, and this article explains the known tweakable TCP/IP parameters.
To enter some of the commands below, you will need to run "elevated" command prompt. To do so, click the Start icon > Run > type: cmd , then click CTRL+SHIFT+ENTER. Alternatively, you can navigate to Start > All Programs > Accessories > right-click Command Prompt and choose "Run as Administrator".
Check the TCP/IP state
To check the current status of the Vista TCP/IP tweakable parameters, in elevated command prompt type the following command:
netsh int tcp show global
You will be presented with something like the following:
The settings, as well as their default and recommended state are explained below. The two most important tweakable parameters are "Auto-Tuning Level" and "Congestion Control Provider".
When checking the TCP state with the "netsh int tcp show global" command, it is also possible to see the following message below all those parameters:
** The above autotuninglevel setting is the result of Windows Scaling heuristics overriding any local/policy configuration on at least one profile.
It is displayed when the "Receive Window Auto-Tuning Level" is not explicitly set, or if the system deemed it necessary to make a change because of user prompted "repairing" of your network connection, for example.
Disable Windows Scaling heuristics
Windows Vista/7 has the ability to automatically change its own TCP Window auto-tuning behavior to a more conservative state regardless of any user settings. It is possible for Windows to override the autotuninlevel even after an user sets their custom TCP auto-tuning level. When that behavior occurs, the "netsh int tcp show global" command displays the following message:
** The above autotuninglevel setting is the result of Windows Scaling heuristics
overriding any local/policy configuration on at least one profile.
To prevent that behavior and enforce any user-set TCP Window auto-tunning level, you should execute the following command:
netsh int tcp set heuristics disabled
possible settings are: disabled,enabled,default (sets to the Windows default state)
recommended: disabled (to retain user-set auto-tuning level)
Note this should be executed in elevated command prompt (with admin priviledges) before setting the autotuninlevel in next section. If the command is accepted by the OS you will see an "Ok." on a new line.
The corresponding Registry value (not necessary to edit if setting via netsh) is located in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters EnableWsd=0 (default: 1, recommended: 0)
TCP Auto-Tuning
To turn off the default RWIN auto tuning behavior, (in elevated command prompt) type:
netsh int tcp set global autotuninglevel=disabled
The default auto-tuning level is "normal", and the possible settings for the above command are:
disabled: uses a fixed value for the tcp receive window. Limits it to 64KB (limited at 65535). highlyrestricted: allows the receive window to grow beyond its default value, very conservatively restricted: somewhat restricted growth of the tcp receive window beyond its default value normal: default value, allows the receive window to grow to accommodate most conditions experimental: allows the receive window to grow to accommodate extreme scenarios (not recommended, it can degrade performance in common scenarios, only intended for research purposes. It enables RWIN values of over 16 MB)
Our recommendation: normal (unless you're experiencing problems).
If you're experiencing problems with your NATrouter or SPIfirewall, try the "restricted", "highlyrestricted", or even "disabled" state. Notes:
- Reportedly, some older residential NAT routers with a SPIfirewall may have problems with enabled tcp auto-tuning in it's "normal" state, resulting in slow speeds, packet loss, reduced network performance in general.
- auto-tuning also causes problems with really old routers that do not support TCP Windows scaling. See MSKB 935400
- netsh set commands take effect immediately after executing, there is no need to reboot.
- sometimes when using "normal" mode and long lasting connections (p2p software / torrents), tcp windows can get very large and consume too much resources, if you're experiencing problems try a more conservative (restricted) setting.
If you're experiencing problems with Auto-Tuning, see also: MS KB 835400 - email issues MS KB 934430 - network connectivity behind firewall problems MS KB 940646 - 3G WWAN throughput issues MS KB 929868 - web browsing issues MS KB 932170 - slow network file transfer
Compound TCP - Improve throughput Add-On Congestion Control Provider
The traditional slow-start and congestion avoidance algorithms in TCP help avoid network congestion by gradually increasing the TCP window at the beginning of transfers until the TCP Receive Window boundary is reached, or packet loss occurs. For broadband internet connections that combine high TCP Window with higher latency (high BDP), these algorithms do not increase the TCP windows fast enough to fully utilize the bandwidth of the connection.
Compound TCP (CTCP) is a newer method, available in Vista and Server 2008 (there is also a hotfix available for XP/2003). CTCP increases the TCP send window more aggressively for broadband connections (with large RWIN and BDP). CTCP attempts to maximize throughput by monitoring delay variations and packet loss. It also ensures that its behavior does not impact other TCP connections negatively.
By default, Vista and Windows 7 have CTCP turned off, it is only on by default under Server 2008. Turning this option on can significantly increase throughput.
To enable CTCP, in elevated command prompt type:
netsh int tcp set global congestionprovider=ctcp
netsh int tcp set global congestionprovider=none
Possible options are: ctcp, none, default (restores the system default value).
Recommended setting: ctcp It is better to use this newer generation CTCP congestion control algorithm for most broadband connections, we highly recommend it being turned on.
ECN Capability
ECN (Explicit Congestion Notification, RFC 3168) is a mechanism that provides routers with an alternate method of communicating network congestion. It is aimed to decrease retransmissions. In essence, ECN assumes that the cause of any packet loss is router congestion. It allows routers experiencing congestion to mark packets and allow clients to automatically lower their transfer rate to prevent further packet loss. Traditionally, TCP/IP networks signal congestion by dropping packets. When ECN is successfully negotiated, an ECN-aware router may set a bit in the IP header (in the DiffServ field) instead of dropping a packet in order to signal congestion. The receiver echoes the congestion indication to the sender, which must react as though a packet drop were detected.
ECN is disabled by default in Vista and other modern TCP/IP implementations, as it is possible that it may cause problems with some outdated routers that drop packets with the ECN bit set, rather than ignoring the bit. To check whether your router supports ECN, you can use the Microsoft Internet Connectivity Evaluation Tool. The results will be displayed under "Traffic Congestion Test".
To enable ECN, in elevated command prompt type:
netsh int tcp set global ecncapability=enabled
Possible settings are: enabled, disabled, default (restores the state to the system default).
The default state is: disabled
Recommendation: enabled (only for short-lived, interactive connections and HTTP requests with routers that support it, in the presense of congestion/packet loss), disabled otherwise (for pure bulk throughput with large TCP Window, no regular congestion/packet loss, or outdated routers without ECN support).
Notes: ECN is only effective in combination with AQM (Active Queue Management) router policy. It has more noticeable effect on performance with interactive connections and HTTP requests, in the presense of router congestion/packet loss. Its effect on bulk throughput with large TCP Window are less clear.
More information on ECN: Explicit Congestion Notification (ECN) for TCP/IP
RSS - Receive-side Scaling
The receive-side scaling setting enables parallelized processing of received packets on multiple processors, while avoiding packet reordering. It avoids packet reordering y separating packets into "flows", and using a single processor for processing all the packets for a given flow. Packets are separated into flows by computing a hash value based on specific fields in each packet, and the resulting hash values are used to select a processor for processing the flow. This approach ensures that all packets belonging to a given TCP connection will be queued to the same processor, in the same order that they were received by the network adapter.
To set RSS:
netsh int tcp set global rss=enabled
Possible rss settings are: disabled, enabled, default (restores rss state to the system default).
Default state is: enabled
Recommended: enabled (if you have 2 or more processor cores and a NIC that can handle RSS)
TCP Chimney Offload
TCP chimney offload enables Windows to offload all TCP processing for a connection to a network adapter. Offloads are initiated on a per-connection basis. Compared to task offload, TCP chimney offload further reduces networking-related CPU overhead, enabling better overall system performance by freeing up CPU time for other tasks.
To set TCP Chimney Offload:
netsh int tcp set global chimney=enabled
Default state: disabled (under Vista), automatic (under Windows 7 and 2008 Server)
Recommended: enabled
The possible states are disabled, enabled, default (Vista), automatic (only Windows 7 and 2008 Server) as follows:
automatic - This default setting is only available under Windows 7 and 2008 Server, it is not available udner Vista. It offloads if the connection is 10 GbE, has a RTT < 20ms, and the connection has exchanged at least 130KB of data. The device driver must also have TCP Chimney enabled. default - this setting restores chimney offload to the system default. Setting this "default" state under Windows 7 and 2008 Server is possible, but it sets the system to the "automatic" mode described above. disabled - this setting is maually configured as disabled. enabled - this setting is manually configured as enabled.
Notes:
Under Windows 7 and Server 2008 the "default" and the additional "automatic" parameter set the system to the same "automatic" state.
For Chimney Offload to work, it needs to be enabled in both the OS and NIC. To enable the "TCP Offloading" setting in your NIC, navigate to the Device Manager, under Network Adapters, in the Advanced tab, and check "Enabled" in the box next to the TCP offload entry.
Direct Cache Access (DCA)
Windows 7 and 2008 Server (but not Vista) add NETDMA 2.0 Direct cache access support. Direct Cache Access (DCA) allows a capable I/O device, such as a network controller, to deliver data directly into a CPU cache. The objective of DCA is to reduce memory latency and the memory bandwidth requirement in high bandwidth (Gigabit) environments. DCA requires support from the I/O device, system chipset, and CPUs.
To enable DCA:
netsh int tcp set global dca=enabled
Available states are: enabled, disabled.
Default state: disabled
Recommended: enabled (provided the CPU/Chipset/NIC support it)
It is also possible to enable this setting by editing the Windows Registry instead of using netsh as follows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters EnableDCA=1(DWORD, entry does not exist by default. Set to 1 to enable, 0 to disable)
Setting MTU
It is sometimes useful to view and set the MTU value for a specific network interface manually. To view a list of active network interfaces and their MTU values in Vista using netsh, open command prompt as administrator and execute the following command:
Where "network interface name" is your specific network adapter name as obtained above (or viewable under Network adapters), and mtu=#### is the desired MTU value.
For example, if the name of your network card is "Wireless Network Connection" and you'd like to set its MTU to 1500, you'd have to type:
johnb1, welcome to the forum! Firefox has a download manager called "Down Them All", which works very well for me. It may be worth your time to try it out. It has worked for me on every Windows & Linux OS that I've installed it on.
Hopefully, out of the answers that has been presented, you'll find a solution. It can be a pain in the rear waiting forever for a download to complete, I know firsthand. There's also lots of really useful information, as well as excellent help on this forum. I hope that you enjoy your stay, and you get your issue straightened out soon.
Don't forget guys the OP said he could download the same files with no trouble. Nibs mentioned the internet connection and I would be thinking that for some reason the Win7 is handling it different to how XP was, somethings changed in his settings.
Tried Freedownloadmanager and found that a test download stopped and started several times as before but the connection held so was able to complete the download.
Then tried some of the tweeks suggested by Nibiru.
netsh int tcp set heuristics disabled
netsh int tcp set global autotuninglevel=disabled
Problem still the same
netsh int tcp set global congestionprovider=ctcp
Big improvement. Downloaded several large files without problem and not using any download manager.
Will leave setting like this for while and see what happens
You'd be very surprised how many "new computers" I see in one day alone that have ancient network drivers from Realtek, from way before Windows 7 RTM release.
These old drivers are also proven bsod causers.
I would definitely install the latest driver from Realtek's website. I guarantee you that the one you have now is from February 2009.
Check your device manager for it's number. Then search for it here on the left side. If it's 8111, don't search and install directly from the link.
I have a similar problem at times with downloads. Some of which can be attributed to having a cable based ISP (Time Warner). I was doing some searching for my internet adapters, and ran across a site called "Radar Sync". My WOT add on in Firefox reports this site as unsafe.
Can anyone verify if this is a safe site or not? I'd like to update my network drivers, I went to the Atheros site to find drivers for my AR5007EG wireless network adapter, but it reported a 2008 driver. Surely there must be a more recent driver than that.
PS: I managed to find a driver (Version 7.7.0.331) Vista 32/64 bit dated 12.06.2009. I believe it was a German website that it came from, so the date my be in reverse. Anyway, from the info that I could find, this component was installed in many XP systems. It's a little surprising to me that a component that old would be installed in a desktop that was manufactured in 2009.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
