> Erm.. aren't client and server supposed to be using the same port?
No. The client and server sides of a TCP connection can be on different ports. For example connecting an ftp client to an ftp server: The remote server is listening on port 20 but the client will locally use some random, high port like 15443. And you could have the client and server on a single machine.
But the thought I originally had for your deal was that only one process should be listening on one port per machine. It should be exclusive access, one port, one process. If, for example, two processes are listening on port 3090, which one responds to a connection request or data transfer? I don't know your client-server interactions - is it possible that they're both trying to connect to each other over the same port?
But this theorizing doesn't explain why it works for you in debug mode. !!??
Paul
No. The client and server sides of a TCP connection can be on different ports. For example connecting an ftp client to an ftp server: The remote server is listening on port 20 but the client will locally use some random, high port like 15443. And you could have the client and server on a single machine.
But the thought I originally had for your deal was that only one process should be listening on one port per machine. It should be exclusive access, one port, one process. If, for example, two processes are listening on port 3090, which one responds to a connection request or data transfer? I don't know your client-server interactions - is it possible that they're both trying to connect to each other over the same port?
But this theorizing doesn't explain why it works for you in debug mode. !!??
Paul