One Domain Two IP Subnets

Discussion in 'Windows Server' started by JHP, Apr 4, 2007.

  1. JHP

    JHP Guest

    Our company (50 users) has one Domain Controller, Exchange Server, and File
    Server (all Windows 2003) - all on 192.168.5/24, but 10 of us are moving,
    with the Servers, to a new site. The second site will be set up with the
    range of 192.168.1/24.

    Were setting up a VPN site-to-site connection - each site with there own T1.

    What can I do to ensure that both sites sill work as one - mainly concerning
    DNS / DHCP / WINS / etc.

    Thank you for any support, documents, KB articles, anything,
    JHP, Apr 4, 2007
    1. Advertisements

  2. JHP

    Herb Martin Guest

    What do you mean by "as one"?

    If you don't filter over the VPNs and setup routing correctly then all will
    operate over the connection -- authentication, replication, resource access,
    etc, assuming you have enough bandwidth to make it practical.

    If you have a DC (or more) at each location (and you should if resources
    exist at both location and access is critical) you should set these up as
    SITES with Subnets, Sitelink(s) and locating the DCs in the correct sites.

    Also, you should have every DC a GC in a single domain forest; a DNS
    server in each location (usually on the DC with AD Integration), and
    replicated WINS servers at each location also perhaps.
    Herb Martin, Apr 4, 2007
    1. Advertisements

  3. JHP

    JHP Guest

    Your preaching to the choir brother, but our company is not prepared to pay
    the $1200 pre Windows 2003 server license, including the $2000 - $10000 a
    pop per blade server.

    Our DC is a GC in a single domain forest, with AD Integration including
    replicated WINS...

    Using Site-to-site VPN - can you foresee any problems besides bandwidth
    issues; also how does DHCP cope with the two subnets - does one of the sites
    need to be setup with static ip's?

    Thank you for taking the time to help,
    JHP, Apr 4, 2007
  4. JHP

    JHP Guest

    I am concerned how things will work in a Domain environment which included
    an Exchange server, UNIX servers, etc.

    Thank you for your comments, if you have anymore advice please give it.
    JHP, Apr 4, 2007
  5. JHP

    Herb Martin Guest

    You can get hardware and (legal) standard Windows Server MUCH
    cheaper than that.

    You are going to be resolving names, and authenticating across that
    WAN line -- so if you DNS/DC goes down you are going to lose
    both access to INTERNAL domain resources AND the ability to resolve
    Internet names (i.e., access to the Internet too.)
    You should have a minimum of two DCs if at all possible anyway.

    Lose your only DC and lose the entire domain unless you have (very good)
    Either one of three ways:

    1) Another DHCP server at each site
    2) By having another "server with DHCP relay agent"
    Although some routers may do this also -- and might call it
    setting the "IP helper" address or some such
    3) Or by having your routers implement "BootP forwarding" (aka RFC1542)

    Herb Martin, Apr 4, 2007
  6. JHP

    JHP Guest

    Thanks again, you have given me allot to think about...
    JHP, Apr 4, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.