[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1236
  • Last Modified:

Setting up networking for a SCCM Test Environment in Hyper-V

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:
DC
SCCM
Distropoint
Management
WSUS
Fallback Status/Reporting
XP Client
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.
0
Bighoppa
Asked:
Bighoppa
  • 5
  • 3
1 Solution
 
Svet PaperovIT ManagerCommented:
I am having difficulties to understand what you are trying to accomplish. Do you have some kind of network diagram to share? Even a logical diagram with routers and network segments will be good.
0
 
BighoppaAuthor Commented:
Yeah, let me draw something up in Dia.  Might make it easier to explain.
0
 
BighoppaAuthor Commented:
Hopefully this will help explain.

Currently everything inside the blah.com virtual domain works.  Anything on the 192.168.1.254 segment fails to get DHCP addresses, connect to internet, etc. What I am attempting to accomplish
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
Svet PaperovIT ManagerCommented:
I am still not sure that I understand well but let try… Correct me if I am off the picture…

Currently your DHCP server, installed on DC/DNS server, provides addresses for 10.1.1.x.

You have added a new virtual network adapter to DC/DNS/DHCP server connected to the segment that should be 192.168.1.x. The IP address of this NIC is 192.168.1.254.

If you set a fixed IP address in 192.168.1.0 to a PC connected to the switch, can you ping it from the DHCP server? (disable all firewall stuff for now if it’s Windows 7)

You created a scope for 192.168.1.0 on the DHCP server but it doesn’t provide addresses. Did you bind the NIC with IP address of 192.168.1.254 to the DHCP server? It’s in DHCP server manager, right-click on the server name (dc.blah.com) and select Add/Remove bindings…

That’s for the DHCP...

Where are the routers?
0
 
BighoppaAuthor Commented:
The 10.1.1.x addresses are for the external interfaces only.  

The DHCP server provides addresses in the 192.168.1.10-100 range.

The AD/DNS/DHCP (192.168.1.1) server is the router as far as that network segment is concerned.
0
 
Svet PaperovIT ManagerCommented:
OK. So, your server second IP address is not 192.168.1.254 but 192.168.1.1 (in addition to an IP address in 10.1.1.0). Did you check the bindings of the DHCP server?

What if you set a static IP address on a PC in the 192.168.1.0/24 subnet? Can you ping the DHCP server 192.168.1.1?
0
 
BighoppaAuthor Commented:
OK I just checked bindings and the 192.168.1.254 interface is bound to DHCP, so it should be giving out addresses within the scope.

I just went over to the lab and checked one of the physical machines and it is getting a DHCP address now.

Now I have a new problem with the external desktops not seeing the DC so I can't add them to the domain.  I'll consider this problem solved, though, and accept the DHCP bindings as the resolution.  Thanks for the help!
0
 
BighoppaAuthor Commented:
Making sure the new interface was bound to the DHCP server solved the issue.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now