Unable to login to vCenter server, launching the vSphere client option gives the error "Authentication failed for one or more vCenter Server systems:https://FQDN_or_IP_of_vCenter:443/sdk"

Products

• VMware vCenter Server
• VMware vCenter Server 8.0

Issue/Introduction

• When logging into the vCenter Server via the vSphere Client, the login process stalls after entering credentials and does not proceed. In some cases, the Launch vSphere Client option may display an error or fail to load entirely.

"Authentication failed for one or more vCenter Server systems:https://FQDN_or_IP_of_vCenter:443/sdk"

• Log snippets from /var/log/vmware/sso/websso.log has the following error:

YYYY-MM-DDTHH:MM:SS WARN websso [45: tomcat-http -- 7] [CorId=###################################c] [com. vmware. identity. idm. server. provider. activedirectory. ActiveDirectoryProvider] obtainDcInfo for domain [AU] failed Native platform error [code: 9502][DNS_ERROR_BAD_PACKET] [A bad packet was received from a DNS server. Potentially the requested address does not exist. ]
YYYY-MM-DDTHH:MM:SS WARN websso [45: tomcat-http -- 7] [CorId=###################################c] [com. vmware. identity. idm. server. provider. activedirectory. ActiveDirectoryProvder] obtainDcInfo for domain [AU] failed Native platform error [code: 9502] [DNS_ERROR_BAD_PACKET] [A bad packet was received from a DNS server. Potentially the requested address does not exist. ]
YYYY-MM-DDTHH:MM:SS WARN websso [45: tomcat-http -- 7] [CorId=###################################c] [com. vmware. identity. idm. server. provider. activedirectory. ActiveDirectoryProvider] obtainDcInfo for domain [AU] failed Native platform error [code: 9502] [DNS_ERROR_BAD_PACKET] [A bad packet was received from a DNS server. Potentially the requested address does not exist. ]
YYYY-MM-DDTHH:MM:SS WARN websso [45:tomcat-http -- 7] [CorId=###################################c] [com. vmware. identity. idm. server. provider. activedirectory. ActiveDirectoryProvider] obtainDcInfo for domain [AU] failed Native platform error [code: 9502] [DNS_ERROR_BAD_PACKET] [A bad packet was received from a DNS server. Potentially the requested address does not exist. ]

• vCenter server was not DNS resolvable. Both nslookup of FQDN and IP address of the vCenter server gives communication timed out error.
• Validate the entries in dnsmasq.log under /var/log/vmware/ for any DNS discrepancies 

Environment

VMware vCenter Server 7.x

VMware vCenter Server 8.x

Cause

This issue arises due to either the unavailability of the configured DNS server within the vCenter Server environment or the incorrect configuration of the DNS server itself.

 

Resolution

1. Validate the current DNS configuration using the command in SSH of the vCenter server: /opt/vmware/share/vami/vami_config_net
2. Use option 0 to show the current configuration
3. Use option 4 to change the DNS server; add the primary and secondary server DNS IP
4. Login to vCenter server UI

Kindly refer the KB Update DNS Server IP address for vCenter Server to update the DNS server IP via VAMI and command line