A WindowsAgent using the WinRM connection method could not connect to the monitored host. The following messages were reported:
ECHO <HostAgents/5.7.2/WindowsAgent/Monitor@host.domain.com-agent>
ERROR [Quartz[0]-711] com.quest.remoteos.SystemMonitorImpl - The agent failed to collect data for host.domain.com. com.quest.glue.api.services.RemoteConnectionException: a connection could not be established
ECHO <HostAgents/5.7.2/WindowsAgent/Monitor@host.domain.com>
DEBUG [Quartz[0]-0] com.quest.glue.core.remoteconnection.ConnectionPool - Unable to authenticate to host host.domain.com with credential 04d18da6-f705-4722-86ea-d94fe8de2722 com.quest.glue.api.services.CredentialRejectedException: received HTTP/401 - credentials rejected ... ECHO <HostAgents/5.7.2/WindowsAgent/Monitor@host.domain.com>
DEBUG2 [Quartz[0]-0] com.quest.glue.core.services.windowsinfo.WindowsInfoServiceImpl - Caught unimportant exception; safe to ignore: connection attempted failed, moving on to next connection com.quest.glue.api.services.InvalidCredentialsException: A connection with host.domain.com-agent could not be established using any of the 1 credentials assigned to this host
com.quest.glue.api.services.InvalidCredentialsException: A connection with host.domain.com-agent could not be established using any of the 1 credentials assigned to this host
The FglAM identified the monitored host as being in a different domain (domain.com
) than the FglAM was in (child.domain.com
), and the krb5.conf
file was not configured to allow contact with the KDC in the parent domain. Both hosts were actually members of the same domain (child.domain.com
).
Update the domain of the credential user from:
domain.com/user
To:
child.domain.com/user
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center