Hyper-V Virtual Switch problems Windows issues with virtual switches in Hyper-V
Hyper-V Virtual Switch problems Windows issues with virtual switches in Hyper-V
Windows server issue with Hyper-V VM not reaching network. VM uses virtual switch 169.254.XXX.XXX, but subnet is 192.168.0.0. Linux VM on same subnet appears online in firewall (PF-Sense). Added IPV4 rule for 168.254.XXX.XXX, but no response. Need help understanding Hyper-V setup.
Additionally, during ping attempts, I receive: PING 192.168.XXX.XXX (192.168.XXX.XXX) 56(84) bytes of data. From 192.168.XXX.XXX icmp_seq=1 Destination Host Unreachable
The 169.254 range is reserved for private networks and usually given when a device can't connect to a DHCP server. It suggests your virtual switch isn't getting an IP from the external network via VM or bridge. Verify that adaptors and virtual adaptors are configured properly in passthrough or bridged mode. I haven't relied heavily on Hyper-V, more of a VMware user, but this should guide you. Good luck!
Display a screenshot of your Hyper-V Virtual Switch Manager. Typically you need one external switch with the right physical network adapter selected. Ensure the checkbox for allowing the host to share the connection is checked if you only have a single Ethernet link. REMOVE: this page gives a concise overview of Hyper-V switches – https://www.nakivo.com/blog/hyper-v-netw...-switches/. NOTE: For proper IP assignment, make sure DHCP is functioning; static IP changes should be handled later.
You modified the static rule on one of your Linux VMs to use DHCP and cleared the reserved IP in the firewall so it would request an address from the DHCP server. After restarting, the VM was able to get an IP from the same subnet as your other devices. However, you're still having trouble pinging between the VM and your server. The screenshot of your Virtual Switch Manager might be relevant. It could relate to the DHCP server's IP range—specifically, the LAN range is 192.168.0.10–255, DHCP uses 192.168.0.10–200, and the reserved range is 192.168.0.200–255. The router's reserved addresses are also in that range. Please let me know if you need more details. Thanks again!
Here I start feeling pretty new. I just set up a pfsense firewall/router a couple of weeks back as the DHCP server. I think there might be an issue, but I haven’t tweaked anything or used any tricky settings. Just a simple setup with the wizard and a rule to let all LAN traffic through.
pfsense is what you mentioned. After testing, it seems like the setup might be working. If the VM and physical machine can ping each other via DHCP, they should be reachable. You can check connectivity by pinging between them. Running Nslookup on the VM's hostname should return its IP address. If issues persist, verify network configurations and firewall rules.