+ Post New Thread
Results 1 to 10 of 10
Windows Server 2008 Thread, A Second Domain/Network on the same subnet in Technical; Hi Guys. I am after some advice I have just procured a shiny new server to start building a brand ...
  1. #1
    Mr.Ben's Avatar
    Join Date
    Jan 2008
    Location
    A Pirate Ship
    Posts
    942
    Thank Post
    182
    Thanked 157 Times in 126 Posts
    Blog Entries
    2
    Rep Power
    65

    A Second Domain/Network on the same subnet

    Hi Guys. I am after some advice

    I have just procured a shiny new server to start building a brand new network with. The existing server installations here have a few problems (dating back before my time!) that make me think that I should start afresh with a new domain and gradually move users and services across to it. The timescale here is about 5 months to do the job. (Month one & two for the planning/build/testing, 3 for training/documentation/ 4 for rollout and 5 for stabilization).

    It is the first time I have had the chance to build from the ground up whilst migrating and the first issue that I have thought of would be how to move DHCP from the old servers to a new one.

    My first thought was that I could (for a short period), assign static IP's to all machines so that they continue to see the old domain and use it's dns, whilst bringing up a new dhcp instance on the new server (the static addresses would be excluded from the range). Is there a better way of doing this?

    I will then create a trust between two two domains to allow for access to information!

  2. #2
    Jamman960's Avatar
    Join Date
    Sep 2007
    Location
    London/Kent
    Posts
    992
    Thank Post
    186
    Thanked 197 Times in 157 Posts
    Rep Power
    47
    You could just use the 1 DHCP server until you switch the old one off at which point you'd just need to ensure that all reservations/exclusions are in place and then just switch off the old and authorise the new one - when clients next need to get an IP address they'll get assigned an address from the new server. As long as the old DHCP server gives out both DNS servers to clients you should be fine.

  3. Thanks to Jamman960 from:

    Mr.Ben (7th October 2010)

  4. #3
    pritchardavid's Avatar
    Join Date
    Sep 2009
    Location
    South Ockendon, Thurrock, United Kingdom
    Posts
    932
    Thank Post
    18
    Thanked 64 Times in 58 Posts
    Rep Power
    26
    another idea you could do

    Make your scope on the old domain a bit smaller and that way you can get a scope running on the second domain, has you have some spare ip address

  5. Thanks to pritchardavid from:

    Mr.Ben (7th October 2010)

  6. #4

    GrumbleDook's Avatar
    Join Date
    Jul 2005
    Location
    Gosport, Hampshire
    Posts
    9,952
    Thank Post
    1,346
    Thanked 1,800 Times in 1,118 Posts
    Blog Entries
    19
    Rep Power
    597
    Instead of using static addresses use DHCP reservation on both servers so that you can migrate only those machines you want across, when you want to.

  7. Thanks to GrumbleDook from:

    Mr.Ben (7th October 2010)

  8. #5

    EduTech's Avatar
    Join Date
    Aug 2007
    Location
    Reading
    Posts
    5,068
    Thank Post
    160
    Thanked 925 Times in 727 Posts
    Blog Entries
    3
    Rep Power
    273
    Yeah, I have done this in the past for a demo environment. All you have to make sure is you don't have 2 DHCP Servers on the network dishing out IP's as you know you'll get problems

    Have Fun!

    James.

  9. Thanks to EduTech from:

    Mr.Ben (7th October 2010)

  10. #6
    Mr.Ben's Avatar
    Join Date
    Jan 2008
    Location
    A Pirate Ship
    Posts
    942
    Thank Post
    182
    Thanked 157 Times in 126 Posts
    Blog Entries
    2
    Rep Power
    65
    Thanks for all the suggestions - I've gone with DHCP reservations as the plan so a big thanks to Tony for reminding me that I can do that!

  11. #7

    GrumbleDook's Avatar
    Join Date
    Jul 2005
    Location
    Gosport, Hampshire
    Posts
    9,952
    Thank Post
    1,346
    Thanked 1,800 Times in 1,118 Posts
    Blog Entries
    19
    Rep Power
    597
    To be honest, I prefer folk to use DHCP reservations anyway ... it allows for a better audit trail if something should go wrong and someone needs to investigate something.

  12. #8
    bart21's Avatar
    Join Date
    Aug 2009
    Location
    peterborough
    Posts
    405
    Thank Post
    79
    Thanked 54 Times in 52 Posts
    Rep Power
    20
    I agree. I would use reservations.

  13. #9

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,859
    Thank Post
    412
    Thanked 777 Times in 650 Posts
    Rep Power
    182
    I would not. My approach would be to create a new DHCP server and allocate a new range to it, and allow both to work in redundant parallel for a while. Then you gradually reduce the range available to the original server so that clients transition off it onto the new one - eventually all of them, and then you can decommission the old server and increase the address space available to the new one.

    You have to do this over a period of several (my rule is 20) N, where N is your lease time. If you just pull the carpet out from under one server, you leave clients thinking they have leases while in fact the new server is allocating the same addresses to someone else, and you get ugly collisions.

  14. #10

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,859
    Thank Post
    412
    Thanked 777 Times in 650 Posts
    Rep Power
    182
    Quote Originally Posted by Jamman960 View Post
    You could just use the 1 DHCP server until you switch the old one off at which point you'd just need to ensure that all reservations/exclusions are in place and then just switch off the old and authorise the new one - when clients next need to get an IP address they'll get assigned an address from the new server. As long as the old DHCP server gives out both DNS servers to clients you should be fine.
    And during the transition, duplicate addresses will be allocated. This is an unsafe approach.

SHARE:
+ Post New Thread

Similar Threads

  1. subnet mask 32
    By s_h084 in forum Windows Server 2008 R2
    Replies: 5
    Last Post: 24th May 2010, 12:01 AM
  2. Bulding a New Domain on the same subnet as old domain...
    By Robot in forum Windows Server 2008 R2
    Replies: 4
    Last Post: 31st March 2010, 04:08 PM
  3. Subnet - just a quickie
    By Simcfc73 in forum Wireless Networks
    Replies: 3
    Last Post: 16th October 2009, 09:04 PM
  4. Subnet Mask
    By laserblazer in forum How do you do....it?
    Replies: 28
    Last Post: 5th February 2008, 10:26 AM
  5. help with network address and subnet
    By sexyali in forum Network and Classroom Management
    Replies: 4
    Last Post: 28th August 2007, 06:18 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •