Windows 2000 Active Directory Domain on a WAN

I have a customer with the following setup

a. Sydney: 192.168.2.xxx domain GNSSYDNEY NT 3.51
b. Brisbane: 192.168.7.xxx domain GNSBRISB NT 3.51
c. Melbourne: 192.168.3.xxx domain GNSMELBOURNE NT 3.51

The servers are independent domains with trust relationships. There is a 64kbit Frame Relay network between the locations.

We are moving all the systems to a Window 2000 system. We have established the domains

groupnews.com.au in Sydney, melbourne.groupnews.com.au in Melbourne and brisbane.groupnews.com.au in Brisbane. We want the credentials of the users replicated in each state so that a user in Sydney can login in Brisbane using Terminal Services using there Sydney users rather than having to replicate the users in each state.

How do we establish the replication between the domains? The link is slow so the replication should occur at night if possible or on demand.
LVL 1
philsmicronetAsked:
Who is Participating?
 
Thomas LeeConnect With a Mentor OwnerCommented:
You probably should have created just one domain: groupnews.com.au and setup three sites (Sydney, Brissie add Melbourne). On the site links, you can then create a schedule as to when DCs in each site will replicate to each other.

Assuming you have to go with three domains then you have a more complex situation. Basically, you'd need to put a DC for each domain in each site, then setup sites to replicate as apprpriate. This is a bit more complex!

Thomas



0
 
JasonCustomLANCommented:
Sounds very similar to a problem I was having today, I'll keep you posted.  Good Luck!
0
 
philsmicronetAuthor Commented:
Ok, thanks. We have setup this way and its works like a dream except the following problem. The DNS servers do not let me put forwarders in because it states it is a root server. I want the Brisbane + Melbourne DNS to look up local addresses and then pass to Sydney if it cant resolve. Sydney needs to then forward to an internet DNS server to resolve public host names. Is this possible?
0
 
Thomas LeeOwnerCommented:
Just remove the "." domain (the root domain) and you should be able to forward.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.