Here are Registry Tweaks and Scroll down to see PatchesThe following content will be shown upon reply1.Increase bandwidth by tweaking QoS in Windows XP Pro
The following tweak applies only to Windows XP Professional edition.
The default system behavior is that all 100% bandwidth is available,
however, if there is a running application that indicates to the OS it
needs to send high priority/real time data, then as long as it has the
socket open, Windows XP will restrict “best effort” traffic to 80% of
the bandwidth so that high priority traffic can be accommodated.
Basically, applications can make this request to the operating system
for QoS support using the QoS application programming interfaces (APIs)
in Windows and this only applies if a specific app is requesting QoS.
If you'd like to change how much bandwidth is reserved for QoS (the default is 20% of the total bandwidth), do the following:
1. Make sure you're logged in as "Administrator" (not just any account with admin privileges).
2. Navigate to START>Run and type: gpedit.msc
3. Navigate to Local Computer Policy > Administrative Templates > Network > QOS Packet Scheduler
4. In the right window, double-click the limit reservable bandwidth setting
5. On the setting tab, check the enabled setting.
6. Where it says "Bandwidth limit %", change it to read 0 (or whatever
percentage you want to reserve for high priority QoS data)
7. Click OK, close gpedit.msc
Under START > My Computer > My Network Connections > View
Network Connections, right-click on your connection and under
Properties (where it lists your protocols), make sure QOS Packet
Scheduler is enabled.
The tweak desribed below helps boost priority for DNS & hostname
resolution in general. What this means is, it helps web pages load
faster, and has negligible effect on downloads (not counting the couple
of ms gain with the host resolution at connect-time).
Applying this tweak assumes some proficiency in editing the Windows
Registry using Regedit (Start > Run > type: regedit). As always,
backup your Registry before making any changes so you can revert to the
previous state if you don't like the results.2.Host Resolution Priority Tweak
host name resolution priority
First, open the Windows Registry using Regedit, and (after backing up) navigate to:
Note the following lines (all hex dwords):
Class = 008 (
- indicates that TCP/IP is a name service provider, don't change.
LocalPriority = 1f3 (499) - local names cache
HostsPriority = 1f4 (500) - the HOSTS file
DnsPriority = 7d0 (2000) - DNS
NetbtPriority = 7d1 (2001) - NetBT name-resolution, including WINS
What we're aiming to do is increase the priority of the last 4
settings, while keeping their order. The valid range is from -32768 to
+32767 and lower numbers mean higher priority compared to other
services. What we're aiming at is lower numbers without going to
extremes, something like what's shown below should work well:
Change the "Priority" lines to:
LocalPriority = 005 (5) - local names cache
HostsPriority = 006 (6) - the HOSTS file
DnsPriority = 007 (7) - DNS
NetbtPriority = 008 (
- NetBT name-resolution, including WINS
The tweak is essentialy the same as in Windows 2000/XP, just the
location in the Registry is slightly different. For a more detailed
description see the Windows 2000/XP section above.
Open the Windows Registry using Regedit, and (after backing up) navigate to:
You should see the following settings:
The "priority" lines should be changed to:
Reboot for changes to take effect.
In addition to the tweaks already covered in Win 2k/XP Registry Tweaks
and More Win 2k/XP Tweaks, the Windows XP Service Pack 2 introduces a
few new issues covered in the article below. Please make sure you
understand what you are doing before making any changes to your
Operating System. Note the information below only applies to Windows XP
Service Pack 2.3.Remove the limit on TCP connection attempts
Windws XP SP2 introduces a few new twists to TCP/IP in order to babysit
users and "reduce the threat" of worms spreading fast without control.
In one such attempt, the devs seem to have limited the number of
possible TCP connection attempts per second to 10 (from unlimited in
SP1). This argumentative feature can possibly affect server and P2P
programs that need to open many outbound connections at the same time.
Rant: The forward thinking of Microsoft developers here is that you can
only infect 10 new systems per second via TCP/IP ?!?... If you also
consider that each of those infected computers will infect 10 others at
the same rate:
second 1: 1+10 computers
second 2: 10+10*10 computers (110 new ones)
second 3: 10+100*10 computers ( 1110 new ones)
second 4: 10+1000*10 computers (11110 new ones)
all the way to 10*60 + 10^60 computers in a single minute (that's a
number with 60 digits, or it would far exceed Earth's population). Even
if we consider that 90% of those computers are unreachable/protected,
one would still reach ALL of them within a minute.
In other words, even though it is not going to stop worm spreading,
it's going to delay it a few seconds, limit possible network congestion
a bit, and limit the use of your PC to 10 connection attempts per
second in the process ! I have no problem with the new default setting
limiting outbound connection attempts. Still, users should have the
option to easily disable or change this setting. I might be going out
on a limb here, but ever since the introduction of Windows XP I can't
help thinking that I dislike all the bult-in Windows "wisardry" in a
sense that the system also limits user access. That irritating trend to
ease the mental load on end users is somewhat insulting, considering
that Windows is to make the more "intelligent" choice instead of the
end user, as well as limit their access to tuning such settings...
End of rant.
With the new implementation, if a P2P or some other network program
attempts to connect to 100 sites at once, it would only be able to
connect to 10 per second, so it would take it 10 seconds to reach all
100. In addition, even though the setting was registry editable in XP
SP1, it is now only possible to edit by changing it directly in the
system file tcpip.sys. To make matters worse, that file is in use, so
you also need to be in Safe mode in order to edit it.
You only need to worry about the number of connection attempts per
second if you have noticed a slowdown in network programs requiring a
number of connections opened at once. You can check if you're hitting
this limit from the Event Viewer, under System - look for TCP/IP
Warnings saying: "TCP/IP has reached the security limit imposed on the
number of concurrent TCP connect attempts". Keep in mind this is a cap
only on incomplete outbound connect attempts per second, not total
connections. Still, running servers and P2P programs can definitely be
affected by this new limitation. Use the fix as you see fit.
To change or remove the limit, you can use the following program:
Event ID 4226 Patcher v2.11
A patching program for removing or changing the limit imposed on
connection attempts in SP2. The patcher has the ability to restore
tcpip.sys back to the original... Still, you might want to back up
tcpip.sys, use it at your own risk. The author of this patch can be
reached @ http://www.lvllord.de/4. Recommended settings for Windows 2000 / XP
Windows 2000 & XP, unlike NT supports large windows as described in
RFC1323 ( the 'RcvWindow' has a maximum value of 2**30 rather than
64K), and includes some other improvements over its predecessors you
can use to speed up any TCP/IP transfers. , the descriptions and other
options are added to provide you with better understanding and enable
you to customize your settings.
All the following entries, unless otherwise noted should be placed in the Windows 2000/XP Registry under the key