Hyper-V Switch created without Ethernet Adapter vEthernet (WSL) NIC C4*-*-*-*-*B4 successfully disconnected from port . The server could not bind to the transport \Device\NetBT_Tcpip_{D7*-*-*-*-*E8} because another computer on the network has the same name. The server could not sta...
AFAIK the eth0 device is connected to the vEternet (WSL) virtual adaptor and I managed to create another vEthernet (WSL-TEST) adaptor through "Virtual Switch Manager" in windows: Ethernet adapter vEthernet (WSL-TEST): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . ....
The reason you are getting a Hyper-V Virtual Ethernet Adapter popping up is due to Windows Sandbox. Windows Sandbox on Win10 2004 now creates a vEthernet interface for every physical NIC. Uninstalling the Sandbox in Control Panel -> Programs and Features -> Turn Windows features on or ...
wsl distro's containers have errors when attempting to attach to the network Diagnostic Logs From Windows 11: PS C:\Users\taylorprins> ipconfig /all Ethernet adapter vEthernet (WSL): Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adap...