Comments on: Windows Vista tcpip.sys Connection Limit Patch for Event ID 4226

By: Andrew

Andrew — Fri, 02 May 2008 15:50:20 +0000

P.s. I have Vista Ultimate 32bit SP1

By: Andrew

Andrew — Fri, 02 May 2008 15:49:49 +0000

I can’t open Windows,even in safe mode..I think I should repair Vista with the Recovery CD…

By: Rick

Rick — Fri, 02 May 2008 15:21:11 +0000

What version of tcpip.sys is this and on which version of Vista? And what specifically is the BSOD (particularly any module it mentions)?

You can reinstate tcpip.original for now so that you can get back into Windows.

By: Observador

Observador — Fri, 02 May 2008 15:19:47 +0000

Andrew you have sp1 installed? What i said is for vista with sp1 of you don´t have it, you probably do something wrong, try restart in safe mode and put the original file again

By: Andrew

Andrew — Fri, 02 May 2008 15:14:19 +0000

Doesn’t work.

By: Observador

Observador — Fri, 02 May 2008 14:02:17 +0000

Andrew, hit F8 on the boot screen and choose disable driver digital signatures check to load windows.

By: Andrew

Andrew — Fri, 02 May 2008 13:58:06 +0000

Hi guys,
I replaced the original tcpip.sys file with the “patched” tcpip.sys one. I restarted but now appears a BSOD at startup and I can’t open my computer anymore!!! Help me please…

By: Rick

Rick — Wed, 16 Apr 2008 16:59:25 +0000

lava, tell us all about 2010 please. It sounds way cool!

OK, I assume you meant SP1, and that you’re only getting to it now since you use one of the languages that MS didn’t release until yesterday.

Yes, SP1 does require a new fix, and it complicates things even on 32-bit due to driver signing checks.

For 32-bit, see message #266, and be sure to read the Readme in that v2.0 of the file.

For 64-bit, see the thread pointed to in #272.

By: lava

lava — Wed, 16 Apr 2008 13:35:26 +0000

Vista SP2 just came out. Does the update undo the tcpip fix? If it does, is another patch already in the works for SP2? I don’t want to update if it’s going to mess up my speeds on bt.

By: GWM 071b - Page 12 - Austech

GWM 071b - Page 12 - Austech — Wed, 16 Apr 2008 00:16:35 +0000

[...] Info on XP & win2003…not confirmed if it works yet. Windows Vista tcpip.sys Connection Limit Patch for Event ID 4226 My Digital Life [...]

By: Rick

Rick — Fri, 11 Apr 2008 19:20:03 +0000

For those interested in the latest on patching 64-bit SP1, check out the messages in this thread starting with till69’s post on April 5th. It’s looking very promising (I’m bjf2000 there).

http://forums.mydigitallife.info/showthread.php?t=1249

By: Adam

Adam — Wed, 02 Apr 2008 18:57:55 +0000

umm i cant copsy the patch, and now ive lost the whole of by desktop i just get a blue screen, what do i do?

By: Rick

Rick — Wed, 02 Apr 2008 17:01:43 +0000

No, it isn’t, even though I’ve had a request out for the new byte string for 64-bit SP1 for quite a while (last time I mentioned it was #262). Apparently, the only people who know how to find it are off planet.

But since you only have a few events and you’re not noticing the problem, I think you’re good as you are.

Plus, you avoid the annoyance of dealing with the unsigned driver nag every time you boot Windows, which is a problem for 32-bit and 64-bit SP1. If you don’t boot Windows that often (say, if you use standby instead) it wouldn’t be that annoying.

For those interested in an adventure, there is a way to get around it, and it’s what I use for 32-bit SP1, but it’s complex:

The Jan 31 and Feb 26 posts here give the specifics:
http://forums.microsoft.com/technet/showpost.aspx?postid=2012166&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=3

By: ElQuia

ElQuia — Wed, 02 Apr 2008 15:45:47 +0000

OK Rick Found it: yes, your right, got some 4226 events….
By reading post i suppose there isn´t a patched tcpip.sys available for vista x64 SP1?

By: ElQuia

ElQuia — Wed, 02 Apr 2008 15:40:07 +0000

Uh Rick, sorry for the very basic question: how do I see the system log?

By: Rick

Rick — Wed, 02 Apr 2008 15:13:18 +0000

ElQuia, that’s hard to say. Are 4226 errors that common in your System Log? If not, then what you’re doing cumulatively on that system is staying mostly within the bounds of the default number of concurrent TCP connect attempts, and you’re not going to notice much of anything. It would probably get noticeably worse the more bandwidth you had and the more you tried to do simultaneously on the system.

The Limewire FAQ mentions a scenario in which the default limit can lead to being disconnected from their network. They mention these three things that may help (you may already be doing these, helping you out of the box):

-Disable Ultrapeer Capabilities in Tools > Options > Speed
-Minimize the number of simultaneous downloads (can also be found in Options > Downloads)
-Minimize the number of other internet programs used alongside LimeWire