|
windows
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
limits the number of concurrent incomplete outbound TCP connection attemptsHi,
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 Hi
Windows 2003 SBS goes up to 75 Lic. workstations. http://www.microsoft.com/windowsserver2003/sbs/default.mspx Jack (MVP-Networking). Show quoteHide quote "skyhawk" <skyhawk@community.nospam> wrote in message news:erLw23S0GHA.4772@TK2MSFTNGP03.phx.gbl... > 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 > > 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 Show quoteHide quote "Jack (MVP-Networking)." <J***@discussiongroup.com> wrote in message news:%23A2DkfT0GHA.5072@TK2MSFTNGP03.phx.gbl... > Hi > Windows 2003 SBS goes up to 75 Lic. workstations. > http://www.microsoft.com/windowsserver2003/sbs/default.mspx > Jack (MVP-Networking). > > "skyhawk" <skyhawk@community.nospam> wrote in message > news:erLw23S0GHA.4772@TK2MSFTNGP03.phx.gbl... >> 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 >> >> > > In news:erLw23S0GHA.4772@TK2MSFTNGP03.phx.gbl, skyhawk <skyhawk@community.nospam> typed:> Hi, I think you mean inbound?> 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 I'm not sure, but I do know from long experience that you can often find > 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 ? 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. > There's no built-in limit to the number of connections you can make to a > 2. I saw on one place on the net that said that Windows 2003 server > had this limitation too .. Is this true ? 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. Show quoteHide quote > > Thanks, > Jerry 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 Show quoteHide quote "skyhawk" <skyhawk@community.nospam> wrote in message news:erLw23S0GHA.4772@TK2MSFTNGP03.phx.gbl... > 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 > > 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. Show quoteHide quote "Doug Sherman [MVP]" <nodspamherman@notampabayspamforme.rr.com> wrote in message news:evjpw8b0GHA.3908@TK2MSFTNGP05.phx.gbl... >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" <skyhawk@community.nospam> wrote in message > news:erLw23S0GHA.4772@TK2MSFTNGP03.phx.gbl... >> 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 >> >> > > 
Other interesting topics
XP: Need to change 'workstation' service so it loads LAST because i have problems. (delay at boot)
Sharing Programs New Connection Wizard creates Dial-Up Connection instead of Broadb Broadband dial up Setting up network - Web Server + client Machine not found on network Elementary question about internet connection sharing of two compu 3 computers connected; 2 see all 3; one only sees itself Trying to connect 2 VPN users: No more connections can be made help setting up a server based network |
|||||||||||||||||||||||
