How do I fix Port Socket Error?

Owned by Hadden Grant
Last updated: Jul 25, 2024 by Eduardo Bahena
1 min read

Velocity connects to the Port IP Address provided within Port Properties and makes a socket connection via the specified port. If Velocity fails to establish the socket connection on that port, you will get port socket error.

Below are the steps to troubleshoot Port Socket Error:

  1. Ensure you are troubleshooting from the Velocity Server or Velocity standalone workstation. This would be the Velocity machine running the Velocity Digi*Trac Network service.

  2. Attempt to ping the panel over the specified IP address.

Successful PING

  1. While the port is disabled in Velocity, try to communicate to the panel over the default TCP port 10001 (unless otherwise specified). Use the following PowerShell command.

TNC <SNIB3_IP_Address> -port 10001
image-20240725-141923.png

In the above example I am able to ping the SNIB3, but I cannot reach the device over TCP port 10001. Below are the possible reasons you cannot reach the SNIB2/SNIB3 over your specified TCP port.

  • The SNIB2/SNIB3 is programmed with a different TCP port number other than 10001. Please connect to the SNIB2/SNIB3 with the SNIB Hunt and Configure tool to review and change the TCP port.

  • Firewall settings are not allowing traffic on the specified TCP port

  • Smart switch or router not allowing TCP traffic over specified port.

  • SNIB2/SNIB3 is holding on to the previous socket connection. Please make sure Velocity states ‘Port Shutdown Completed' when successfully disconnecting from the panel. Please make sure there is no other Velocity system is making a connection this panel.

  • Duplicate IP address. There may be another device in your network sharing the same IP address as your SNIB2/SNIB3.

5. Once the network related issue has been corrected. You should now be able to reach the SNIB2/SNIB3 over your specified port.

  1. You may need to reset encryption with the controller. See the steps below to reset encryption.