Windows 10 Bug in Windows networking - Private connection is reported to WinRM as being public

  • Thread starter Thread starter John Gwinner
  • Start date Start date
J

John Gwinner

I am getting the same error as:

How can I get winrm to setup Firewall Exceptions? - Microsoft Community


As is typical, MS palms it off to community support, when clearly it's a defective product.


Situation: I have two NIC's in my machine. As far as I know, both are set to private.


When I try to setup WinRM to allow HyperV connections from another PC IN MY SAME HOUSE - it says I cannot:


PS C:\WINDOWS\system32> Enable-PSRemoting


WinRM is already set up to receive requests on this computer.

Set-WSManQuickConfig : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859113"

Machine="localhost"><f:Message><f:ProviderFault provider="Config provider"

path="%systemroot%\system32\WsmSvc.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault"

Code="2150859113" Machine="mymachine"><f: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.

</f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>

At line:116 char:17

+ Set-WSManQuickConfig -force

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException

+ FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand


Yet, if I check the current connection:


PS C:\WINDOWS\system32> Get-NetConnectionProfile





Name : Network

InterfaceAlias : vEthernet (External NIC)

InterfaceIndex : 68

NetworkCategory : Private

IPv4Connectivity : Internet

IPv6Connectivity : NoTraffic

Continue reading...
 
Back
Top