The management console uses port 3000 (UDP) to broadcast and search for the IS. Port 5005 (TCP) is used for communication between the management console as well as the IS. Ports 137 (UDP), 138 (UDP), and 139 (TCP) are used for the IS and NS communication.

The following are additional TCP ports:

Management console listens at ports 1000-1009.

IS listens at port 5005-5014 and at ports 3000-3009 for broadcasts.

IS listens at 1921 and communicates at port 9921 for NetWare servers.

RPC listens to ports 3628 and 5168.

If these ports are open, would you be able to TELNET these ports from IS to remote NS?

Check if the TCP/IP filtering is enabled on the remote NSs.

Go to TCP/IP properties.

Check Options to verify if this is enabled or disabled. If it is enabled, check if the ports are open.

Edit the tmrpc.ini file to a value of 2.Each time an RPC binding wants to be created from an RPC client to an RPC server, the client will read the [DefaultProtocol] section of the TmRPC.ini file (located in the ServerProtect home directory) and then get the RPC server's value.

If the value is 1, named pipe is used to connect.

If the value is 2, TCP/IP is used to connect.

The TmRpc.ini file is used to record the communication protocol used in RPCFor example:

Geolocation Notification

Please approve access on GeoIP location for us to better provide information based on your support region.
If your location now is different from your real support region, you may manually re-select support region
in the upper right corner or click here.