⌊ K™¦krizzna.web.id ⌉
Sekedar coretan seorang nyubi
How to crack the TCP connections limit in Windows imposed by Microsoft
How to crack the TCP connections limit in Windows imposed by Microsoft
Introduction
Windows XP SP2 introduced 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 other programs (see list below) 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 network program (e.g. Xrumer) 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 (causing possible software timeouts) . 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.
You need to patch your Windows if you:
Use SEO Software like: Xrumer, Scrapebox, etc.
Use Proxy Checker
Use P2P Software like: Bittorrent
any other Software using more then 10 simultaneous outbound connections
This guide applies to the follwoing Windows Version:
Windows 2000
Windows XP SP2 SP3
Windows 2003/2008
Windows Vista SP1 SP2
Windows 7, All 32bit (x86) / 64bit (x64)
What you need:
Project Name: TCP-Z (TCP-Z Network Monitor)
Support OS： Windows XP SP2 SP3/2003/2008/Vista SP1 SP2/Windows 7, All 32bit (x86) / 64bit (x64)
(Event ID 4226 Patcher, EvID4226 fix, TCP/IP Patch, TCP Half Open Connection Limit Patch.)
Remove / increase the limit of half-open (incomplete outbound) TCP connections, Release the power of your network, download faster, and more task can be run at the same time.
You can download the Patch here:
Includes:
TCP-Z (Patch TCPIP in memory – must be enabled each time you start Windows)
Univseral Tcpip.sys Patch (I recommend this method – Patch it – restart – done)
Driver for TCP-Z (by installing this driver TCP-Z will automaticall change Tcpip.sys in memory)
Note:You could get a Virus warning on the Driver for TCP-Z as Virus Software assumes its a virus by using the heuristic flag detection method.
I recommend to set the new TCPIP limit to a minimum of 100 and a maximum of 1024 (X-Rumer)
Recommendation: Before buying Proxy Lists apply this patch.
Buy HTTP Anonymous, Elite, SOCKS 4 and 5 Proxy Lists here
Article from articlesbase.com
Tags: connections, crack, imposed, limit, Microsoft, Windows
Recent Comments