Spider Ethernet running today’s SDK.
I am now able to get 33 sockets running. Thirty two inbound connections and a listening thread.
If I try to start another connection, after the 33 sockets are in use, the Connect()
eventually timeout and results in an error on the client PC.
If I kill one of the 32 connections, I can start a replacement connection.
Wasn’t today’s update supposed to bump that to 128?
Wow this is surprising! We did change the network profile for sure!! We will look into it on Monday.
Yes, but it has been increased by one. Might be another issue.
That is not possible to go by one. Something is very strange!
Yes. I might be wrong about the one additional, but I don’t think so.
It appears that the current version only allows 32 inbound calls to be active. Perhaps
there is another constant for the maximum number of simultaneous inbound calls that is the
limiter? Or maximum TCP sockets?