1.Troubleshooting using telnet:
- For Windows Server 2000/2003 Backup Exec Servers.
To test the connection between the backup server and the remote server, enter the following at a command prompt on the media server:
telnet servername 10000
For Windows Server 2008, the telnet client will need to be installed before running the telnet command. Refer to Microsoft article :
i.Example telnet output: Open port by another application.
Fig. 1 shows a telnet connection to the remote server has been established successfully, but no non-standard characters are returned, showing the port is open, but not by Backup Exec for Windows.
Fig. 1
ii.Example telnet output: Port not open or in use.
Fig. 2 shows a telnet connection to the remote server has failed, showing the port not in a LISTENING state.
Fig. 2
2.Troubleshooting using netstat:
To view the ports, process, and IP currently in use on the remote server, use the following command on the remote server:
netstat -anb > c:\netstat.txt
- This will list the port and process that is using the port to a text file on the C:\ drive. If another destination is preferred, simply change the drive letter and file name.
This will list the server name and port to a text file on the C:\ drive. If another destination is preferred, simply change the drive letter and file name.
Review the netstat.txt for port 10000 to confirm if the process is beremote and the state is LISTENING
Workaround:
- The Backup Exec remote agent requires port 10000 by default to send and receive connections with Backup Exec for Windows server.
Beremote.exe should be the only process using port 10000 and the state of the port should say LISTENING in the netstat log. If any other application has been assigned port 10000, the above error will occur.
- If an alternative port for beremote.exe is required, refer to article below on how to change the port being used for the remote agent process:
https://www.veritas.com/docs/000025920