- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @NasirOm
Check this maybe help
Marking this response as "Solution " or "Kudo"
ASAJM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you tried with IP?
Marking this response as "Solution " or "Kudo"
ASAJM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
This is the error screenshot just in case you need more info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try to connect without HTTPS or port
Just FQDN "yourserver.yourdomain"
Marking this response as "Solution " or "Kudo"
ASAJM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
if nslookup <vcenterFQDN> resolves correct then "connect-viserver <vcenterFQDN> " should work.
connect-viserver <ip> should work always
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
nslookup is working fine... but connect-viserver is not working.. I tried in various machines but still the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
what powercli-version do you have ? ("get-module vmware*" or "get-powercliversion")
what is your actual error when trying to connect?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Powercli version is 12.4.0. Please see the screenshot of the error below.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did you really read the previous posts ?
try "connect-viserver <yourvcenterfqdn"
NO LEADING https, NO TRAILING port, just fqdn!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
to eliminate dns problems try with "connect-viserver x.x.x.x"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ok thats a brand new info - then try connect-viserver x.x.x.x -port yyy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.