vSphere Client Problem

[stmux]

vSphere 6.5 (Testing HTML client before updating from ver 5.5)

Currently accessing vCenter Server (Windows 2012r2) with vSphere Web Client Version 6.5.0.10000 Build 5973321

vCenter Client Appliance installed on above vCenter Server

From esxi6.5 About Screen logged in with Firefox as root:

Client version: 1.21.0

Client build number: 5724747

ESXi version: 6.5.0

ESXi build number: 6765664

vSphere Web Client Appliance - 3.30.0.0 Build 7271216

The appliance installed and started with no errors.  I am able to root into the appliance and make changes.  I am able to root into the esxi server via web browser using url shown in the esxi host screen and a nslookup for https://appliance.domain.com returns the correct ip address, 192.168.0.202, so DNS is working properly.  However, I cannot get the vSphere Client to come up.  When I enter https://appliance.domain.com:9443/ or https://192.168.0.202:9443 I get "Unable To Connect" Firefox can’t establish a connection to the server at 192.168.0.202:9443 .

I would appreciate any guidance or suggestions ,

Thank you,

jay

[daphnissov]

Do you get a webpage at https://appliance.domain.com ?

[stmux]

No web page only the following error, "Unable To Connect" Firefox can’t establish a connection to the server at 192.168.0.202:9443 .

[daphnissov]

So 202 is your vCenter. Can you ping that IP? If yes, do you possibly have an IP conflict on your network? Disconnect the vNIC on vCenter to verify. If all that's good, check firewall on your Windows box. Login locally to it and see if you can pull up https://localhost.

[stmux]

"So 202 is your vCenter. Can you ping that IP? If yes, do you possibly have an IP conflict on your network? Disconnect the vNIC on vCenter to verify. If all that's good, check firewall on your Windows box. Login locally to it and see if you can pull up https://localhost."

Yes, vCenter runs on Server 2012r2.  The vCenter Server ip address, 192.168.0.233 (Static), can be ping'd from anywhere on the network.   I checked the router and there are no conflicts with ip addresses.  https://localhost on the vCenter Server brings up the vSphere Client and I can login.  I have been using the appliance url and ip address, 192.168.0.202, to access the vCenter Client from the network.  I tried using the vCenter Server ip address, https://192.168.0.233 without the port number and the vCenter Client login page comes up.  However, it is refusing the same login I used directly on the vCenter Server to access the vCenter Client.  Any clue why that might occur?

jay

[daphnissov]

I have been using the appliance url and ip address, 192.168.0.202, to access the vCenter Client from the network.

Hang on, I'm confused here. If your vCenter is 192.168.0.233 what is the 202 address?

However, it is refusing the same login I used directly on the vCenter Server to access the vCenter Client.

Can you explain and illustrate what exactly you mean? What login are you trying? Feel free to post copious screenshots if you'd like.

[stmux]

I'm sorry, 192.168.0.233 is the esxi 6.5 host ip address.  192.168.0.202 is the VCSA ip address.  So, when I login directly to the 233 address with the vCenter Client I see both of those ip addresses under summary.and the About shows vSphere Client Version 6.5.0.10000.  It's good news to know that the client is working from the VC Server but I need to get it working from the network.  Hope this makes more sense now.

jay

[stmux]

I finally got it working on the network by directing the browser to the vCenter Server ip address which I was confusing with the host address.  Your help is greatly appreciated.

Thank You!

jay