[ويندووس] [فيستا] [تكبيب.سس] توصيل حد رقعة لحادث [إيد] 4226
ظاهريّا في [ويندووس] [فيستا], ينفذ مكروسوفت بعد و [هرد-ليميت] (بشدّة يرمّز في [تكبيب.سس]) القصوى متزامنة [هلف-وبن] (ناقصة) خارجة [تكب] توصيل محاولات لكلّ ثانية أنّ النظامة يستطيع جعلت, بما أنّ في [ويندووس] [إكسب] [سب2], [إين وردر تو] يبرمج حميت النظامة من يكون يستعمل بخبيثة, مثل حميات وديدان, أن ينشر إلى حاسوبات [أونينفكتد], أو إلى إطلاق يوزّع [دنيل وف سرفيس] هجوم ([دّوس]). عندما ضربت الحد, في حادث مشاهدة, هناك سيكون هذا مدخل:
[إفنتيد] 4226: قد بلغ [تكب/يب] الأمن حد يفرض على الرقم من [تكب] متواقتة يربط محاولات
ما لم [ويندووس] [إكسب] [سب2] أيّ يتلقّى 10 توصيل قصوى ناقصة متواقتة يحاول حد لكلّ ثانية, [ويندووس] [فيستا] تقصير أسّست حد على أيّ طبعة من [فيستا] مستعملات يكون يستعمل. مثلا, بيتيّة يتلقّى أساسيّة [مإكسيموم ليميت] من 2, و [فيستا] نهائيّة 25 لكلّ ثانية. عاديّة [ويندووس] [فيستا] مستعملات سوفت لا يواجه أيّ مشكلة أو [هلف-وبن] [نتوورك كنّكأيشن] بطيئة مع التوصيلات حد. مهما, ثقيلة [ب2ب] ([بير-تو-بير]) تطبيقات مستعملات مثل [أوتورّنت], [بيتّورّنت], [بيتكمت], [أزوريوس], حروف, [إمول] ([إدونكي] شبكة), [إتك], أو [ب2بتف] مثل [تفنتس], [بّليف], [بّسترم], [سبكست], [إتك] يمكن واجهت بعض خطأ أو تمهّلت [دوونلوأد] و [أوبلوأد] سرعة واجبة إلى هذا حد.
انصدعت واجبة إلى يحسن أمن, إلى نقطة معيّنة أو ال [تكب] متواقتة توصيل حد في [فيستا] ليس مثل يتيح بما أنّ في [ويندووس] [إكسب]. [هلف-وبن] أن يزيل [كنكرّنت] قصوى توصيل حدود في [ويندووس] [فيستا], يطبّق ال يرقّع [تكبيب.سس] مع ال [ستبس] تالي:
- [دوونلوأد] يرقّع [تكبيب.سس]: [فيستا] [تكب/يب] و [أوك] سيارة [بتشر] (احتويت يرقّع [تكبيب.سس] في المحفوظ)
[64-بيت] [تكبيب.سس] أو [32-بيت] [تكبيب.سس]. بديلة [دوونلوأد] خطوة ل [32-بيت] و [64-بيت]. - فتحت أمر رسالة حثّ, وركضت التالي 2 أوامر:
1. [تكيوون] /f c:\\windows\\system32\\drivers\\tcpip.sys
2. [ككلس] c:\\windows\\system32\\drivers\\tcpip.sys /G "[أوسرنم]": [ف]استبدلت [أوسرنم] مع الحقيقيّة مستعملة اسم أنّ استعمل أن [لوغن] إلى [ويندووس] [فيستا] حاليّا.
الثاني أمر علبة أيضا يستعمل يحسن [لككلس]:
[إيككلس] c:\\Windows\\System32\\drivers\\tcpip.sys /grant "[أوسرنم]": [ف]
- أعجزت ال [تكب/يب] [أوتو-تثنينغ] سمة ب يركض الأمر تالي في أمر رسالة حثّ:
ثبت [نتش] [تكب] دوليّة شاملة [أوتوتثنينغلفلديسبل]
- ل [ويندووس] [64-بيت] [فيستا] ([إكس64]), النزاهة يحتاج تدقيقات أن يكون أعجزت ك هو حاجة كلّ سائقات أن يكون وقعت. هكذا ركضت الأمر تالي في [دو] رسالة حثّ:
[بكدديت.إكس] - [لوأدوبأيشنس] محدّدة [دّيسبلينتغريتشكس]
بطاقة: تطلّبت فوق أمر [نو لونجر] يساند, ومستعملات أن يضغط [ف8] على [سستم سترتثب] أن يجتنب سائقة يقع نزاهة تدقيق.
- تذكّرت استبدلت ال [تكبيب.سس] في C:\\windows\\system32\\drivers ملف مع ال يرقّع [تكبيب.سس] يجلب من خطوة 1 (الإستعمال ال يصحّ [إكس64] أو [إكس86] صيغة). Normally, this procedure can be done by simply login to Windows Vista with administrator account. However, if the process failed, reboot the computer and then press F8 to boot up in Safe Mode, and then copy and paste overwrite the tcpip.sys.
- Next, the maximum number of TCP half complete connection limits need to be set in registry. Open registry editor (regedit), and navigate to the following registry key:
HKEY_LOCALL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
- Right click on the right pane, select “New”, then select “DWORD value”. Enter the new value name as “TcpNumConnections” (without quotes).
- Double click on TcpNumConnections registry value, and modify the value data to the desired maximum TCP/IP connection limit that you want to allow, in decimal value. For example, enter 500 as the value data for TcpNumConnections. You can use any limit that you prefer. Alternatively, download this registry registration file (another download link) that when executed, will set the TCP simultaneous connection limit to 16777214 (you can always modify the value in the file or in the registry after applied).
- Restart computer.
New: Windows Vista Event ID 4226 Auto Patcher
Latest Version: 2.0
Windows Vista Event ID 4226 Auto Patcher has been renamed as Vista tcpip.sys and UAC Auto Patcher, which now has 6 versions of auto patcher download links for different versions of tcpip.sys with the release of various hotfixes and SP1. Visit here for details.
Driver Version: CrackTcpip.sys for Vista SP1 v.668 - a non-patching method to bypass TCP connection limit.
Also available is TCP/IP auto patcher for 64-bit (x64) Windows Vista SP1.
Gui Version: VistaTcpPath TCP Auto Patcher which works for Vista RTM (non-SP1) version of tcpip.sys.
Old Version:
Version 1.0
Version 1.2
Version 1.3
Version 1.4
Version 1.5
With thanks to YaronMaor for batch script.
The TCP connection limit which trigger Event ID 4226 has now increased to 500 (or any other value you set), and will likely fix the error for re-occurring again.
IMPORTANT: This is a machine translated page which is provided "as is" without warranty. Machine translation may be difficult to understand. Please refer to original English article whenever possible.
Share and contribute or get technical support and help at My Digital Life Forums.
Related Articles
- Windows XP SP2 TCP Connection Limit (Event ID 4226)
- TCP/IP Has Reached the Security Limit Imposed on the Number of Concurrent TCP Connect Attempts Error on Windows Vista
- VistaTcpPatch Windows Vista TCP Half Open Limit Auto Patcher GUI Version
- CrackTcpip.sys Driver for Vista SP1 v.668 to Patch tcpip.sys 6.0.6001.17052
- Limit Maximum TCP Connections to Web Servers
- Increase Multithread Download Speed by Disable Vista Auto Tuning on TCP/IP
- TCPIP.SYS Driver Patcher CrackTcpip.sys for Vista SP1 v.744 and 6001.18000 (RTM)
- Optimize and Increase BitTorrent (BT) Download Speed in Vista
- Workaround to Run eMule in Windows Vista
- ppStream Connection Limit in Configuration Settings
Entries (RSS)
August 24th, 2008 15:58
i have vista sp1 x32 and when i used tyhis patch i had 2 system restore it . it would not let me boot. i got blue screen of death do not use
August 23rd, 2008 23:50
Installed the half-open patcher (see previous post) and it works smoothely, no fuss to install, easy GUI, set the nummber of half-connection, reboot, and you are done. Rollback to original tcpip.sys is possible.
August 11th, 2008 00:08
Thank you much for the patcher.
August 10th, 2008 03:06
I was thinking more along the lines of a security program of some kind which operates on file signatures, particularly for files in important directories like that one. Once it saw that the file was no longer the one it knew, it locked access to that file, though it certainly should have notified you about it.
I don’t know if the program you use does that, however.
Tons of people have used the patched file without incident. It can’t behave differently for you than others without some other variable involved.
Checking the System log for that time period might be informative.
Did you install using the batch file? Because that should have plowed right through any locked file issues.
August 9th, 2008 23:11
It looked to me like the system has recognized the new file and didn’t want to accept it. No firewall could be blocking it, because I didn’t change any settings for it. I just replaced the tcpip.sys (after some trouble-at first the file was locked, and I have some trouble removing it).
August 8th, 2008 04:47
Since the file itself (tcpip.sys) is good, it sounds to me like a firewall (or comparable) program was blocking or otherwise interfering with communications, as it didn’t recognize the new system file.
August 8th, 2008 04:38
My problem wa this: after applying this “home made” patch, all my external connections have failed, LAN and Wireless. After waiting about 30 mins for something to happen, nothing did. So i copied back original file and rebooted the system. Before login wireless hass connected, after login I can access my home network (LAN). So this patch doesn’t work for me.
Yes, I checked for the right version of the file, I installed that readydriver (or whatever it is) for quicker boot, but it didn’t work. Looks like I will have to live with this stupid enforcment until official microsoft update (that will happen: never).