"Server could not be located" when adding a server to NOM (multiple network cards)
Updated: 02 Mar 2009
I was recently playing with NBU 6.5 and NOM (NetBackup Operation Manager) 6.5 (no patch on either) on a pair of Windows (2003 SP1) servers which have multiple public networks (one for the clients / data, and one for iSCSI).
After setting up NOM and being able to login, wasn't able to add my Master server to the NOM server (which is a separate Media server). Get the generic:
Server "servername" could not be located. Make sure the server is reachable on the network and NetBackup is running.
Went through and checked nslookup, ping, and bptestbpcd (bpclntcmd), and one thing I found was that the bptestbpcd was sometimes coming back with the iSCIS network IPs instead of the public IPs.
Under Windows' Network Connections window, under Advanced->Advanced Settings and on the Adapters and Bindings tab found that the binding order had the public network card last. Moved that to the top of the list, and then was able to add the Master server without issue.
Posting this in case it helps someone else.
discussion Filed Under: