F5F Stay Refreshed Power Users Networks HyperV remote control issues with WinRM public network setup

HyperV remote control issues with WinRM public network setup

HyperV remote control issues with WinRM public network setup

T
TweeYeno
Member
69
12-01-2016, 06:45 PM
#1
I was adjusting an old NUC to run as a HyperV server and after fixing the network drivers it started working. Now I wanted to add it to my HyperV management on a Windows 10 machine that also hosts a VM. I followed all the instructions but encountered an error when using WinRM QuickConfig, specifically about a public network. It’s configured with a private name, interface alias, and IPv4 settings. I think the issue lies with the virtual interface, though there were no matching results online. Anyone have experience with this configuration? Or should I consider removing the HyperV service entirely and just install the management software?
T
TweeYeno
12-01-2016, 06:45 PM #1

I was adjusting an old NUC to run as a HyperV server and after fixing the network drivers it started working. Now I wanted to add it to my HyperV management on a Windows 10 machine that also hosts a VM. I followed all the instructions but encountered an error when using WinRM QuickConfig, specifically about a public network. It’s configured with a private name, interface alias, and IPv4 settings. I think the issue lies with the virtual interface, though there were no matching results online. Anyone have experience with this configuration? Or should I consider removing the HyperV service entirely and just install the management software?

A
asmuund
Member
125
12-01-2016, 07:16 PM
#2
The operating system in use is [OS name]. All systems are configured within the same domain. Firewall rules are currently set to [default setting].
A
asmuund
12-01-2016, 07:16 PM #2

The operating system in use is [OS name]. All systems are configured within the same domain. Firewall rules are currently set to [default setting].

A
AnnoyedOne
Junior Member
14
12-07-2016, 04:40 AM
#3
HyperV 2019 core same workgroup and firewall configurations were established following the instructions. However, the issue lies with the vSwitch. I removed the HyperV host from my Windows 10 machine, which restored normal network behavior. Once that was done, I added the HyperV server to the Hyper-V management tool and everything functioned perfectly. Whenever I enable the HyperV host on this system, it generates a public network, and WinRM is experiencing problems. Now I don’t need to run VMs directly on the computer—this is why I set up the NUC. Still puzzled about it.
A
AnnoyedOne
12-07-2016, 04:40 AM #3

HyperV 2019 core same workgroup and firewall configurations were established following the instructions. However, the issue lies with the vSwitch. I removed the HyperV host from my Windows 10 machine, which restored normal network behavior. Once that was done, I added the HyperV server to the Hyper-V management tool and everything functioned perfectly. Whenever I enable the HyperV host on this system, it generates a public network, and WinRM is experiencing problems. Now I don’t need to run VMs directly on the computer—this is why I set up the NUC. Still puzzled about it.