H
huhuiyu
As you know the xp limits its tcp connection ,i want to know which
command to display it ?
command to display it ?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
V
VanguardLH
It's not a command. It's not an option in some program. It's a
registry setting. Read:
http://support.microsoft.com/kb/183110
I have mine set to 16 (10 hex). Well, I suppose the "command" would be
"regedit.exe".
registry setting. Read:
http://support.microsoft.com/kb/183110
I have mine set to 16 (10 hex). Well, I suppose the "command" would be
"regedit.exe".
S
Steve Riley [MSFT]
The registry keys documented in KB 183110 are for maximum simultaneous HTTP
connections to a single Web server. The defaults are four connections for an
HTTP 1.0 server, and two connections for an HTTP 1.1 server (the HTTP 1.1
specification mandates a two-connection limit).
The OP asked about XP's TCP connection limit. We hard-coded that to 10 in
service pack 2. There is no registry key to change this.
--
Steve Riley
(e-mail address removed)
http://blogs.technet.com/steriley
http://www.protectyourwindowsnetwork.com
connections to a single Web server. The defaults are four connections for an
HTTP 1.0 server, and two connections for an HTTP 1.1 server (the HTTP 1.1
specification mandates a two-connection limit).
The OP asked about XP's TCP connection limit. We hard-coded that to 10 in
service pack 2. There is no registry key to change this.
--
Steve Riley
(e-mail address removed)
http://blogs.technet.com/steriley
http://www.protectyourwindowsnetwork.com
M
Michael Bednarek
As you know the xp limits its tcp connection ,i want to know which
command to display it ?
Do you see event 4226 frequently in your Event Log? If so, get the fix
from <http://www.lvllord.de/>. That program will a) display the current
setting; b) offer to modify it.
V
VanguardLH
You saw more than I did. There was no mention of whether the limits
that the OP wanted to exceed were outbound or inbound connect limits.
"xp" doesn't actually describe much nor does "its connection" specify
outbound or inbound connects. I guess outbound. You guessed inbound.
The post was vague so the result is replies that are just as unfocused
as was the question.
The registry hacks only specify maximum outbound connects via HTTP and
HTTPS. That doesn't mean there is necessarily a web server at the other
end. Depends on the port used which doesn't have to be 80. Depends on
what process is listening on that port at the other end; for example,
some remote access tools use port 80 to get around corporate firewalls,
like TeamViewer. You only know the registry edits are for outbound HTTP
and HTTPS, not what is on the other end.
The workstation 10-connect inbound limit was set back in Windows NT 3.5,
not in a service pack for Windows XP. Read
http://support.microsoft.com/kb/314882 and you'll notice it refers back
to Windows 2000. Go read http://support.microsoft.com/kb/122920 and
notice that goes back to WinNT3.5. It wasn't Service Pack 2 for Windows
XP that established that limit
...
that the OP wanted to exceed were outbound or inbound connect limits.
"xp" doesn't actually describe much nor does "its connection" specify
outbound or inbound connects. I guess outbound. You guessed inbound.
The post was vague so the result is replies that are just as unfocused
as was the question.
The registry hacks only specify maximum outbound connects via HTTP and
HTTPS. That doesn't mean there is necessarily a web server at the other
end. Depends on the port used which doesn't have to be 80. Depends on
what process is listening on that port at the other end; for example,
some remote access tools use port 80 to get around corporate firewalls,
like TeamViewer. You only know the registry edits are for outbound HTTP
and HTTPS, not what is on the other end.
The workstation 10-connect inbound limit was set back in Windows NT 3.5,
not in a service pack for Windows XP. Read
http://support.microsoft.com/kb/314882 and you'll notice it refers back
to Windows 2000. Go read http://support.microsoft.com/kb/122920 and
notice that goes back to WinNT3.5. It wasn't Service Pack 2 for Windows
XP that established that limit
...
S
Steve Riley [MSFT]
Agreed, the OP didn't specify whether the connections were inbound or
outbound.
Inbound connections have been limited to 10 for some time now, as you
indicate in the KBs you reference. The 10-connection limit for outbound
sessions was indeed an XP SP 2 change. Because people often come to the
newsgroups to look for ways around that, I figured the OP's question was
similar.
outbound.
Inbound connections have been limited to 10 for some time now, as you
indicate in the KBs you reference. The 10-connection limit for outbound
sessions was indeed an XP SP 2 change. Because people often come to the
newsgroups to look for ways around that, I figured the OP's question was
similar.