A road named NoNameUno

So I started firing the client from host, and found connection failure. On the command line it says "Failed to connect". Hmm time for some debugging now !!!.

Started the wireshark on both machines. In the past I used sysinternal tools ( bought it ) TcpPro and I used the Microsoft's network monitoring tool, but once in a while I go to Linux development world so wireshark is best for me, and since its inception as Ethreal, it has improved a lot. I can capture some telephony or voice traffics with it...

Then fireup again and see 3 SYN packet going from the client to the server. Off hand I don't know where is the setting for number of retries, but I sure know that there should be SYN+ACK from the receiving end, and then there is the ACK from sending side to complete the 3-way handshake. Hmm, no clue why 3 SYN and it is showing in the receiver side too, so sounds like network is working fine... 

So my first thought was to start the tracelogging of wsk echoserver. And found that nothing has been logged. If you are here, and never tried the trace logging I strongly recommend you to read the installation notes of wsk echoserver and use it. Very simple to use the basics.

 Before I try to concentrate on debugging the actual problem, I thought I should be ready with the tracing otherwise it could be a long process. So my next step was to start the user level client from the target machine and use the localhost ( 127.0.0.1) interface. The client worked, meaning what back what it sent, no connection failure... And I've a nice trace from the wsk server.

So the question now is why the packets are showing up at the otherend ( that is what wireshark on the receiver side is showing ), and still connection is not being setup properly....