WS-Managemet Service

%3CLINGO-SUB%20id%3D%22lingo-sub-1616592%22%20slang%3D%22en-US%22%3EWS-Managemet%20Service%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1616592%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20folks%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20implemented%20WAC%20in%20our%20production%20environment%20and%20all%20works%20swimmingly%20just%20after%20install.%20But%20when%20trying%20to%20use%20it%20from%20the%20gateway%20%3CA%20href%3D%22https%3A%2F%2F%5Bgateway%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2F%5Bgateway%3C%2FA%3E%26nbsp%3Baddress%5D.domain%2C%20using%20credentials%20that%20have%20full%20access%20over%20the%20servers%20in%20the%20list%20the%20following%20message%20keeps%20appearing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%3EThe%20client%20cannot%20connect%20to%20the%20destination%20specified%20in%20the%20request.%20Verify%20that%20the%20service%20on%20the%20destination%20is%20running%20and%20is%20accepting%20requests.%20Consult%20the%20logs%20and%20documentation%20for%20the%20WS-Management%20service%20running%20on%20the%20destination%2C%20most%20commonly%20IIS%20or%20WinRM.%20If%20the%20destination%20is%20the%20WinRM%20service%2C%20run%20the%20following%20command%20on%20the%20destination%20to%20analyze%20and%20configure%20the%20WinRM%20service%3A%20%22winrm%20quickconfig%22.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20weird%20thing%20is%20though%20that%20just%20after%20install%20it%20works%20perfect%20but%20give%20it%20a%20day%20or%20so%20and%20this%20error%20comes%20up.%20all%20our%20servers%20are%20running%20WinRM%20service%20and%20when%20running%20PS%20command%20winrm%20quickconfig%20there%20response%20is%20%22PS%20C%3A%5CUsers%5C%5Busername%5D%26gt%3B%20winrm%20quickconfig%3CBR%20%2F%3EWinRM%20service%20is%20already%20running%20on%20this%20machine.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Eanyone%20had%20this%20or%20know%20what%20the%20issue%20could%20be%3F%20we%20control%20around%205000%2B%20servers.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ETIA%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi folks, 

 

I have implemented WAC in our production environment and all works swimmingly just after install. But when trying to use it from the gateway https://[gateway address].domain, using credentials that have full access over the servers in the list the following message keeps appearing.

 

"The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig"."

 

The weird thing is though that just after install it works perfect but give it a day or so and this error comes up. all our servers are running WinRM service and when running PS command winrm quickconfig there response is "PS C:\Users\[username]> winrm quickconfig
WinRM service is already running on this machine."

 

anyone had this or know what the issue could be? we control around 5000+ servers. 

 

TIA

0 Replies