- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
after configuration of agentless user-id using Kerberos with WinRM-HTTP (was hard to get it working needed pa support for it)
i encounter this issue
i got 2 DC in my environment DCA and DCB
When DCA is restarted i get Connection refused on both DCA and DCB in server monitoring
i get error connection failed, HTTP code 100, Timeout was reached for DCA
and error connection failed, HTTP code 0, Couldn't connect to server for DCB
When DCB is restarted i get connection refused only on DCB
with error connection failed, HTTP code 0, Couldn't connect to server on DCB
DCA show connected
Any one encountered this ?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!