Setting up networking for a SCCM Test Environment in Hyper-V
Posted on 2011-05-09
I've been having trouble setting up a test environment and couldn't find anything that specifically addressed my situation. I'm probably missing something obvious, but a few more sets of eyes always help get some perspective.
We have a test lab set up to mimic our production SCCM environment.
Virtual host running 2008 R2 with a VLAN1 external network connection, to keep it separated from the test domain.
blah.com top level domain containing our AD VM.
wee.blah.com child domain containing the following VMs:
Win 7 Client
Everything within the virtual domain works fine. The host has 12 NIC ports, so external connections are not a problem. I have network connections set up as follows:
Private Blah Network - All VMs communicate on this network
External Blah Network - The AD server acts as DHCP and DNS and has network connections to both this external network and the Private network. Routing and Remote Access is configured with basic forwarding and NAT.
Everything up to this point work fine. All VMs can talk to each other as well as the outside world. Here's where I am having trouble.
We are trying to test management of external clients via SCCM. As part of this test, the higher-ups want to connect another external network segment with some physical clients for testing. I have not yet been able to make this happen. I've created another virtual network in Hyper-V named Blah Physical Network, bound it to a physical NIC, connected that NIC both directly to a PC and to a hub with two other machines on it. I cannot get the DHCP server (AD) to assign any addresses along this segment. If I assign the addresses manually, the physical connection becomes pingable, but it doesn't get DNS resolution or any kind of routing.
I've been banging my head against this wall for a few days now. Any sort of push in the right direction would be greatly appreciated. If you have any other questions about the setup, please ask.