# WinRM not working **URL:** \ **Category:** PowerShell Help\ **Created:** [September 6, 2019, 11:42am UTC](https://forums.powershell.org/t/winrm-not-working/13101 "2019-09-06T11:42:32Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![trgrassijr](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@trgrassijr](https://forums.powershell.org/u/trgrassijr)\ **Post date:** [September 6, 2019, 11:42am UTC](https://forums.powershell.org/t/winrm-not-working/13101/1 "2019-09-06T11:42:32Z")
I have a Windows 10 Desktop VM ``` PS C:\util> invoke-command -ComputerName tgkw004 -ScriptBlock {get-service nscp} [tgkw004] Connecting to remote server tgkw004 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. + CategoryInfo : OpenError: (tgkw004:String) [], PSRemotingTransportException + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionStateBroken ``` From the workstation I run this ``` PS C:\util> winrm quickconfig WinRM service is already running on this machine. WSManFault Message ProviderFault WSManFault Message = WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again. Error number: -2144108183 0x80338169 WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again. PS C:\util> Enable-psremoting WinRM is already set up to receive requests on this computer. Set-WSManQuickConfig : WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again. At line:116 char:17 + Set-WSManQuickConfig -force + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand PS C:\util> PS C:\util> $PSVersionTable Name Value ---- ----- PSVersion 5.1.16299.1146 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.16299.1146 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 ``` I tried upgrading to powershell 6.2.2 but that did not make any difference Any ideas? Thank you Tom ``` ``` ---
**Author:** ![Olaf](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/olaf/32/992_2.png) [@Olaf](https://forums.powershell.org/u/Olaf)\ **Post date:** [September 6, 2019, 12:17pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/2 "2019-09-06T12:17:09Z")
Did you actually read the messages? The solution is there … > [@](#): > > Message = WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again. ---
**Author:** ![trgrassijr](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@trgrassijr](https://forums.powershell.org/u/trgrassijr)\ **Post date:** [September 6, 2019, 12:28pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/3 "2019-09-06T12:28:32Z")
Yes I saw that message But it does not inform you of which firewall rule to change Any ideas? ---
**Author:** ![jasonrobertson](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/jasonrobertson/32/164_2.png) [@jasonrobertson](https://forums.powershell.org/u/jasonrobertson)\ **Post date:** [September 6, 2019, 3:13pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/4 "2019-09-06T15:13:38Z")
Tom, This is not a firewall acl issue, but the fact you are using the Public firewall and not for a Domain or the Private firewall. The answer is in the error message as Olaf has already stated. You will need to enable to Domain or Public Firewall as well or have all three disabled. Disabling the firewall in Windows is not recommended unless you have a 3rd party firewall to replace it. ---
**Author:** ![trgrassijr](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@trgrassijr](https://forums.powershell.org/u/trgrassijr)\ **Post date:** [September 6, 2019, 3:31pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/5 "2019-09-06T15:31:35Z")
Jason, I only use Microsoft Firewall no third party. I tried disabling the firewall that made no difference. It also does not tell you which rule is the issue ---
**Author:** ![Olaf](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/olaf/32/992_2.png) [@Olaf](https://forums.powershell.org/u/Olaf)\ **Post date:** [September 6, 2019, 4:37pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/6 "2019-09-06T16:37:57Z")
You set up your Microsoft Firewall included in your Windows operating system with one of 3 network types - Private, Domain or Public. In one of them - Public - the Firewall exception does not work as you wich it to work. So you have to use either the Domain profile - what’s recomended if your computer is a domain joined computer - or the Privat profile. ---
**Author:** ![trgrassijr](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@trgrassijr](https://forums.powershell.org/u/trgrassijr)\ **Post date:** [September 6, 2019, 4:42pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/7 "2019-09-06T16:42:34Z")
All my computers/servers are domain joined. Is there a power shell command to list to rules example? ---
**Author:** ![Olaf](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/olaf/32/992_2.png) [@Olaf](https://forums.powershell.org/u/Olaf)\ **Post date:** [September 6, 2019, 5:23pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/8 "2019-09-06T17:23:42Z")
With ``` Get-NetFirewallProfile ``` you can see an overview over the existing firewall profiles and with ``` (Get-NetConnectionProfile).NetworkCategory ``` you can see the active profile. ---
**Author:** ![aaron-hardy](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@aaron-hardy](https://forums.powershell.org/u/aaron-hardy)\ **Post date:** [September 6, 2019, 5:25pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/9 "2019-09-06T17:25:51Z")
I’ve run into a similar issue in the past that was caused by multiple network adapters being present on a domain-joined computer, which one was set to DomainAuthenticated and the other, Public. Because WinRM applies to all adapters by default, if just one is Public, you’ll get an error enabling WinRM/PSRemoting. [Get-NetConnectionProfile](https://docs.microsoft.com/en-us/powershell/module/netconnection/get-netconnectionprofile?view=win10-ps) and [Set-NetConnectionProfile](https://docs.microsoft.com/en-us/powershell/module/netconnection/set-netconnectionprofile?view=win10-ps) are needed as stated in this article: [https://www.paulligocki.com/how-to-setup-winrm-in-a-workgroup-non-domain-environment](https://www.paulligocki.com/how-to-setup-winrm-in-a-workgroup-non-domain-environment/) ---
**Author:** ![trgrassijr](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@trgrassijr](https://forums.powershell.org/u/trgrassijr)\ **Post date:** [September 6, 2019, 7:46pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/10 "2019-09-06T19:46:12Z")
PS C:\util\> Get-NetFirewallProfile Name : Domain Enabled : False DefaultInboundAction : NotConfigured DefaultOutboundAction : NotConfigured AllowInboundRules : NotConfigured AllowLocalFirewallRules : NotConfigured AllowLocalIPsecRules : NotConfigured AllowUserApps : NotConfigured AllowUserPorts : NotConfigured AllowUnicastResponseToMulticast : NotConfigured NotifyOnListen : True EnableStealthModeForIPsec : NotConfigured LogFileName : %systemroot%\system32\LogFiles\Firewall\pfirewall.log LogMaxSizeKilobytes : 4096 LogAllowed : False LogBlocked : False LogIgnored : NotConfigured DisabledInterfaceAliases : {NotConfigured} Name : Private Enabled : False DefaultInboundAction : NotConfigured DefaultOutboundAction : NotConfigured AllowInboundRules : NotConfigured AllowLocalFirewallRules : NotConfigured AllowLocalIPsecRules : NotConfigured AllowUserApps : NotConfigured AllowUserPorts : NotConfigured AllowUnicastResponseToMulticast : NotConfigured NotifyOnListen : True EnableStealthModeForIPsec : NotConfigured LogFileName : %systemroot%\system32\LogFiles\Firewall\pfirewall.log LogMaxSizeKilobytes : 4096 LogAllowed : False LogBlocked : False LogIgnored : NotConfigured DisabledInterfaceAliases : {NotConfigured} Name : Public Enabled : False DefaultInboundAction : NotConfigured DefaultOutboundAction : NotConfigured AllowInboundRules : NotConfigured AllowLocalFirewallRules : NotConfigured AllowLocalIPsecRules : NotConfigured AllowUserApps : NotConfigured AllowUserPorts : NotConfigured AllowUnicastResponseToMulticast : NotConfigured NotifyOnListen : True EnableStealthModeForIPsec : NotConfigured LogFileName : %systemroot%\system32\LogFiles\Firewall\pfirewall.log LogMaxSizeKilobytes : 4096 LogAllowed : False LogBlocked : False LogIgnored : NotConfigured DisabledInterfaceAliases : {NotConfigured} PS C:\util\> (Get-NetConnectionProfile).NetworkCategory Public PS C:\util\> ---
**Author:** ![trgrassijr](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@trgrassijr](https://forums.powershell.org/u/trgrassijr)\ **Post date:** [September 6, 2019, 8:04pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/11 "2019-09-06T20:04:12Z")
PS C:\util\> (Get-NetConnectionProfile).NetworkCategory Public PS C:\util\> Get-NetConnectionProfile | select interfacealias,networkCategory interfacealias NetworkCategory * * * Primary Public PS C:\util\> Get-NetConnectionProfile | Set-NetConnectionProfile -NetworkCategory Private PS C:\util\> Get-NetConnectionProfile | select interfacealias,networkCategory interfacealias NetworkCategory * * * Primary Private PS C:\util\> Enable-PSRemoting -force WinRM is already set up to receive requests on this computer. WinRM is already set up for remote management on this computer. PS C:\util\> winrm quickconfig WinRM service is already running on this machine. WinRM is already set up for remote management on this computer. PS C:\util\> Enable-PSRemoting -force WinRM is already set up to receive requests on this computer. WinRM is already set up for remote management on this computer. PS C:\util\> Do I need to restart the computer? After making the change to private I still get the PS C:\util\> invoke-command -ComputerName tgkw004 -ScriptBlock {get-service nscp} [tgkw004] Connecting to remote server tgkw004 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. + CategoryInfo : OpenError: (tgkw004:String) , PSRemotingTransportException + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionStateBroken PS C:\util\> ---
**Author:** ![kvprasoon](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/kvprasoon/32/4449_2.png) [@kvprasoon](https://forums.powershell.org/u/kvprasoon)\ **Post date:** [September 8, 2019, 9:28am UTC](https://forums.powershell.org/t/winrm-not-working/13101/12 "2019-09-08T09:28:19Z")
This error can come because of many reasons. Did you read about\_Remote\_Troubleshooting doc ? you can read by executing **Get-Help about\_Remote\_Troubleshooting**. Additional to it, check the state of Windows Firewall service, it should be running as well. ---
**Author:** ![maarten](https://avatars.discourse-cdn.com/v4/letter/m/ecccb3/32.png) [@maarten](https://forums.powershell.org/u/maarten)\ **Post date:** [September 9, 2019, 2:59am UTC](https://forums.powershell.org/t/winrm-not-working/13101/13 "2019-09-09T02:59:18Z")
I use an batch file to enable WinRM remote PSremote.cmd \ psexec -s \%1 C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command “Set-NetFirewallRule -Name “WINRM-HTTP-In-TCP” -RemoteAddress Any” -Profile Domain psexec -s \%1 C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command “Enable-PSRemoting -SkipNetworkProfileCheck -Force” ---
**Author:** ![fredrik-kacsmarck](https://avatars.discourse-cdn.com/v4/letter/f/a183cd/32.png) [@fredrik-kacsmarck](https://forums.powershell.org/u/fredrik-kacsmarck)\ **Post date:** [September 10, 2019, 9:33am UTC](https://forums.powershell.org/t/winrm-not-working/13101/14 "2019-09-10T09:33:59Z")
Maybe start with the basics, checking that you can actually reach the machine/port from your machine. [pre] Test-NetConnection tgkw004 -Port 5985 Test-NetConnection tgkw004 -Port 5986 [/pre] First is the default HTTP port, second is the default HTTPS port. If neither of those are accessible then it’s most likely a firewall issue, if the TcpTestSucceeded is “true” then it’s a WinRM configuration issue. ---
**Author:** ![jasonrobertson](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/jasonrobertson/32/164_2.png) [@jasonrobertson](https://forums.powershell.org/u/jasonrobertson)\ **Post date:** [September 10, 2019, 11:02am UTC](https://forums.powershell.org/t/winrm-not-working/13101/15 "2019-09-10T11:02:10Z")
Tom, Are you using Wifi or Ethernet? If you are on Wifi it could be that your Security Admins have configured wifi to be classified as Public instead of Domain Authenticated via GPO. Try using Ethernet instead, you want to see DomainAuthenticated for NetworkCategory if your computer is connnected to a domain. I would also ask why are you using invoke-command for Get-Service when you can just provide the computername? ``` Get-Service nscp -ComputerName tgkw004 ``` ---
**Author:** ![nitbha](https://avatars.discourse-cdn.com/v4/letter/n/6a8cbe/32.png) [@nitbha](https://forums.powershell.org/u/nitbha)\ **Post date:** [September 11, 2019, 4:43am UTC](https://forums.powershell.org/t/winrm-not-working/13101/16 "2019-09-11T04:43:04Z")
Can you check if the S **erver** :tgkw004 has **WinRM** service is in start mode ? ---
**Author:** ![js2010](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@js2010](https://forums.powershell.org/u/js2010)\ **Post date:** [September 11, 2019, 8:28am UTC](https://forums.powershell.org/t/winrm-not-working/13101/17 "2019-09-11T08:28:23Z")
Here’s my script to enable powershell remote in windows 10. It’s a PITA to get right. You don’t have to be on a domain. Don’t forget to set trustedhosts on the other end. ``` # enable remote powershell #on target: enable-psremoting -force -skipnetworkprofilecheck $result = $? # (not firewall control panel displayname) # powershell 4 in win7 doesn't have it Set-NetFirewallRule -Name WINRM-HTTP-In-TCP -RemoteAddress 192.168.1.1 # DisplayName : Windows Remote Management (HTTP-In) Set-NetFirewallRule -Name WINRM-HTTP-In-TCP-NoScope -Enabled True -RemoteAddress 192.168.1.1 # domain,private profiles, DisplayName : Windows Remote Management (HTTP-In) #(to disable: disable-psremoting -force) if ( -not $result ) { exit 1 } #on source or client: #start-service winrm #Set-Item WSMan:\localhost\Client\TrustedHosts -Value 192.168.1.2 #$Cred = Get-Credential # don't need cred after this #$S = New-PSSession -ComputerName 172.17.64.195 -Credential $Cred #remove-session $s # ? #Invoke-Command -ComputerName 172.17.64.195 -ScriptBlock { Get-ChildItem C:\ } -credential $cred #Enter-PSSession -ComputerName 172.17.64.195 -Credential $cred #copy-item "c:\users\admin\desktop\there" "c:\users\admin\desktop" -fromsession $s #copy-item "c:\users\admin\desktop\there" "c:\users\admin\desktop" -tosession $s ``` ---
**Author:** ![trgrassijr](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@trgrassijr](https://forums.powershell.org/u/trgrassijr)\ **Post date:** [September 12, 2019, 6:46am UTC](https://forums.powershell.org/t/winrm-not-working/13101/18 "2019-09-12T06:46:04Z")
First Thanks to all the suggestions they lead me to the real problem. After trying this command I found the problem Test-NetConnection tgkw004 -Port 5985 Not WINRM not FIREWALL it was DNS The computer registered with DNS the wrong ip address I had to disjoin the computer from the domain and join the computer back then the computer registered in DNS and winrm worked Thanks again This is now resolved. ---
**Author:** ![aaron-hardy](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@aaron-hardy](https://forums.powershell.org/u/aaron-hardy)\ **Post date:** [September 12, 2019, 2:48pm UTC](https://forums.powershell.org/t/winrm-not-working/13101/19 "2019-09-12T14:48:05Z")
If you hadn’t tried it, you could have used `ipconfig /registerdns` to initialize/update name registration with DNS (no reboot required either) and avoid the domain rejoin. ---
**Author:** ![sinoath](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@sinoath](https://forums.powershell.org/u/sinoath)\ **Post date:** [September 14, 2019, 6:59am UTC](https://forums.powershell.org/t/winrm-not-working/13101/20 "2019-09-14T06:59:56Z")
hi all, first thing: thank you all for the infos that helped me figure out how to configure winRM. Now everything seems to work just fine. Here’s my concern: is it norma that whenever i issue a command (like get-process -computername MyRemoteComputer) i have to wait 10-15 seconds before i can see any output on screen? I am studing powershell in a LAN enviroment with a laptop connected via wireless (the client) and a desktop connected via ethernet (the remote host). Is there anything i can check to get faster response from the remote computer? Thank you in advance [Next page](https://forums.powershell.org/t/winrm-not-working/13101.md?page=2)