SOLVED

WAC will not connect to Windows 10 computer(s)

%3CLINGO-SUB%20id%3D%22lingo-sub-1267819%22%20slang%3D%22en-US%22%3EWAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1267819%22%20slang%3D%22en-US%22%3E%3CP%3EI%20get%20THIS%20connection%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConnecting%20to%20remote%20server%20xxx-203.domain.local%20failed%20with%20the%20following%20error%20message%20%3A%20WinRM%20cannot%20complete%20the%20operation.%20Verify%20that%20the%20specified%20computer%20name%20is%20valid%2C%20that%20the%20computer%20is%20accessible%20over%20the%20network%2C%20and%20that%20a%20firewall%20exception%20for%20the%20WinRM%20service%20is%20enabled%20and%20allows%20access%20from%20this%20computer.%20By%20default%2C%20the%20WinRM%20firewall%20exception%20for%20public%20profiles%20limits%20access%20to%20remote%20computers%20within%20the%20same%20local%20subnet.%20For%20more%20information%2C%20see%20the%20about_Remote_Troubleshooting%20Help%20topic.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProblem%20is%3A%20the%20name%20IS%20valid%2C%20the%20computer%20IS%20accessible%20over%20the%20network%2C%20the%20firewall%20exception%20IS%20enabled%20via%20Group%20Policy%2C%20then%20WinRM%20service%20is%20started%20via%20Group%20Policy%2C%20WinRM%20PS-remoting%20IS%20installed%2C%20I%20did%20winrm%20quickconfig%20on%20this%20device.%20I%20know%20this%20particular%20device%20has%20been%20rebooted.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20am%20I%20missing%3F%3F%20that%20should%20be%20done%20for%20WAC%20to%20touch%20this%20computer%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%2C%20Tom%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1269047%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1269047%22%20slang%3D%22en-US%22%3ETry%20running%20the%20following%20on%20the%20client%20machine%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3Ewinrm%20enum%20winrm%2Fconfig%2Flistener%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3ELook%20for%20the%20line%20%22ListeningOn%20%3D%20%22%2C%20does%20it%20have%20a%20valid%20IP%20or%20does%20it%20say%20NULL%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20went%20through%20this%20this%20morning%20and%20it%20turns%20out%20it%20was%20an%20old%20GPO%20that%20was%20set%20to%20filter%20out%20IP's%20under%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EComputer%20Configuration%20-%20Administrative%20Templates%20-%20Windows%20Components%20-%20Windows%20Remote%20Management%20(WinRM)%20-%20WinRM%20Service%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIPV4%20filter%20was%20filled%20in%20with%20IP's%20that%20were%20thought%20to%20filter%20what%20IP's%20to%20listen%20TO%20when%20they%20actually%20filter%20what%20IP's%20to%20listen%20ON.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20there%20are%20IP's%20listed%2C%20remove%20them%20and%20then%20just%20put%20*%20in%20the%20filter%20field.%20Update%20your%20GPO%20on%20the%20client%20and%20run%20the%20winrm%20enum%20command%20again.%20It%20should%20list%20the%20IP's%20available%20on%20the%20client%20machine.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1269074%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1269074%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F603244%22%20target%3D%22_blank%22%3E%40MrDecepticon%3C%2FA%3E%26nbsp%3BWell%20I%20did%20have%20this%20configured%20to%20the%20local%20subnet%20range.%20I've%20changed%20it%20to%20*.%20I%20have%20to%20wait%20for%20group%20policy%20to%20update%20since%20I%20don't%20have%20direct%20access%20to%20the%20client%20machine.%20By%20this%20evening%20or%20tomorrow%20I%20should%20know%20if%20this%20works%20or%20not.%20Thank%20you!!%20%3A)%3C%2Fimg%3E%20tom%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1271308%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271308%22%20slang%3D%22en-US%22%3EThis%20didn't%20work%20either%2C%20still%20same%20error%20message.%20Can%20anyone%20suggest%20any%20other%20ways%20I%20can%20test%20winrm%3F%3F%20I%20don't%20have%20remote%20access%20to%20the%20particular%20Win10%20computer%20unfortunately.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1285269%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1285269%22%20slang%3D%22en-US%22%3E%3CP%3ESee%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fmanage%2Fwindows-admin-center%2Fsupport%2Ftroubleshooting%23i-can-connect-to-some-servers-but-not-others%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EI%20can%20connect%20to%20some%20servers%2C%20but%20not%20others%3C%2FA%3E%20section%20of%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fmanage%2Fwindows-admin-center%2Fsupport%2Ftroubleshooting%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWAC%20troubleshooting%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20first%20diagnosis%20step%20is%20to%20try%20remote%20PowerShell%20from%20the%20console.%3C%2FP%3E%0A%3CP%3EOn%20the%20same%20machine%20where%20you%20have%20installed%20WAC%2C%20try%3A%3C%2FP%3E%0A%3CPRE%3EEnter-PSSession%26nbsp%3B%3CSPAN%3Exxx-203.domain.local%3C%2FSPAN%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1289716%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1289716%22%20slang%3D%22en-US%22%3EI%20get%20the%20same%20error%2C%20only%20in%20PowerShell%20red.%20Maybe%20I%20can%20do%20rsop%20to%20see%20if%20the%20relevant%20policy%20items%20are%20applying%20to%20this%20computer...%3F%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1289913%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1289913%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20get%20the%20same%20error%20in%20the%20console%20then%20it's%20a%20Remote%20PowerShell%2FWSMAN%2FWinRM%20configuration%20issue%2C%20unrelated%20to%20Windows%20Admin%20Center.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303076%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20will%20not%20connect%20to%20Windows%2010%20computer(s)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303076%22%20slang%3D%22en-US%22%3EI%20finally%20got%20it%20sussed%20with%20this%20link%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.mustbegeek.com%2Fhow-to-enable-winrm-via-group-policy%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.mustbegeek.com%2Fhow-to-enable-winrm-via-group-policy%2F%3C%2FA%3E%3CBR%20%2F%3EIt%20helped%20me%20figure%20out%20that%20I%20needed%20to%20do%20some%20things%20in%20Group%20Policy%20then%20wait.%20I%20did%20all%20this%20last%20night%20and%20today%20I%20could%20touch%20the%20desired%20Win10%20box.%20Now%20only%20to%20figure%20out%20various%20other%20things...Thank%20you%2C%20everyone!!%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

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 name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.

 

Problem is: the name IS valid, the computer IS accessible over the network, the firewall exception IS enabled via Group Policy, then WinRM service is started via Group Policy, WinRM PS-remoting IS installed, I did winrm quickconfig on this device. I know this particular device has been rebooted.

 

What am I missing?? that should be done for WAC to touch this computer??

 

Thank you, Tom

 

7 Replies
Highlighted
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.
Highlighted

@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

Highlighted
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.
Highlighted

See the I can connect to some servers, but not others section of WAC troubleshooting.

 

The first diagnosis step is to try remote PowerShell from the console.

On the same machine where you have installed WAC, try:

Enter-PSSession xxx-203.domain.local

 

 

Highlighted
I get the same error, only in PowerShell red. Maybe I can do rsop to see if the relevant policy items are applying to this computer...??
Highlighted

If you get the same error in the console then it's a Remote PowerShell/WSMAN/WinRM configuration issue, unrelated to Windows Admin Center.

Highlighted
Best Response confirmed by tlyczko2 (Occasional Contributor)
Solution
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!! :)