"Browse Failure" when using separate backup network
In our newly rebuilt infrastructure i wanted to use a separated backup network for all the backup traffic, but getting a "Browse Failure / Access denied" message while loading the available selection from the agent.
BackupExec Server IP: 10.0.0.1 (Backup network)
Agent IP: 192.168.1.1 (LAN)
Agent IP: 10.0.0.10 (Backup network)
Agent FQDN: myhost.example.com
If i add the host with the LAN IP or FQDN, the selection list loads fine, but accesses the Agent through the firewall (which is properly configured).
If i add the host with the Backup Network IP, it works too.
But, i want to use an FQDN when adding the host. Would like to see the names of the server instead the IP address on the backp network.
So, i thought i will add a new DNS record, f.ex. "myhost.backup.example.com" which points to the IP of the backup network.
Now, if i use the new FQDN, i can add the host without problem, but, if i try to create a new backup for the host, i get this error:
Browse Failure Failure to browse 'myhost.backup.example.com'. Access is denied.
I compared the debug output when using the normal FQDN (through the firewall) with the output of the backup FQDN (same network) and found this difference:
- Informational: Restrict Anonymous Support is enabled - creating DLE for remote machine \\myhost.backup.example.com - legacy_MSNetCreateTempDLE() - Info: NetServerGetInfo() failed with error code: 5. Using GetVersionEx() to get the server information
The correct (i think) would be:
- Informational: Restrict Anonymous Support is enabled - creating DLE for local machine
Looks like it doesn't know the new FQDN because it doesn't matches the servers real hostname.
Any way to get this setup working with an FQDN somehow?
Thank you very much