...
Below are the steps to troubleshoot Port Socket Error:
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.
Attempt to ping the panel over the specified IP address
...
If this is successful, move to the next step
If this fails, ensure the network connection is set between the controller and Workstation
...
Disable and Reenable Key Components
...
Disable the Port, XBox, and Controller
...
.
...
While the port is disabled in Velocity, try to communicate to the panel over the default TCP port 10001 (unless otherwise specified).
| Code Block |
|---|
TNC <SNIB3_IP_Address> -port 10001 |
...
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.
...
You may need to reset encryption with the controller. See the steps below to reset encryption.