Problem in Running the Winsock Client and Server Code Sample

Question

Hello, Microsoft team.
I'm glad I have a chance to ask the Microsoft development team questions.
So, basically, I'm an IoT Engineer, and right now I am doing a project related to sending data (video stream and frames) by using socket.
So. I tried to run the Winsock Client and Server Code Sample from Microsoft documentation.
I didn't encounter any error in compiling both programs but when I tried to execute, the server and then the client, the server's program is not executed anything and the client's program just couldn't be executed,

this is the message from the Client's program when I tried to execute
'usage: C:\Users\project\x64\Debug\project.exe server-name'

This is the output when I executed the server's program.
]1

Do you have any idea on how to solve these issues?

Answer 1

Hi @Bill Son Makmur ,

I tested Complete Winsock Client/Server Code, the picture you uploaded should be the result from Winsock Server Code. This behavior is normal and means that the code is executing as expected. After the breakpoint we can see that the value of iResult is 0, and then observe the code:

 if (iResult != 0) {  
 printf("getaddrinfo failed with error: %d\n", iResult);  
 WSACleanup();  
 return 1;  
 }  

Only output if iResult is not equal to 0.

Similarly, for functions such as socket in the subsequent code, you could enter their documentation by pressing F1 on them. We can clearly find that there is no statement output because neither ListenSocket nor iResult meets the judgment condition of if().

Best regards,

Elya

---

If the answer is the right solution, please click "Accept Answer" and upvote it.If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

As long as the client and server are on the same computer the client can be started using "client.exe localhost". And what you see is the server waiting for a connection.