Printable View
In XP Pro, there is no limit to the number of outbound connections to other network resources, but a single workstation is limited to hosting a maximum of 10 inbound connections.
Has anyone read about or found a workaround to this inbound connection limitation?
The only thing I've been able to find directly related to this is at Q314882 in the Knowledge Base.
The M$ folks have been doing that since NT3.x as I remember. They seem to want you to get a server version for >10 connections. Except that there isn't an NT5.1 server version in production right now (Windows .NET Server 2003 is up to RC-2 I think).
Assuming there was some sort of hack that would do the job, I think doing it would be a violation of the fine print in the XP license.
I had a feeling that was going to be the answer. Have to wait and see what .NET has to offer.
Thanks for the reply, Newt.
In you're talking about connections to shared network resources here then keep in mind that the limit applies to simultaneous active connections. Example: if you had 11 PCs networked and all tried to map to a particular drive at one time this would exceed the limit. However, if no more than 10 connected (or would be connected) to this same shared resource at a given time then there would be no problem. My point is simply that you could have more than 10 PCs in a network and whether there would be problems hitting the "limit" would depend on the access habits/patterns in regard to shared resources on a given computer.
In this particular case it's thirteen PC's trying to map to one. I didn't think the limit had been raised in XP, but I told him I'd ask here and find out for sure. I had no doubt the VirtualDr crew would have the answer readily available.Quote:
Originally posted by DrMDJ
keep in mind that the limit applies to simultaneous active connections.
Thanks for the reply, Dr.
13 PCs all mapping (at once)? Bummer! If only they could not maintain constant connections (mapping)...