Hi guys - hopefully someone can me help out on this one:
As far as I know there is an upper limit to the maximum number of concurrent network connections allowed by windows 10 (pro in my case) of twenty. Now I understand this effectively requires you to run Windows Server for file serving etc puposes. In our case, however, we pull all texture data, caches etc. off a Linux server with no relevant maximum connection limit when rendering. Only our license servers run off a windows 10 pro machine, ie. VRay, Autodesk etc.
Now, how does this relate to the above connection limit - is that techincally different from connections invoked by file transfers etc., or does windows 10 lmit us to 20 rendernodes querying licenses off the windows 10 computer? If the second is the case, ie. it is the same as file transfers - doe the license querys count as one open connection per rendernode or could one node use up 2 for each license service, effectively limiting us to ten render nodes?
Any help is greatly appreciated, cheers,
j
max concurrent connection limit on windows 10 / license servers
It’s a possibility that I am way off base on this, but I believe the “connection” limit for Windows 10 would be related to its’ RPC connection capability. In other words, how many file shares or concurrent other Windows users are allowed to simultaneously connect.
If you have a 3rd party software running as a service, say under port 9999, and it was serving some type of license traffic. I “do not” believe it would count against your Windows services.
This is just a thought on my part on how I understand it works. It would be very easy to test though through a sim. How I would do that would be to setup a FTP or fake web service, and have another machine(s) to a stress test with opening hundreds of connections on whichever port I created for testing. This doesn’t exactly mimic a 3rd party license service like Autodesk, but would give you a quick idea if it might work or not.
That 10 limit should just be for windows file and print sharing, any other service should be allowed to freely run. You’ll need to turn off the windows sharing to lose the nagging warning messages though.
What Mash said. I used Windows Pro versions for many small server purposes where they handled hundreds of connected users, just not for file and print services but own databases.