-
Titre
What do the different credential alarms mean and why have they been triggered? -
Description
What do the different credential alarms mean and why have they been triggered?
-
Résolution
Error:
"Cannot establish connection to HOSTNAME : received HTTP/401 - credentials rejected"
Potential root cause + trouble shooting tips:
- WinRM connection attempt failed with bad user name/password error. Please make sure the entered user name and password are correct.
- High resource usage, CPU and/or memory is preventing a successfull logon - look at solution 13309.
- Invalid namespace - look at solution 115973.
- In solution 156825 you will find further trouble shooting tips.
Error:
Cannot establish connection to HOSTNAME : HTTP request failed [Caused by: Connection to https://HOSTNAME:5986 refused]
Potential root cause + trouble shooting tips:
- WinRM connection via https not allowed and/or not configured. The steps to configure WinRM properly can be found here.
- In solution 156825 you will find further trouble shooting tips.
Error:
Cannot establish connection to HOSTNAME : A connection to the remote host could not be established. Windows returned error code 0x800706ba [Caused by: Invoke of: ConnectServer
Source: SWbemLocator Description: The RPC server is unavailable.Potential root cause + trouble shooting tips:
- Connection via native WMI failed; RPC server on the target machine is stopped. To investigate this alarm, look at solution 204932.
- In solution 156825 and 94039 you will find further trouble shooting tips.
Error:
Cannot establish connection to HOSTNAME : The WS-Management service could not be contacted and a non-SOAP packet was received
Potential root cause + trouble shooting tips: