When attempting to connect to Client machines from a Control or Tutor Console across the LAN/WAN directly using TCP, you may receive a “1704 error that the Client does not respond”.
This means there is a communication issue between the two machines. You will need to diagnose whether the Client and Control or Student and Tutor Console can communicate with each other. We recommend performing two tests from the Control to the Client machine:
- Ping test.
- PowerShell Test-NetConnection.
Performing a ping test
On the Control or Tutor Console machine, run the Command window as an administrator and enter ping followed by the IP address of the machine you are communicating to.
For example, ping 10.20.10.38
You will receive a response informing you if the packets sent from the Control machine to the Client are being received. A successful ping will show all the packets have been received. If this is unsuccessful this would suggest there is a connectivity issue between the Control and Client machine that will need to be resolved.
Using PowerShell to test the Port is available
To confirm whether the port the Client is listening on is open, you can use the PowerShell Test-NetConnection command.
Open PowerShell and enter Test-NetConnection -ComputerName -Port followed by the IP address of the machine and port that the Client is listening on.
Test-NetConnection -ComputerName 10.20.10.38 -Port 5405
If a connection is successful, it will show “TCPTestSuceeded: True”.
If the above fails, then this would confirm the the Client is not available on port 5405. Common reasons for this can relate to one of the following :
– A firewall blocking the port
– The Client not running
– The Client configured to run on a different port