Hyper-V promiscuous mode broken? - Win10 build 2004

Sebastian187 1 Reputation point
2020-08-05T13:51:27.19+00:00

Does anyone have Hyper-V promiscuous mode working with Windows 10 Enterprise - build 2004?

Promiscuous mode worked for me months ago running an older build of Windows 10 following this guide: https://cloudbase.it/hyper-v-promiscuous-mode/

So when I try to get my physical NIC (Default Switch) mirroring its traffic to my virtual machines network interfaces set to "destination" using the standard cmdlets I end up with no error message but it does not work either. Using the script provided on the article above I end up with the an error stating the ICS could not be modified. 

PS C:\Windows\system32> Set-VMSwitchPortMonitorMode -SwitchName "Default Switch" -MonitorMode Source
Failed while modifying virtual Ethernet switch connection settings.
**The automatic Internet Connection Sharing switch cannot be modified.**
At C:\Users\USER\Documents\VMSwitchPortMonitorMode.psm1:68 char:25
+                         throw $job.ErrorDescription
+                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Failed while mo...ot be modified.:String) [], RuntimeException
    + FullyQualifiedErrorId : Failed while modifying virtual Ethernet switch connection settings.
The automatic Internet Connection Sharing switch cannot be modified.

Any ideas? This is driving me nuts for two days now...... whatever I tried I failed.

EDIT: Also when I deselect NDIS Filter on the Switch Manager I encounter the same error messages stating the ICS Switch could not be modified.

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,560 questions
Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,277 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian Xue (Shanghai Wicresoft Co., Ltd.) 30,386 Reputation points Microsoft Vendor
    2020-08-06T09:37:16.227+00:00

    Hi，
    You could enable port monitoring in powershell following these steps

    Set the Mirroring Mode of the capturing VM to Destination. 

    Set-VMNetworkAdapter <name of the VM> -PortMirroring Destination

    Enable Source Mirror Mode on the External port of the Virtual Switch the capturing VM is attached to. 

    $A = Get-VMSystemSwitchExtensionPortFeature -FeatureMame "Ethernet Switch Port Security Settings"  
$A.SettingData.MonitorMode = 2  
Add-VMSwitchExtensionPortFeature -ExternalPort -SwitchName <name of the switch> -VMSwitchExtensionFeature $A

    Or you could configure it in Hyper-V Manager refering to this link
    https://learn.microsoft.com/en-us/archive/blogs/technet/mspfe/virtual-machine-network-monitoring-the-easy-way-with-hyper-v-in-windows-server-2012

    According to the error message, you may also check if the ICS is enabled and the ICS service is running.

    Best Regards，
    Ian

  2. m310400 1 Reputation point
    2021-02-17T08:13:55.267+00:00

    Hello

    I've had the same problem, but the solution is...
    It's just a way to erase the problematic switch and rebuild it.

    0 comments
  3. Joshua Resch 1 Reputation point
    2021-07-09T14:09:47.987+00:00

    Step One
    -FeatureMame should prob be FeatureName

    Step two
    If the VM is already connected to the NIC, you may have to shutdown the VM

    Step 3
    Rebuild the switch (Also requires VM shutdown)

    Worked for us, best of luck

    0 comments