I run Vista 64 Ultimate and used to think I was a decently experienced programmer. I have a trading application that requires I have the UI on one computer and the main process code possibly (but not necessarily) on a second computer.
Tcp seemed the best way to accomplish this because at some point the second computer may not run windows. While I am no Tcp expert, I am not a complete novice and the code works when the applications are on two different computers (either on my local network or over the internet).
Additionally, if the two applications are on the same machine using the 127.0.0.1 loopback, they connect fine, the server can send test messages to the client exactly like one would expect but when the cliend sends a message to the server, it can take literally ten minutes for the complete message to arrive (this is using a 10 byte message). Thinking this had to be my code, I have copied and compiled Dev Studio sdk code, even found three different sample Tcp client server applications and they all exhibit the exact same behavior.
I have even run both the client and server as admin with the same results. It can't (famous last words) be a hardware issue because the packets never even hit the network (I used WireShark to verify this) so that seems to point to a rights issue or something related. Any suggestions?
Tcp seemed the best way to accomplish this because at some point the second computer may not run windows. While I am no Tcp expert, I am not a complete novice and the code works when the applications are on two different computers (either on my local network or over the internet).
Additionally, if the two applications are on the same machine using the 127.0.0.1 loopback, they connect fine, the server can send test messages to the client exactly like one would expect but when the cliend sends a message to the server, it can take literally ten minutes for the complete message to arrive (this is using a 10 byte message). Thinking this had to be my code, I have copied and compiled Dev Studio sdk code, even found three different sample Tcp client server applications and they all exhibit the exact same behavior.
I have even run both the client and server as admin with the same results. It can't (famous last words) be a hardware issue because the packets never even hit the network (I used WireShark to verify this) so that seems to point to a rights issue or something related. Any suggestions?