Vcenter Discovery Error - error when accessing the SDK URL at https://servername/sdk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2023 12:31 AM
Hi ,
I have been encountering an error while discovering one of my Vcenter. Below is the Error Message :
1. Cannot connect, status is SSH_PROTOCOL_FAILURE. Received server DISCONNECT message: DISCONNECT: code: 2, reason: Protocol error, description: Too many authentication failures
2. Unable to establish connection to https://10.199.104.100/sdk: java.rmi.RemoteException: Exception caught trying to invoke method RetrieveServiceContent; nested exception is:
java.net.SocketException: Connection reset
3. Timeout trying to read from https://10.199.104.100/sdk
I have checked for firewall blocks and server MTU and all are good. VmWare admin says its not a server issue and share me a KB from VMware which says /sdk will not be accessible as it is not an HTML link.
I have also verified the credentials and it works fine accessing /mob but not /sdk.
VMware KB -- Informational: Expected error when accessing the SDK URL at https://servername/sdk (1003218) (vmware...
Please advise.
- Labels:
-
Orchestration (ITOM)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2024 11:45 PM
We are getting the same issue in our environment.Could you please tell me how you fixed the issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2024 11:51 PM
Hi Usha,
We identified an issue with the credentials used to discover the vcenter.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2023 06:24 PM
Hi everyone,
I'm facing the same issue and haven't made much progress. Has anyone encountered this before and could share the steps to resolve it? Your assistance would be greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2024 11:51 PM
You may want to verify the credentials used for windows discovery. That was the issue in my case.