- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2014 01:04 PM
I'm getting the following error while trying to run Discovery on a vCenter instance:
Unable to establish connection to https://x.x.x.x/sdk (where x.x.x.x is, of course, the real IP Address)
I can browse the url from IE on the MID Server, but just keep getting the error in the Discovery logs.
Any pointers?
Thanks
Solved! Go to Solution.
- Labels:
-
Discovery
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2014 12:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-05-2014 09:48 PM
Thanks Doug! Not sure why the .jar attachment file was missing, but this is EXACTLY the root cause why I was getting the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-12-2014 10:06 AM
Jason you would see that during a clone. For better or worse in a clone by default you don't move over large attachments.. and this .jar file is one of those large attachments...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-20-2017 11:05 PM
Hi Doug,
I am facing the similar issue of "Unable to establish connection to https://10.x.x.x/sdk" while discovering VCenter.
Could you please explain what you did exactly to solve this issue?
Thanks,
Sreejith
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2017 03:20 PM
Hello Aleck,
When i checked DNS name of a CI it have multiple Duplicated IP address Attached to it. Can i know is this normal to exist such duplicated IP address for a DNS name of a server.
If it is abnormal can you please let me know any way to overcome such duplicates in that table.
Thanks,
Niranjan.