Backup of a remote server fails with error: 0xe0000f02 - The media server could not connect to the remote computer. The remote computer may not exist on the selected subnet, but the option to use any available network route was not selected.
The media server could not connect to the remote computer. The remote computer may not exist on the selected subnet, but the option to use any available network route was not selected. Try selecting an alternative network interface, or allow Backup Exec to choose any available network interface.
The following error is displayed in the job log :
The media server was unable to connect to remote machine SERVER1 using selected subnet: 0.0.0.0
The backup of a remote Windows server fails with the above-mentioned errors if the Backup Exec (tm) server has multiple network interface cards (NIC) and the backup job is configured to use a specific NIC card.
The two NIC cards on the Backup Exec (tm) server may have different subnet masks.
To resolve this issue, the vxmon on the remote server should be configured to advertise using the IP on the NIC for backup.
To advertise a remote server to a media server, perform the following:
1. Browse to C:\Program Files\Symantec\Backup Exec\RAWS.
2. Open vxmon.exe (Figure 1).
3. The vxmon creates an icon in the system tray. Right-click on the vxmon icon and select Options (Figure 2).
4. Click on the Publishing tab select Enable Remote Agent advertising then click Add and type the IP address of the media server (Figure 3).
5. Now the Remote Agent will advertise itself to the media server only to the specified IP address. It can be configured to advertise on multiple Backup Exec servers.