Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Joining 2 windows 2003 (standard) servers over a WAN

Posted on 2014-04-29
3
210 Views
Last Modified: 2014-05-06
we would like to join 2 windows 2003 servers together over a WAN.

Does anyone have any detailed instructions on how to do this? I have not connected any together before and would like to be able to do this.

Any advice greatly appreciated.

Many thanks.
0
Comment
Question by:nigelbeatson
  • 2
3 Comments
 

Author Comment

by:nigelbeatson
ID: 40029887
Having read the question again, I thought I should provide some additional information.

The 2 sites are in the UK, but in different cities. both have a high speed internect facility. I would I have Exchange running at site 1 and would like to provide a connection so that we can have access to the mail server from site 2.

Would site 1 be the only domain controller, or is there some kind of replica required at site 2?

Do we need both sites to work using the same local domain name, and how is DHCP configured? Do we have the same IP address subnet at both sites.

I would like to have an understanding of what is required to facilitate this, as so far I have only dealt with stand alone servers, so if there is any step by step instructions anywhere, I would love to see them.

Many thanks.
0
 
LVL 77

Accepted Solution

by:
Rob Williams earned 500 total points
ID: 40030175
That is a big topic :-)

You would normally join the two using two VPN capable routers.  The established tunnel makes connectivity seamless.

Both sites MUST use different subnets for routing to take place.

The servers would normalcy be members of the same local domain (simpler), but they do not have to be, you can set up a trust relationship between the two.  You also configure active directory sites and services for the two sites, subnets, and servers.

You only need one domain controller but all machines, members of the same domain have to authenticate to it and use it as their sole DNS server.  This can slow performance a bit and if the VPN goes down, users on the site without a DC cannot authenticate (except using cached credentials) and will have no Internet.  A DC at each site is recommended but certainly not necessary.  It can be a Read Only DC.

DHCP is handled locally by router or server (recommended) however DHCP must assign your DNS server/s as its only DNS server, you cannot add an ISP or router as an alternate.  It must also hand out the domain suffix.
0
 

Author Closing Comment

by:nigelbeatson
ID: 40043975
Many thanks.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The HP utility "HP Lights-Out Online Configuration Utility for Windows Server 2003/2008" could be of great use when it comes to remotely configure a HP servers ILO WITHOUT rebooting the server. We would only need to create and run scripts using thi…
I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question