limits the number of concurrent incomplete outbound TCP connection attempts

[skyhawk]

Hi,
Our company was thinking of upgrading our systems to XP, but we worried
about the 10 connection limit for incomplete outbound TCP connections. We
may have to make a change regarding the networking part of our application.
I had a couple of questions about the feature.

1 .It appears that the limit includes open connections that are in the
process of opening (the computer exists and the protocol hasn't completely
opened the socket) and connections where the computer doesn't exist (not
powered up whatever). Is this true ?

2. I saw on one place on the net that said that Windows 2003 server had
this limitation too .. Is this true ?

Thanks,
Jerry

 

[Jack \(MVP-Networking\).]

Hi
Windows 2003 SBS goes up to 75 Lic. workstations.
http://www.microsoft.com/windowsserver2003/sbs/default.mspx
Jack (MVP-Networking).

 

[Lanwench [MVP - Exchange]]

In

Hi,
Our company was thinking of upgrading our systems to XP, but we
worried about the 10 connection limit for incomplete outbound TCP
connections.

I think you mean inbound?

We may have to make a change regarding the networking
part of our application. I had a couple of questions about the
feature.
1 .It appears that the limit includes open connections that are in the
process of opening (the computer exists and the protocol hasn't
completely opened the socket) and connections where the computer
doesn't exist (not powered up whatever). Is this true ?

I'm not sure, but I do know from long experience that you can often find
yourself running out of available connections because the 'server' hasn't
kept up with the current connection status....and I'm pretty sure that one
computer can take up more than one connection at a time.

2. I saw on one place on the net that said that Windows 2003 server
had this limitation too .. Is this true ?

There's no built-in limit to the number of connections you can make to a
W2003 server. You just need to buy as many CALs as you have
clients...whether devices or users....and most people stop & disable the
buggy license logging service and keep track of their licenses manually.

 

[skyhawk]

Sorry I don't mean the # of connections , but the # of concurrent
half-opened connections in regards to event ID 4226.

As it has been explained in detail :
The TCP/IP stack in Windows XP with Service Pack 2 (SP2) installed limits
the number of concurrent,
incomplete outbound TCP connection attempts. When the limit is reached,
subsequent connection attempts are put in a queue and resolved at a fixed
rate
so that there are only a limited number of connections in the incomplete
state.
During normal operation, when programs are connecting to available hosts at
valid IP addresses,
no limit is imposed on the number of connections in the incomplete state.
When the number of incomplete connections exceeds the limit, for example,
as a result of programs connecting to IP addresses that are not valid,
connection-rate limitations are invoked, and this event is logged.



Actually after re-reading this paragraph, I think I answered part one myself
.

Thanks,

Jerry

 

[Doug Sherman [MVP]]

I think you may be referring to the SP2 outbound connection attempts/sec
limit. Go here:

http://www.speedguide.net/read_articles.php?id=1497

Doug Sherman
MCSE, MCSA, MCP+I, MVP

 

[skyhawk]

Thanks, Doug yes I am.
We have one install on XP and I am trying to find out if this is causing us
issues or it is something else.