vSphere Client accessibility can be impacted by indefinite loading during the authentication handshake. This document outlines steps to mitigate the underlying DNS and network connectivity failures.
root account.Step 1: Validate Network Connectivity
curl -v telnet://<vCenter FQDN/IP>:53Connection timed out" or "Failed to connect" confirm with the network administrator that Port 53 (UDP/TCP) is open between the appliance and the DNS server.root@VC FQDN[ ~ ] curl -v telnet://<DNS server IP>:53
Trying ##.##.##.##:53 ...* connect to ##.##.##.## port 53 from <vCenter IP> port 55788 failed: Connection timed out*Step 2: Verify Name Resolution
nslookup <FQDN> nslookup <IP_Address>server can't find" or time out, the DNS configuration requires correction.root@VC FQDN [ - ]# nslookup <vCenter IP>
;; communications error to ##.##.##.## 53: timed outVMware vCenter Server
This issue is typically caused by a DNS resolution failure. vCenter Server relies on Forward (A) and Reverse (PTR) DNS records to validate Service Principal Names (SPN) and SAML tokens during the SSO handshake. If DNS servers are unreachable or if Port 53 (UDP/TCP) is blocked by firewall rules, SSO service threads exhaust, preventing successful authentication.
/opt/vmware/share/vami/vami_config_netservice-control --restart vsphere-ui[Workaround] If immediate access is required while the above configuration takes time, append a static mapping to the host file on your local Windows system or jump box.
OS Drive:\Windows\System32\drivers\etc\.<vCenter_IP> <vCenter_Hostname>