cancel
Showing results for 
Search instead for 
Did you mean: 
nagaeendra
Flexera beginner

Re: Fail to run discovery on VMware vCenter

Hi @stefangeerars 

Yes, verified SchUseStrongCrypto it is set to dword:00000001

No TLS 1.0 and TLS 1.1 are set to enable.

should SSL 2.0 and 3.0 be enabled or disabled.

Thanx

0 Kudos
stefangeerars
Occasional contributor

Re: Fail to run discovery on VMware vCenter

Try adding the registry key

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]"DefaultSecureProtocols"

with value: dword:00000200

Stefan

0 Kudos
Moderator mgunnels Moderator
Moderator

Re: Fail to run discovery on VMware vCenter

Question, Is the certificate on the vCenter server still valid?

0 Kudos
nagaeendra
Flexera beginner

Re: Fail to run discovery on VMware vCenter

Hi @ mgunnels 

Yes, certificate on vCenter is valid. though root certificate authority are different between these 2 server (vCenter & FNMS server) 

0 Kudos
Highlighted
nagaeendra
Flexera beginner

Re: Fail to run discovery on VMware vCenter

Hi @stefangeerars 


Checked by adding dword:00000200
Doesn't throw me SSL error now by doesn't do discovery also
But  on ESXquery I see  
" Decryption operation failed 
In fsend call to WinHttpSendRequest : A connection with the server could not be established (12029) 
An error occured in HTTP processing 
Failed to retrieve contents from web service https://vCenter server:443/sdk
BindingServer(ServerIP, proto=https, port=0) failed. "

0 Kudos