topic Re: Unable to connect vcenter using powerCLI in VMware Remote Console Discussions

Unable to connect vcenter using powerCLI

NasirOm — Wed, 06 Oct 2021 14:20:56 GMT

I am trying to access the vcenter from powerCLI and getting the error "The hostname could not be parsed". The vcenter version is 6.7. Encountering the same error when trying with the ip or the FQDN.

Any ideas.

Thanks..

Re: Unable to connect vcenter using powerCLI

asajm — Thu, 07 Oct 2021 07:10:02 GMT

Hi @NasirOm

Check this maybe help

VIServer-Invalid-URI

Re: Unable to connect vcenter using powerCLI

NasirOm — Thu, 07 Oct 2021 07:31:49 GMT

Thanks.. For me i am not able to connect the vcenter even when just running the command Connect-VIserer -Server Servename:port

I checked the Vimuri in vcenter settings and it has the correct FQDN.

Re: Unable to connect vcenter using powerCLI

asajm — Thu, 07 Oct 2021 07:46:33 GMT

Are you tried with IP?

Re: Unable to connect vcenter using powerCLI

NasirOm — Thu, 07 Oct 2021 08:38:24 GMT

Yes i tried that too, getting the same error. i am able to access with fqdn and IP in vsphere web client. Only the powercli i am encountering the issue.

Re: Unable to connect vcenter using powerCLI

NasirOm — Thu, 07 Oct 2021 08:52:22 GMT

This is the error screenshot just in case you need more info.

Re: Unable to connect vcenter using powerCLI

asajm — Thu, 07 Oct 2021 08:58:26 GMT

Try to connect without HTTPS or port

Just FQDN "yourserver.yourdomain"

Re: Unable to connect vcenter using powerCLI

NasirOm — Thu, 07 Oct 2021 09:03:23 GMT

Without mentioning the port and https the error is could not resolve the requester Vserver and no endpoint listening. Port must be mentioned for a successful connection i guess..

i tried connecting with the port but removing the https and i am getting the same hostname could not be parsed error.

Re: Unable to connect vcenter using powerCLI

berndweyand — Thu, 07 Oct 2021 10:05:19 GMT

if nslookup <vcenterFQDN> resolves correct then "connect-viserver <vcenterFQDN> " should work.

connect-viserver <ip> should work always

Re: Unable to connect vcenter using powerCLI

NasirOm — Mon, 11 Oct 2021 07:08:52 GMT

nslookup is working fine... but connect-viserver is not working.. I tried in various machines but still the same issue.

Re: Unable to connect vcenter using powerCLI

berndweyand — Mon, 11 Oct 2021 07:19:10 GMT

what powercli-version do you have ? ("get-module vmware*" or "get-powercliversion")

what is your actual error when trying to connect?

Re: Unable to connect vcenter using powerCLI

NasirOm — Mon, 11 Oct 2021 07:25:30 GMT

Powercli version is 12.4.0. Please see the screenshot of the error below.

Re: Unable to connect vcenter using powerCLI

berndweyand — Mon, 11 Oct 2021 07:36:58 GMT

did you really read the previous posts ?

try "connect-viserver <yourvcenterfqdn"

NO LEADING https, NO TRAILING port, just fqdn!

Re: Unable to connect vcenter using powerCLI

NasirOm — Mon, 11 Oct 2021 08:10:44 GMT

Yes i read and i replied after trying.. i am getting the below error without port and https .

Could not resolve the requested VC server.
Additional Information: There was no endpoint listening at https://fqdn.com/sdk that could accept
the message. This is often caused by an incorrect address or SOAP action

Re: Unable to connect vcenter using powerCLI

berndweyand — Mon, 11 Oct 2021 08:23:07 GMT

to eliminate dns problems try with "connect-viserver x.x.x.x"

Re: Unable to connect vcenter using powerCLI

NasirOm — Mon, 11 Oct 2021 08:28:18 GMT

Sorry i should have mentioned in my previous post.. I tried with just IP also without port and https and i am getting the same error message in my previous reply.

Just for your information, i am not using the default port for the vcenter connection. That is the reason i am entering the port number while trying to connect.

Re: Unable to connect vcenter using powerCLI

berndweyand — Mon, 11 Oct 2021 08:35:36 GMT

ok thats a brand new info - then try connect-viserver x.x.x.x -port yyy

Re: Unable to connect vcenter using powerCLI

NasirOm — Mon, 11 Oct 2021 09:29:49 GMT

Thanks.. Found what i was doing wrong.. i was typing x.x.x.x:portnumber instead of what you suggested.. Thanks a lot friend. Kudos...

So it should be fqdn -port yyy or x.x.x.x -port yyy.