How to resolve Win2k Domain name conflict with an existing NT 4 Domain
Posted on 2003-11-13
I'm currently trying to extend our Win2k Domain to our remote offices through VPN tunnels on SonicWall gear. Subnets have been created and the VPN tunnels are up. I can see both sides of the networks from either location.
Memphis is our HQ. The Win2k Domain "Wunderlichsecurities.com" is running with 3 DCs and 60 local clients.
Houston has been running their own NT 4 domain. "Wunderlich"
Problem is that the domain name is the same as our NetBios Win2k Domain in Memphis.
When the VPN tunnel is up, an election is forced on the network and the Houston NT4 servers basically win. Which wreaks havoc when trying to do anything in AD. Temporarily I have taken down the VPN link.
Eventually I will build another DC here in Memphis, replicate AD and send it to Houston.
1. Is that the best way to extend the domain to Houston? Should the server be built in Houston on the different subnet and replicate AD over the VPN link?
2. Until then, should I trust the existing NT domain to our Win2K domain? Can you trust a domain by the same name?
Houston is just the first site I'm doing, I have 3 other locations to do also, so this will set the blueprint for how I do the other locations.