The vSwitch had external access until I turned off DHCP on the firewall and told my DC to take that over. You mention to fix the vswitch to the host to have external access but I'm unsure of what to do there. Mike400, when I do a ping to 8.8.8.8 and from the DC I get host unreachable and a timeout. The vSwitch is pulling the external DNS, IP, etc. The host NIC is showing the correct IP but the vSwitch is pulling that external info. I explained it backwards though, now that I look at it.

Ok, my bad, I did forget to statically assign my host IP (I built it on my home network and then moved it to site so that's why I was initially using DHCP on the host). If the first one passes and the second one doesn't then you have a DNS problem. If the first ping fails then you have the wrong gateway address set in the DHCP server. Retry the two pings above from the client. Restart a workstation and verify it shows up in the DHCP and DNS server. This is the minimal configuration for a Windows client. Next, in your DHCP Server ensure you have scope configuration entries for DNS (point to your DC), Gateway address (point to your router since that's your DNS server), and node type - set to 0x8. In the Windows DNS server you can actually test name resolution - do so and verify you get good tests. For some reason a lot of Spiceheads seem to think DNS forwarders are the second coming.

In general, forwarders add a level of complexity without any real benefit.

In the DC's DNS server remove ALL forwarders and then try again. If you get a response from the first but not the second then your DNS configuration is wrong. If you don't get a response from the first ping you don't have your router/gateway configured or the DC isn't connected to a Hyper-V switch that has external (off host) access. Ping You should get responses back from both.

Arch virtualbox dhcp not working