Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

New AD site won't replicate AD

I am connected to a new location over a hardware vpn.  My main domain is 192.168.0.x.  The new site is 192.168.20.x.  I made a new site in AD.  I DCpromo'd the server at the new location and after some work, was able to join clients to the domain at the new location.  I have corresponding dns forwarders at each location forwarding to each other.  I had it so I could ping by name from the main office to the new server and could ping the client only by ip at the new location.  I could ping everything by name from the client at the new location back to the main office.  Basically, it's all screwed up now .  Because the AD sites and services wouldn't replicate we dcpromo'd the new server back down, changed it's name and ip and dcpromo'd back up again.  Same result everywhere. I almost want to start from scratch but I feel like it's too late.  I am hoping it is just a DNS adjustment somewhere.
0
hindsight
Asked:
hindsight
1 Solution
 
hindsightAuthor Commented:
I have since flushed the meta data from AD at the main office and renamed and dcpromo'd the new location server again.  The DC at the main office has 3 nics.  two have a 10.10.x.x ip's that correspond to a NAS device.  Problem is when I ping my DC from the new location I get a10.10.x.x ip back instead of the desired 192.168.0.x address.  This ip's show up in DNS.  Even if I delete the A records they come back again on their own. Anyone want to take a shot at this? Anyone? Anyone?
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now