Adding another Member server from a different subnet

Archived from groups: microsoft.public.win2000.active_directory (More info?)

I have our main network on a 10.5.x network and I am implimenting a new
remote network on a 172.x network (should I be using 10.6.x?)
How do I get this new server into our existing network? Should I configure
it and dcpromo it in the 10.5.x network and then change the network and dns
to 172.x or should I configure and dcpromo it in the 172x from the start
(looking for least problems down the road)?

I think I am going to use a child domain for the remote network. I have a
small network connection to this network and I want it to have the same
information (users, etc) from the main network.
This may be an easy question for some but I am a little stumped.
All thoughts are appreciated.
Thank You
3 answers Last reply
More about adding member server subnet
  1. Archived from groups: microsoft.public.win2000.active_directory (More info?)

    > I have our main network on a 10.5.x network and I am implimenting a new
    > remote network on a 172.x network (should I be using 10.6.x?) How do I get
    > this new server into our existing network? Should I configure it and
    > dcpromo it in the 10.5.x network and then change the network and dns to
    > 172.x or should I configure and dcpromo it in the 172x from the start
    > (looking for least problems down the road)?

    As this is going to be a member server, no you shouldn't DCPROMO it. You
    should simply configure routing between the sites (comms not software) and
    then configure the server to use an internal DNS server in the other site
    and then join it to the domain. You could make this a secondary DNS server
    and point to self if the WAN link is slow or whatever.


    > I think I am going to use a child domain for the remote network. I have a
    > small network connection to this network and I want it to have the same
    > information (users, etc) from the main network.

    You don't want a child domain. You simply need to configure a site in
    Active Directory Sites and Services. You obviously DON'T want a member
    server and DO want a DC. Therefore you should create a new site and then,
    after following my earlier advice, DCPROMO the box as a new DC in an
    existing domain.

    --
    Paul Williams
    Microsoft MVP - Windows Server - Directory Services
    http://www.msresource.net | http://forums.msresource.net
  2. Archived from groups: microsoft.public.win2000.active_directory (More info?)

    I appologize if I am a little slow but to make sure...
    Basically
    Install W2k3 on new server in the remote network
    Setup routing on the remote server to get to the existing network (I will
    have a hardware VPN between sites if that counts)
    Setup the remote server to use the DNS of the Main Network
    DCPromo the remote server as a new server in an existing domain
    ...Is this Correct? I got a little confused beween 'to dcpromo or not to
    dcpromo'

    I think I will use sites and services as you mentioned
    Thank you for your advice. This does help me a lot but as always, it
    creates extra questions.

    Would I have a mess if I installed the remote server on the main network,
    changed IPs and moved the server to a different site through sites and
    services?

    Thank you again.
    Corey

    "ptwilliams" <ptw2001@hotmail.com> wrote in message
    news:elH08K9XFHA.1368@tk2msftngp13.phx.gbl...
    >> I have our main network on a 10.5.x network and I am implimenting a new
    >> remote network on a 172.x network (should I be using 10.6.x?) How do I
    >> get
    >> this new server into our existing network? Should I configure it and
    >> dcpromo it in the 10.5.x network and then change the network and dns to
    >> 172.x or should I configure and dcpromo it in the 172x from the start
    >> (looking for least problems down the road)?
    >
    > As this is going to be a member server, no you shouldn't DCPROMO it. You
    > should simply configure routing between the sites (comms not software) and
    > then configure the server to use an internal DNS server in the other site
    > and then join it to the domain. You could make this a secondary DNS
    > server
    > and point to self if the WAN link is slow or whatever.
    >
    >
    >> I think I am going to use a child domain for the remote network. I have
    >> a
    >> small network connection to this network and I want it to have the same
    >> information (users, etc) from the main network.
    >
    > You don't want a child domain. You simply need to configure a site in
    > Active Directory Sites and Services. You obviously DON'T want a member
    > server and DO want a DC. Therefore you should create a new site and then,
    > after following my earlier advice, DCPROMO the box as a new DC in an
    > existing domain.
    >
    > --
    > Paul Williams
    > Microsoft MVP - Windows Server - Directory Services
    > http://www.msresource.net | http://forums.msresource.net
    >
    >
  3. Archived from groups: microsoft.public.win2000.active_directory (More info?)

    > I appologize if I am a little slow but to make sure...

    Don't apologise. Your here to get help. Well all start somewhere.


    > Install W2k3 on new server in the remote network
    > Setup routing on the remote server to get to the existing network (I will
    > have a hardware VPN between sites if that counts)
    > Setup the remote server to use the DNS of the Main Network
    > DCPromo the remote server as a new server in an existing domain
    > ...Is this Correct? I got a little confused beween 'to dcpromo or not to
    > dcpromo'

    Don't configure the server to route. Use your hardware. Yes, if you want a
    DC run DCPROMO.


    > I think I will use sites and services as you mentioned Thank you for your
    > advice. This does help me a lot but as always, it creates extra
    > questions.

    Good and no problem!


    > Would I have a mess if I installed the remote server on the main network,
    > changed IPs and moved the server to a different site through sites and
    > services?

    There's a tiny bit more work involved if you do this at the main site and
    move it. The following explains what's needed:
    -- http://www.msresource.net/content/view/22/47/


    If this is the first time you're doing this, do it at the local site and
    ship it out there. You don't want or need network problems confusing things
    or making life more difficult.

    All the best to you. And post as many questions as you need...

    --
    Paul Williams
    Microsoft MVP - Windows Server - Directory Services
    http://www.msresource.net | http://forums.msresource.net
Ask a new question

Read More

Servers Windows