[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 638
  • Last Modified:

LAN to WAN

I have a question on how to link two LANs together.  On one LAN (Small network) we have one Domain Controller; on the other LAN (Main network) I have a Domain Controller and a Exchange Server.  We have created a tunnel connection between both sites with two routers.  What’s the best way to configure the servers so I can have everyone on the same Domain? or tree?  I don’t want people using POP3 or OWA anymore.  
0
ranpage
Asked:
ranpage
  • 5
  • 4
  • 2
2 Solutions
 
JammyPakCommented:
what addressing scheme are you using in the two sites?

if you have a tunnel that is acting as a bridge, then you could use the same logical network address for both sites. Otherwise, you'll need to have different logical network addresses for each site, and then configure routing to pass packets from one site to the other. As long as there's no firewall or access control lists limiting which packet types can go through the tunnel, then there will be no reason why someone from site a can't join a domain in site b. You will likely have name resolution problems, so you should set up a common DNS or WINS server for both sites to use - or , setup replication for WINS and secondary zones for DNS. This will be necessary for machines in one site to locate machines in the other based on name (since broadcasts may not be going through the tunnel)
0
 
sstephensnetCommented:
Since the 2 domains were created separate you will have to demote one controler and then promote it to be a DC again once you have established connectivity between the two.  Once you have done this you can set up the New DC to be a Active directory DNS server for the domain.  It will then mirror  the DNS zone for the original domain, just as jammy said would be needed.  Once all of this is done you could actually set up a Site in Win2000 so that computers in one location would not cross the WAN link to authinticate with the DC.
0
 
ranpageAuthor Commented:
Could you give me more detail on how to demote and promote the servers?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
sstephensnetCommented:
0
 
ranpageAuthor Commented:
what type of server will the server be how shall I can configure it.  Replication Partner? also yes we are windows 2000 server
0
 
JammyPakCommented:
Ah..I missed the point that you had 2 domains as well....
When you uninstall Active Directory (using dcpromo), then your server is just a 'member server'....after you will reinstall Active Directory (using dcpromo again) as an additional domain controller in the existing domain. You'll have to have DNS working before you'll be able to do this.
0
 
JammyPakCommented:
Ah...something I thought of....

I don't know if you've planned this all out, but you may not want to combine the two sites into one domain. You could leave the domains separate and setup trusts or something....the benefit being less intrusion on the client.

If you combine into one domain, then all pc's that are members of the domain that's disappearing will have to be taken out of their existing domain, and put into the other one. All user accounts will also have to be created in the other domain. Plus, when user's login to their PC's again, it will create a brand new user profile for them...so you'll have to copy their profile if  they want to have the same desktop, My Documents, etc.

Just a heads up really....
0
 
ranpageAuthor Commented:
If I were to have one domain how who I configure the AD during the install?
0
 
JammyPakCommented:
this is what sstephensnet was referring to -

to combine the domains, you demote your one domain controller (which blows away one of your domains) and then repromote it to a domain controller of the other domain. both of these actions are done using dcpromo.exe

now you'll only have one domain, but everyone in the other site will be 'domainless' untill you re-add them to the new domain.
0
 
ranpageAuthor Commented:
I understand that I have to demote and promote. but when install active directory what DCpromo scenario should I use to configure the new server?  ALso is it ok if the neworks have different network nodes i.e. 192.168.0 and 192.168.2  ?
0
 
JammyPakCommented:
"is it ok if the neworks have different network nodes i.e. 192.168.0 and 192.168.2  ?"

this depends...

if the two sites are acting as separate segments, then they must use separate network addresses - however, this means that you'll have to setup routing to get to the other site.

if the two sites are connected in bridge mode, then they are acting as one segment, and they must use the same network address

also, i'm assuming that your subnet mask is 255.255.255.0

"when install active directory what DCpromo scenario should I use:

what are the options? basically, you want to install it as an additional domain controller in an existing domain...I don't remember what "scenarios" you have to choose from
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 5
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now