Did you also check ReverseDNS for vCenter and Networker (NMC) Server? It is really frustrating but often forward DNS and reverse lookup DNS are the main failures of nit getting a client / system added.
I'd agree on that one, check name resolution on Networker server (FQDN, short name, IP), ensure you are using DNS and not hosts tables as I believe there are some security "enhancements" that validate against DNS these days...
PatricJ
1 Rookie
•
68 Posts
0
March 29th, 2017 06:00
Did you also check ReverseDNS for vCenter and Networker (NMC) Server? It is really frustrating but often forward DNS and reverse lookup DNS are the main failures of nit getting a client / system added.
DavidHampson-rY
294 Posts
0
March 29th, 2017 07:00
I'd agree on that one, check name resolution on Networker server (FQDN, short name, IP), ensure you are using DNS and not hosts tables as I believe there are some security "enhancements" that validate against DNS these days...
dhbennett
3 Posts
0
April 4th, 2017 12:00
I am having the same issue. I can connect my 6.5 Windows-based Vcenter but not the 6.5 VCSA. Name resolution appears to work fine.
bingo.1
2.4K Posts
0
April 10th, 2017 07:00
I just went through the connection to the VCSA last week using NVP 2.0.1-2 - without anyissue.
If the name resolution is fine then I expect a firewall and/or an account issue.