Moving a domain controller to new building

  • Thread starter Thread starter Scott Yenor
  • Start date Start date
S

Scott Yenor

Hello,

I have setup an additional domain controller in my office with the
intent of moving it to a differnet building until I can get all my
users moved there. I took my newly installed domain controller to the
new building and started it up, but it tells me that it can't find the
domain controller for the network (even though it's supposed to be the
domain controller).

Anyone have any ideas as to what it might be and how I can fix it.

Regards,

Scott Yenor
 
Is this machine a DNS server? Doesn't sound like it ...

What is the configuration of the server's DNS client (resolver)? It needs
to be able to find the DNS server hosting the domain's SRV records.

Is this server now in a new site? If so - change the site it is in ...

-ds
 
Before moving a DC you should create the appropriate site and subnet and
associate the two. It's best to set the DNS client to look at the DNS
server in the original (or main, if that's different) site, until after
you're sure replication is working correctly.

Now that you've already moved the DC, I would do the following:

[On the DC in the original site]
Create a site with an applicable name, and a subnet that matches the new
subnet of the new site (don't use the same subnet).
Associate the site and subnet (using dssite.msc)

[On the DC in the new site]
Point the DNS client at the main DNS server.
Perform the following at the command prompt:
C:\>ipconfig /flushdns
C:\>net stop netlogon
C:\>net start netlogon
C:\>ipconfig /registerdns

Leave things like this for a couple of hours. When your sure that the two
are replicating, you should change the DNS to point to itself -if it isn't a
DNS server it should be (I'd use AD Integrated DNS). Also, ensure that this
box is a GC.


Paul.
______________________________
 
Back
Top