SP2 and Peer To peer
#1
08-14-04, 10:06 AM
Join Date: Nov 2002
Posts: 2,451
Upvotes: 0
Received 0 Upvotes
on
0 Posts
SP2 and Peer To peer
Alot of people are having problems using peer to peer file sharing networks after installing the service pack 2 for XP. If you are, you need to replace your TCP stack. You can go here:http://www.speedguide.net and download one of their registry speed patches (like the sguide tweak 2k) and install/merge it. Might fix the problem, and may get you better speed!
Last edited by tae; 08-14-04 at 05:18 PM. Reason: see post below for better fix
#3
08-14-04, 02:44 PM
Join Date: Nov 2002
Posts: 2,451
Upvotes: 0
Received 0 Upvotes
on
0 Posts
the problem and fix
THE PROBLEM:
SP2 limits the number of simultaneous incomplete outbound TCP connection attempts. This is how to test if it effects you.
Directions
By design SP2 limits the number of simultaneous incomplete outbound TCP connection attempts. After the rate is reached, subsequent connection attempts are placed in a queue eventually to be resolved at a fixed rate.
Rumors are already around the internet that this slows down programs that open multiple TCP connections at once. Port scanners are a good example of this. Some P2P might be effect as well in theory.
Microsoft now will create a unique event log message with ID 4226 when this rate limiting occurs. Here is how to see if you are affected by this change.
Opening the Event Viewer:
1. Open Your Control Panel
2. Click Performance and Maintenance (skip if in classic view)
3. Click Administrative Tools Folder
4. Click Event Viewer
5. In the Event Viewer select System in the left column
6. Scroll through the events in the right column looking for 4226 errors.
http://www.tech-recipes.com/windows_...ix/4226fix.htm
THE FIX:
http://www.lvllord.de/4226fix/4226fix.htm
SP2 limits the number of simultaneous incomplete outbound TCP connection attempts. This is how to test if it effects you.
Directions
By design SP2 limits the number of simultaneous incomplete outbound TCP connection attempts. After the rate is reached, subsequent connection attempts are placed in a queue eventually to be resolved at a fixed rate.
Rumors are already around the internet that this slows down programs that open multiple TCP connections at once. Port scanners are a good example of this. Some P2P might be effect as well in theory.
Microsoft now will create a unique event log message with ID 4226 when this rate limiting occurs. Here is how to see if you are affected by this change.
Opening the Event Viewer:
1. Open Your Control Panel
2. Click Performance and Maintenance (skip if in classic view)
3. Click Administrative Tools Folder
4. Click Event Viewer
5. In the Event Viewer select System in the left column
6. Scroll through the events in the right column looking for 4226 errors.
http://www.tech-recipes.com/windows_...ix/4226fix.htm
THE FIX:
http://www.lvllord.de/4226fix/4226fix.htm
#4
08-14-04, 05:16 PM
Join Date: Nov 2002
Posts: 2,451
Upvotes: 0
Received 0 Upvotes
on
0 Posts
RAHAROLD:
they will help upto the speed of your wireless. If that is the slowest link in the chain, they wont help. If it's not, then they should help. Either way, it probably won't hurt to try. They can all be reversed.
they will help upto the speed of your wireless. If that is the slowest link in the chain, they wont help. If it's not, then they should help. Either way, it probably won't hurt to try. They can all be reversed.
