Is it possible to join a computer to the domain from a remote location and promote it to a DC? Obviously, this would be a security concern, so I'm assuming you can't. Anyway, if you can't, then it sounds like you need to join it to the domain at the local site, promote it to a DC & GC server, configure sites and subnets putting the future remote DC it the remote site before shutting it down and moving it to the new location. Am I wrong?
Housenet - in reply to your questions:
-Are you pointing your DNS settings to the ADDNS ip in TCP/IP of the NIC on the remote server?
>I tried putting in the local DNS IP into the remote DNS TCP/IP settings to attempt to connect the remote client, join it to the domain, and promote it to a DC. That's when I received the error message.
-Is there an ldap record in the _msdcs.mydomain.com->dc->_
>Yes, there is an _ldap record in my AD DNS zone.
Main Topics
Browse All Topics





by: HousenetPosted on 2005-10-10 at 07:12:47ID: 15052353
The first few replic sync's with AD are critical. The fisrt several syncs including enabling GC (The DC in the remote subnet must be a GC to process logins at that site without a working connection to the GC at HQ on the other side of the link) should be fully tested on the LAN before shipping the server to the remote site.
ldap.tcp_ in your AD DNS zone?
As for your specific error message....
-Are you pointing your DNS settings to the ADDNS ip in TCP/IP of the NIC on the remote server?
-Is there an ldap record in the _msdcs.mydomain.com->dc->_