Forum Discussion
Solved
WAC will not connect to Windows 10 computer(s)
I get THIS connection error: Connecting to remote server xxx-203.domain.local failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer nam...
- I finally got it sussed with this link:
https://www.mustbegeek.com/how-to-enable-winrm-via-group-policy/
It helped me figure out that I needed to do some things in Group Policy then wait. I did all this last night and today I could touch the desired Win10 box. Now only to figure out various other things...Thank you, everyone!! 🙂
Try running the following on the client machine
winrm enum winrm/config/listener
Look for the line "ListeningOn = ", does it have a valid IP or does it say NULL?
I went through this this morning and it turns out it was an old GPO that was set to filter out IP's under
Computer Configuration - Administrative Templates - Windows Components - Windows Remote Management (WinRM) - WinRM Service
IPV4 filter was filled in with IP's that were thought to filter what IP's to listen TO when they actually filter what IP's to listen ON.
If there are IP's listed, remove them and then just put * in the filter field. Update your GPO on the client and run the winrm enum command again. It should list the IP's available on the client machine.
winrm enum winrm/config/listener
Look for the line "ListeningOn = ", does it have a valid IP or does it say NULL?
I went through this this morning and it turns out it was an old GPO that was set to filter out IP's under
Computer Configuration - Administrative Templates - Windows Components - Windows Remote Management (WinRM) - WinRM Service
IPV4 filter was filled in with IP's that were thought to filter what IP's to listen TO when they actually filter what IP's to listen ON.
If there are IP's listed, remove them and then just put * in the filter field. Update your GPO on the client and run the winrm enum command again. It should list the IP's available on the client machine.
MrDecepticon Well I did have this configured to the local subnet range. I've changed it to *. I have to wait for group policy to update since I don't have direct access to the client machine. By this evening or tomorrow I should know if this works or not. Thank you!! 🙂 tom
- This didn't work either, still same error message. Can anyone suggest any other ways I can test winrm?? I don't have remote access to the particular Win10 computer unfortunately.