Using a VB.NET app I wrote, I can use a TCPListener to connect to another networked app, and upon connection, I receive a new port, as expected. The communication works from there.
In Xojo, using TCPSocket.Listen, I can connect to the networked app, but the port I get back is the same port I was listening on. (50000)
When using TCPSocket.Connect instead of TCPSocket.Listen in this same app, and connecting to a hardware device (instead of a networked app), the port always comes back after connecting with a new port #, not 50000 and all is well.
For some reason, when using TCPSocket.Listen, the port it comes back with is always the same port I'm using to listen. Same issue on both Mac and Windows.
Anyone ever run into this issue before?