Could not connect to the vCenter Server over the network

[Anonymous user]

Hi,

I am stuck at this error when configuring the network shutdown client (pcns v4.3) for VMWare

When the client is installed the initial configuration wizard pops up in the webinterface, there we choose for "Host managed by vCenter Server." and fill in the vCenter Server IP Address/Hostname, vCenter Server Username and vCenter Server Password.

Our vSphere Server version is 6.0, and it is installed on a dedicated physical machine.

The PCNS 4.3 is installed on a vMA and runs in our VMWare cluster.

The vCenter User has "Power On/Off" rights to the VM Cluster and I can logon to vCenter with this account.

Thanks
Tony

[BillP]

Hi,

What error are you seeing? 

1. Could not connect to the vCenter Server over the network.
2. Connection error due to invalid logon credentials.

Also, when entering the information are you entering vCenter Server IP or domain name? 

[Anonymous user]

Hi Bill,

I am getting the Could not connect to the VCenter Server over the network.  I've tried using the FQDN (vcenter-02.domain.local), hostname (vcenter-02) and the IP address (192.168.0.xxx).  I can logon to vCenter using the PCNS admin account I've created, which is a Virtual machine power user.

Tony

[Anonymous user]

Hi Bill,

I've checked the debug.log and have found the following:

2019-10-30T08:37:29,326 ERROR qtp2116584-126 com.vmware.vim25.ws.WSClient - Exception caught while invoking method: RetrieveServiceContent
java.net.UnknownHostException: qs-vcenter-02

qs-vcenter-02 is our vCenter server.  I can ping the server.  I have tried the Configuration Wizard a few times since and still get the same error, but it's not showing in debug.log.

Any Ideas

[Anonymous user · Accepted solution]

Issue sorted, it was an id10t error on my part.  Tried to use the IP address of qs-vcenter-02 and got invalid credentials (which I knew were correct) in the error.log.

I then remembered that our vCenter is not domain aware and changed the server name to domain\servername and the username to adminuser@domain.local and I've got past the error.

Thanks

Tony