vCenter UI stays in login screen due to DNS issue
search cancel

vCenter UI stays in login screen due to DNS issue

book

Article ID: 425999

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

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.

  • vSphere Client interface displays a continuous loading or spinning icon.
  • The login does not time out or provide an immediate error message.
  • Access via SSH and the VAMI (Port 5480) may still work using the root account.

Step 1: Validate Network Connectivity

  1. Log in to the vCenter Server Appliance (VCSA) via SSH using root credentials.
  2. Execute the following command to test connectivity to the DNS server on Port 53: curl -v telnet://<vCenter FQDN/IP>:53
  3. If the output indicates "Connection 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.
    Output:
    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

  1. Perform forward and reverse lookup tests: nslookup <FQDN> nslookup <IP_Address>
  2. If commands return "server can't find" or time out, the DNS configuration requires correction.
    Output:
    root@VC FQDN [ - ]# nslookup <vCenter IP>
    ;; communications error to ##.##.##.## 53: timed out

Environment

VMware vCenter Server



Cause

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.

Resolution

  1. If the DNS servers configured on the vCenter are incorrect, outdated, or have been decommissioned, you must point the appliance to servers that are functional following below instructions:
    1. SSH to vCenter as root user.
    2. Run the VAMI network configuration parameter /opt/vmware/share/vami/vami_config_net
    3. Select option 4 (DNS) 
    4. Update the Primary and/or Secondary DNS server IPs to valid, reachable servers.
    5. Exit and restart the vSphere UI service to clear cached sessions: service-control --restart vsphere-ui
  2. If the vCenter configuration is correct (pointing to the right servers) but the tests still time out, you must coordinate with your AS/DNS team to ensure that both Forward (A) and Reverse (PTR) records exist for the vCenter's FQDN and IP address.

[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.

  1. Open Notepad as Administrator
  2. Navigate to OS Drive:\Windows\System32\drivers\etc\.
    Note: Change the file type dropdown (bottom right) from "Text Documents (.txt)" to "All Files"
  3. Open the hosts file and add a new line at the bottom: <vCenter_IP> <vCenter_Hostname>
  4. Save the file.