Windows 2003 DC Issues

I get the following errors everymorning in the Event log of the DC. We recently removed the old DC from the network, it was 2003 also. the AD is fine, the server has beeen runniing fine for 3 mo. now but these error keep happening. for some reason this dc is still looking for the old dc. something about a global catalog server it is looking for. how can i make this server the global catalog server.

here are some of the error logs

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is " ". The event data contains the error.


The DNS server was unable to connect to the domain naming FSMO pbbsrv-1.baileyarch.local. No modifications to Directory Partitions are possible until the FSMO server is available for LDAP connections. The event data contains the error code.



pbbsrv-1 was removed months ago form the network.


thanks

 

I think i found the answer, the removed server was still listed under the sites and service snap in, so this was most likely causing the problem, i will find out in a few days if the error still happens

thanks

 

I think you nailed the problem.

Might also be worth a check to make sure there are no active DNS records for the old machine.

 

Hi,
see the article http://support.microsoft.com/default.aspx?scid=kb;en-us;216498 for remove a DC form the active directory.
There are some other tasks to do

greetings Andy

 

thanks.
now the only error i get is this:

The DNS server was unable to connect to the domain naming FSMO pbbsrv-1.baileyarch.local. No modifications to Directory Partitions are possible until the FSMO server is available for LDAP connections. The event data contains the error code.


thanks for the help

My prolem right now is that i have to seize all the fsmo roles, but i hope it does not hurt my current AD