Skip to content
  • There are no suggestions because the search field is empty.

Error 4226 in Windows Event Log on XP SP2 Computer

I have two new PCs running XP service pack two and we just installed OmniServer version 2.0-026. When we turn on one we get these errors in our Windows event log. The errors in the event log talk about reaching the limit of TCPIP. Here is the event:

Event Type: Warning Event Source: Tcpip Event Category: None Event ID: 4226 Description: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

What is this, and is there something we can do about it? My OmniServer configuration has 81 topics, each one connecting to a unique TCP/IP device.

Starting with Windows XP SP2, Microsoft imposed a limit on TCP/IP connection attempts for a given machine. That limit is 10 TCP/IP connections per second.

The old limit under XP and SP1 was unlimited.

Microsoft's explanation of what they did can be found here:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx
It's under the TCP/IP section. Their solution to this problem is to stop the application making all the requests, which of course in this application is not a practical solution.

The overall effect of this can mean a slow down in startup if there are large number of TCP/IP connections that must be opened. In this case, 81 topics will take about 9 seconds to start up, but you should still eventually get all your connections. This is a limitation on XP SP2 imposed by Microsoft and cannot be changed. 

It is important to note this same limitation will affect any other OPC server or driver attempting to open multiple TCP/IP connections in a rapid manner.