It appears that Backup Exec 2014 running on my Server 2012 machine is having problems resolving the FQDN of some Hyper-V virtual machines. For example, if I right-click on my Server 2012 Hyper-V Host and select "Install Backup Exec Agent for Windows to Guest Virtual Machines", I eventually get this.
Note that Oasis, Safehouse, and USSBAFM01 do not have a host name in parentheses. I think this means that Backup Exec was unable to resolve the FQDN for that particular machine. Note that Support2 is in our DMZ and is domainless, yet it was resolved and I was able to push-install the Backup Exec Agent for Windows on it no problem. Now if we continue, we get the following error.
I'm not sure what the issue that Backup Exec is having because all three of these machines have no problem with address resolution. "nslookup oasis" returns the FQDN and IP address, and so does "nslookup IP address". File and Printer Sharing is enabled on all three. I've installed the Backup Agent for Windows on all three machines using the DVD ISO. I can actaully join these servers to Backup Exec 2014 by manually using the Add Servers and Virtual Hosts button and entering the FQDN. But when I do that, Backup Exec knows these are VMs, however, it doesn't seem to link them to the proper virtual host.
If I run a test/edit credentials test on the host, I get the following. Note that even though it is flagging an error, there is a green checkbox next to each of these, implying that something passed.
Between these three machines, there are some commonalities. I recently migrated all 3 machines from a 2008 R2 Hyper-V host to a 2012 Hyper-V host. All 3 machines are 2008 R2 servers.
About a year ago, I did a similar migration on USSBADCG01 and as you can see in the snips above, it seems to have made it okay.
Other things I have tried including flushing the DNS cache on the Backup Exec server and deleteing/re-adding the virtual ethernet adapter on the VM. I've also tried enabling/disabling NetBIOS.
Any hints are appreciated. Thanks in advance!