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
From this perspective, when connecting to a Windows VM, you must turn off the firewall (avoid unless you're doing tests) or activate the built-in ICMP rule at https://kb.iu.edu/d/aopy
Here’s a revised version of your message:
So, let's begin with the basics. I have a physical Pfsense server equipped with two NICs—one for WAN and one for LAN. The WAN uses DHCP from my ISP since we don’t have a fixed IP address. The LAN has a static address range of 192.168.0.1 to 256, while the DHCP range spans from 192.168.0.10 to 200. The latter part (192.168.0.201 to 256) is reserved for future use and isn’t available for assignment. On my side, I have a Windows Server 2016 with two virtual machines: one running Ubuntu 14.04 with a static IP, and another using Ubuntu 16.04 with DHCP. Currently, I’m working from a home network connected via VPN, which prevents me from testing directly on the network. However, my work PC is linked through the VPN, allowing me to reach the servers successfully. Keep in mind that my work PC is always behind a VPN connection.
This suggests the problem likely involves the virtual switch failing to route traffic between the host and virtual machines or an issue with the adapter/virtual adaptor configuration. I recommend checking a tutorial on setting up network adapters on a Hyper-V server with just one NIC. If your 2016 server has several NICs, consider assigning one for Hyper-V and another for Windows.
Does your server have several connections? Which of them is assigned an IP address?
I initially believed PFSense operated as a virtual machine. Based on your configuration, your Virtual Switch Settings seem appropriate. Are you using a single Ethernet port or multiple? As @harry4742 mentioned, the server’s IP address is likely set through a virtual adapter provided by HyperV (the checkbox enabling host sharing confirms this).
There are a few issues detected. Your configuration appears to be mismatched. The setup shows a virtual switch with a physical adapter, but the steps suggest adjustments for a hyper-v adapter instead. Please verify the correct adapter type and follow the appropriate instructions.
It seems you're asking about an internal IP address. Are you looking for information on how to manage or hide it?
A bit uncertain, actually! It's a habit of mine to keep things hidden.
It's resolved! As discussed, including @Blake, an issue arose with my Hyper-V virtual switch. My primary Ethernet card got assigned an IP, but the virtual switch couldn't reach DHCP. I removed the old switch, set up a new one, and reconfigured the VM—now everything works properly. Connection info matches Blake's screenshots. Thanks to everyone for the support! Looking forward to being back soon with another hiccup.