Unable to access Vcenter

Question

Unable to access Vcenter

Kaushik Srinivas 20

Unable to access vcenter from jump machine. We verified if the fqdn is resolving from nslookup command and found out, it is successfully resolving.

Kindly need further assistance in resolving this.

Screen shots

image (2)

image (3)

Thanks & Regards

Kaushik

0 comments

1 answer

Your answer

Answer 1

From the provided information, we can see that the FQDN is resolving correctly via nslookup, which confirms that DNS resolution is working as expected. However, the browser error “ERR_CONNECTION_TIMED_OUT” indicates that the issue is likely related to network connectivity (Layer 4/Layer 7) rather than DNS.

Recommended next checks:

Validate basic network connectivity
From the jump machine, try: ping <vcenter FQDN/IP> Test-NetConnection <vcenter FQDN> -Port 443

This helps confirm if the host is reachable and if HTTPS (port 443) is open.

Check firewall / NSG / routing

Ensure outbound connectivity from the jump machine to vCenter on TCP 443 is allowed.
Validate if any firewall, NSG, or proxy is blocking the traffic path.
Connection timeout typically indicates packets are not reaching the destination (blocked or dropped). - https://learn.microsoft.com/en-us/azure/azure-arc/resource-bridge/troubleshoot-resource-bridge

Verify proxy configuration (if applicable)

Check whether the jump machine is configured with a proxy that might be blocking access.
Confirm proxy bypass rules for vCenter FQDN.

Test using IP instead of FQDN

Try accessing - https://<vcenter IP>
This helps isolate any remaining name resolution or certificate-related issues.

Validate vCenter service status

Ensure vCenter services are up and responding internally.
Try accessing vCenter from another machine within the same network segment to confirm if the issue is jump machine specific.

Kaushik Srinivas 20 Reputation points

2026-06-10T09:24:24.9133333+00:00

Dint work after retrying the suggested steps,

Recommended next checks:

Validate basic network connectivity, Verified by trying to ping other VC and worked fine, also checked trying to upload a document and download a document to drop box verifying connectivity has no issues.

From the jump machine, try: ping <vcenter FQDN/IP> Test-NetConnection <vcenter FQDN> -Port 443 Test-Net Connection to FQDN and ping to both FQDN and ip failed

Check firewall / NSG / routing

Ensure outbound connectivity from the jump machine to vCenter on TCP 443 is allowed, TCP 443 port is allowed as i am able to connect to another VC from the same jump machine

Validate if any firewall, NSG, or proxy is blocking the traffic path. No NSG, firewall or proxy is not blocking the traffic path

Verify proxy configuration (if applicable)

Check whether the jump machine is configured with a proxy that might be blocking access. No its not blocking access

Confirm proxy bypass rules for vCenter FQDN.

Test using IP instead of FQDN

Try accessing - https://<vcenter IP> not able to access vcenter with IP

Validate vCenter service status

Try accessing vCenter from another machine within the same network segment to confirm if the issue is jump machine specific. Tried from a different jump machine and the vcenter is not reachable.