Network and Classroom Management Thread, 2 Domains on 1 IP Range. in Technical; Hi I need a little help in trying to get my new network running. I've inherited a school where they ...
2nd May 2012, 07:48 PM #1
- Rep Power
2 Domains on 1 IP Range.
Hi I need a little help in trying to get my new network running. I've inherited a school where they have one (semi broken cc3) domain (domain A), a 2nd (vanilla) domain (Domain B). For a short while (lets say a period of 3 months) they need both domains to run on the same network simoultaneously.
What's the best way to go about this. Can I run Domain A and domain B on the same DHCP Scope, obviously both have their own DHCP, DNS servers.
What I've come up with is I will exclude an IP range on Domain A (lets say 50 addresses) extending the exclusion as and when required. I will then statically assign the clients on domain B the excluded ip addresses, until such time where I will be in a position to completely switch off domain A.
I have configured WDS on domain B. During the middle of the day when its reasonably safe that everyone has turned their computers on and have an IP assigned,
1) I switch off dhcp and dns on domain A
2) Activate the dhcp scope on domain B,
3) Build the stations that I need to,
4) Then deactivate dhcp on domain B
5) and reactive dns and dhcp on domain A.
I have set my WDS to listen for unknown clients, but without an activated dhcp scope on domain B the pxe boot process does not pick up an IP address.
Is there a better way to get these two domains working on the same range simultaneously, or I just have to put up with this long winded process until they are back on one domain?
IDG Tech News
2nd May 2012, 08:34 PM #2
Domain A with a shortened DHCP scope and Domain B with a limited scope for exactly the number of addresses needed which are allocated via reserved IP addresses. Or DHCP reservations for both?
2nd May 2012, 09:08 PM #3
Yes I've seen this many times - one DHCP scope but two domains with a trust. Absolutely pointless these days, but back in the days of Windows 98 it was considered more necessary.
2nd May 2012, 10:14 PM #4
- Rep Power
ah yes ofcourse, If i reserve the mac address of the client for an IP in Domain B, i then don't need to set a static ip, and so avoiding a second visit to the machine to change ip allocation to DHCP, once domain A is decommissioned.
Nice one. I'll test that.. but I'm not sure with two DHCP servers running, how do I stop the client from getting an IP from DHCP on Domain A
2nd May 2012, 10:23 PM #5
Use AD without DNS integration. Setup two DNS zones on the same server. DHCP with one scope.
By vote-for-pedro in forum Windows Server 2000/2003
Last Post: 7th July 2010, 12:39 PM
By techie08 in forum Windows Server 2000/2003
Last Post: 20th May 2009, 11:11 PM
By Kyle in forum Wireless Networks
Last Post: 29th September 2008, 08:17 PM
By chrisjako in forum Wireless Networks
Last Post: 6th February 2008, 04:28 PM
By tosca925 in forum Windows
Last Post: 12th August 2007, 01:35 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)