Search results for query: *

It looks to be fixed now after I corrected the IP address in DNS.

When I originally set up the 2nd DC, it was here in New York - then we shipped it to LA. When I ping it from the NY DC using the DNS name, it uses the old IP address - not the current one.

Thanks again Keshav. So far, it looks to be a DNS issue. Firewall is disabled on both DC's. I can ping both ways successfully by IP address but not by DNS name. Event Log gives File Replication Event ID 13508 on both DC's (pasted below). I have yet to run DCDiag, but will soon. Event Type...

Another thing - when I changed the admin password in AD on the NY DC, the changes did not come into effect on the LA DC; it is still using the old password. Combined with the situation above, it seems that there is a problem with the new DC - it is not syncing with Active Directory across the...

Keshav: Thanks for the response. That is the behavior that I expected but when I logged-in to the NY DC (changes were made on the LA server), AD Sites and Services did not reflect the changes - even after several hours. I'm currently working to find out why.

The new DC server is in LA now and I've made the changes suggested above in AD. Do I need to do the same for the server in NY? Thanks again.

yes, thanks very much.

Keshav, that's what I was looking for - thanks for the advice!

Here's the current situation: Los Angeles location is using the DC at New York location. We are shipping a new server out to act as a DC in LA. We want LA to look to that DC - not the one in NY. We don't want to create a child domain because we want to provide redundancy in case one of DC's goes...