TCP-Com Can’t Connect as Client to TCP/IP Server

If you are having difficulty connecting TCP-Com as a TCP/IP Client to a TCP/IP Server, there are a few potential causes. 

Try the following troubleshooting steps:

  1. Double-check that the IP Address and Port number for your TCP/IP Server are specified correctly in TCP-Com.
  2. Ensure that the TCP/IP Server is in a mode where it is listening for incoming TCP/IP connections. If the Server is another instance of TCP-Com (either on a different workstation or the same), make sure it is activated and “Listening” for connections.
    • Note: Some Serial Device Servers and laboratory balances can only accept one TCP/IP Client connection, in which case the Server will reject the connection attempt from TCP-Com if it is already connected to another client.

It is also possible that…

  • The TCP/IP Server may be behind a firewall blocking incoming connections to the TCP/IP Port. If this is the case, you’ll need to edit the firewall settings to allow client connections. We do not recommend fully disabling the Windows Firewall unless you are sure it is safe to do so.

The TCP/IP Server may not be located in the same network or subnet as the workstation running TCP-Com. To learn more about this and possible solutions, please see Connecting to a Serial or Networked Device Over the Internet.

Contact Us