XP Pro incoming connection limit?

Post #109,720 by bluke 7/15/03 9:55:30 AM Reply	XP Pro incoming connection limit? Does Windows XP Pro limit you to 10 simultaneous incoming connections? That is what this Microsoft knowledgebase article seems to imply [link\|http://support.microsoft.com/default.aspx?scid=kb;en-us;314882\|Inbound Connections Limit in Windows XP] "For Windows XP Professional, the maximum number of other computers that are permitted to simultaneously connect over the network is ten. This limit includes all transports and resource sharing protocols combined. For Windows XP Home Edition, the maximum number of other computers that are permitted to simultaneously connect over the network is five." However, I am running a web server on XP Pro for some testing and look at netstat and see 30+ tcp connections. What is going on?
Post #109,724 by deSitter 7/15/03 10:08:40 AM Reply	Re: XP Pro incoming connection limit? I think it's a EULA issue rather than a physical one. Windows NTWS 4 had a similar artificial limit. With a simple reghack it could be circumvented. -drl
Post #109,732 by Andrew Grygus 7/15/03 10:48:55 AM Reply	It's in the last sentence. TCP/IP connections aren't enforced, but logical connections are (disk & printer). If I remember correctly, this was specifically done to allow serving Web pagess. [link\|http://www.aaxnet.com\|AAx]
Post #109,750 by pwhysall 7/15/03 11:50:55 AM Reply	Re: XP Pro incoming connection limit? Connections, not sockets. Try getting 11 computers to connect to the same share; won't happen. Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]
Post #109,878 by kmself 7/16/03 1:45:05 AM Reply	Some add'l data -- incoming Samba connections I ran into this with a Linux box in a MSFT shop. Was using `smbmount` to mount shares from Windows boxen. Found that I could only connect a certain number of shares per box.... Turns out that there's this ten-user limit... and that each connection to a box (some had more than ten shares) counted as a concurrency. \r\n\r\n My interim fix was to use autofs with a four second timeout (could have dropped this to 1-2 seconds, hmm...), which kept me from holding open any one connection too long, though I'd not time out if I was repeatedly hitting a share. \r\n\r\n There's some additional stuff, including the opportunity to permanently authenticate to an NT domain, which may get around some of these restrictions. You're still limited by the number of simultaneous users accessing a share (or server), I suspect. Check with the Windows Boi, Peter Whysall, for specifics. --\r\n Karsten M. Self [link\|mailto:kmself@ix.netcom.com\|kmself@ix.netcom.com]\r\n [link\|http://kmself.home.netcom.com/\|http://kmself.home.netcom.com/]\r\n What part of "gestalt" don't you understand?\r\n [link\|http://twiki.iwethey.org/twiki/bin/view/Main/\|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n \r\n Keep software free. Oppose the CBDTPA. Kill S.2048 dead.\r\n[link\|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html\|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n

Welcome to IWETHEY!