Windows Forum

Ask something
Discussion Locked

Sites and Replication, Single Domain

0 helpful
4 replies

by stevetd

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have 3 sites in a Win2k environment only. DC is setup in primary site. How should we install DC's in remote sites? This will be 1 domain. With remote site DC's replicating. Should the new DC's be setup at the primary site then moved physically tothe new site. We have setup site links with different subnets. When using Dcpromo the machines in the remote sites cannot see our DC in the primary site. DNS is pointing to the first sites DC. DNS is working fine. Pings work, networked all through Fibre. Any help would be great...thanks for any advise in advance.

4 replies

by bettynumb1

Do you have a WINS server anywhere? Are your routers configured to pass NetBios traffic? You might be having problems passing NetBIOS over your WAN.

When we deployed to remote sites we built the DC's at our main site and left them in the main site boundary until we physically moved them to the remote location. Then we moved them into their site. We pointed the servers back to the main site's WINS server. The remote site DC's are DNS servers as well.

by joseph moore

Ok, if all of your IP addressing is correct, and DNS is ok (really make sure the SOA records point to your DC at the main site), then I would read Technet article Q180094:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q180094
(please remove any spaces)

Put in a single record in the LMHOSTS file of the 2 other machines you want to be DCs, pointing to the IP address and NetBIOS machine name of your DC in the main site. The article tells you why you need this. It should fix your problem.

And I would set up the other DCs in the remote sites. Really test out the fibre connections.

hope this helps

by stevetd

Glad to say I figured it out finaly, I was thinking last night this way had to work....Brought the machines back to the main site, changed subnet addressing to local network, authenticated, joined domain, replicated. Then took machines back to remote location changed addressing back to remote subnet, moved servers into corisponding "sites" in sites and services, logged in, replicated and all is fine with great response. Seems this is the best way not having to use any other transport. Just incase anyone else has this problem, which I fought with for a week. This took about 2hrs in total. Feels good to work so hard on a problem then it finaly works....:)

This discussion is closed to new replies.