Symptoms
The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. When attempting to register a new vProxy in the NetWorker Management Console (NMC), it fails with login and connection errors.
160859:nsrvproxy_mgmt: vProxy management job started with CLI: 'C:\Program Files\EMC NetWorker\nsr\bin\nsrvproxy_mgmt.exe register -s [NetWorker Server] -v [vCenter Server] -h [vProxy] -p 9090 -j 13 -k 0 '
161332:nsrvproxy_mgmt: Starting '[vProxy]' vProxy registration to '[NetWorker Server]' NetWorker server.
197027:nsrvproxy_mgmt: NW server IP/hostname not enforced during registration.
NSR VMware proxy resource on '[vProxy]' deleted.
161327:nsrvproxy_mgmt: Failed to register vProxy '[vProxy]': Received an HTTP code: 500, libCURL message: "", vProxy message: "Error received from vProxy ="500: Unable to log in to vCenter '[vCenter Server]': Post https://[vCenter Server]/sdk__;[vCenter Server]: dial tcp: lookup [vCenter Server] on [::1]:53: read udp [::1]:37612->[::1]:53: read: connection refused".
Cause
The vProxy cannot resolve the vCenter name because it is not configured with a proper DNS.
Resolution
Edit the vProxy /etc/resolv.conf file to include a proper DNS that can resolve the NetWorker Server, vCenter Server, and Data Domain. DNS is configured during deployment of the vProxy appliance. You can also manually reconfigure the network/DNS settings by following: NVP vProxy: How to manually change the vProxy Appliance network interface settings
