over speed tested
Thursday, 21. September 2006, 13:05:52
Here's how to get it back:
Click Start-->Run-->type "gpedit.msc" without the "
This opens the group policy editor. Then go to
Local Computer Policy-->Computer Configuration-->Administrative Templates-->Network-->QOS Packet Scheduler-->Limit Reservable Bandwidth
Double click on Limit Reservable bandwidth. It will say it is not configured, but the truth is under the 'Explain' tab :
"By default, the Packet Scheduler limits the system to 20 percent of the bandwidth of a connection, but you can use this setting to override the default."
So the trick is to ENABLE reservable bandwidth, then set it to ZERO.
This will allow the system to reserve nothing, rather than the default 20%.
works on XP Pro, 2000 but not on other o/s not tested.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316666
Windows XP Quality of Service (QoS) enhancements and behavior
View products that this article applies to.
Article ID:316666
Last Review:February 9, 2006
Revision:4.0
This article was previously published under Q316666
On This Page
SUMMARYSUMMARY
QoS for Internet Connection Sharing QoS for Internet Connection Sharing
QoS for modems and remote accessQoS for modems and remote access
Clarification about the use of QoS in end computers that are running Windows XPClarification about the use of QoS in end computers that are running Windows XP
Correction of some incorrect claims about Windows XP QoS supportCorrection of some incorrect claims about Windows XP QoS support
SUMMARY
Networking Quality of Service (QoS) refers to a variety of techniques that prioritize one type of traffic or program that operates across a network connection instead of relying only on "best effort" connectivity. QoS mechanisms are built into both Microsoft Windows 2000 and Windows XP. This article describes the enhancements in QoS that are available in Windows XP. References to the QoS features that were first introduced in Windows 2000 are also mentioned in this article.
Back to the topBack to the top
QoS for Internet Connection Sharing
When one network is connected to another network through a slow link or connection, such as a dial-up line, a situation can exist that will increase the delay of traffic that is traversing the slow link. This delay occurs because of the speed mismatch between what the end stations in the communication know about, and the slow link. The slow link causes a bottleneck in the network path. This applies only to connection-oriented communication when you use TCP.
If the receiving client is running on a relatively fast network, such as a 100 megabytes per second Ethernet network, behind a computer that is running Windows XP with the Internet Connection Sharing service, and the server that this receiver is communicating with is behind a remote access on a fast network, the mismatch exists. In this scenario, the receiver's receive window is set to a large value that is based on the speed of the link the receiver is connected to. The sender starts out by sending at a slow rate, but if packets are not lost, the sender eventually sends almost a full window size of packets.
This scenario can affect the performance of other TCP connections that traverse the same network. Packets sit in a potentially large queue and wait to be transmitted over the slow network. If packet loss occurs, data has to be retransmitted, and this also congests the link.
The solution to this issue is to have the computer that is running Internet Connection Sharing on the edge of the network automatically set the receive window to a smaller size that is appropriate to the slow link. This setting overrides the receiver's specification. This setting will not adversely affect traffic, because the window size is being set as if the receiver were connected directly to the slow link. The QoS Packet Scheduler component that is running on the Internet Connection Sharing computer makes this window adjustment.
Back to the topBack to the top
QoS for modems and remote access
As of January 2002, many people still connect to the Internet through slow links, such as connections with speeds of 56 kilobits per second. Even with the limitations on the speed of the link, many users will run several programs at the same time that access the network. For example, users may simultaneously use downloads, e-mail, chat, and even audio or video streaming. Most of these programs use TCP as the underlying protocol for the transfer, and each programs uses its own connection or connections.







