We are having a problem with one of our servers connecting to the BUE server.
The BUE server has 2 NICs; one connecting to the xxx.xxx.21.x subnet, and one other connected to our tape LAN on a 192.168.x.x subnet. The servers that are being backed up are on the 21 subnet. The server in question is on the xxx.xxx.228.x subnet. The firewall allows connections on all appropriate ports between the 21 and 228 subnets for the backups to happen, hence that is not the problem. The server on the 228 subnet fails it's backup when the NIC connected to the tape LAN is enabled. I've watched the transactions through the firewall when the Tape LAN NIC is disabled, and everything works fine, but as soon as I re-enable the Tape LAN NIC, the job fails and no connections are made. Sometimes it will make a few connections, but not the necessary port 10000 connection. I have set the backup job to use the appropriate network card in the network category of the job, but it still fails as soon as the Tape LAN NIC is enabled, even though I've specified that the backup server should specifically use the xxx.xxx.21.x NIC (not the Tape LAN NIC)
Here is a copy of the error I get when the job fails when the Tape LAN NIC is enabled. The job is successful when the Tape LAN NIC is enabled:
"Credentials CheckDevice : \\SOVPER-PAYROLL, \\SOVPER-PAYROLL\C:Check status : Error: a000846b, The job failed with the following error:
Device could not be backed up because an error occurred while connecting to the Remote Agent for Windows Servers.
Make sure that the Remote Agent for Windows Servers is running on the target computer."
The BUE Remote agent is installed and running on the remote server. I checked.