Thanks, the server in question is not a DNS server itself, so that's not the
issue. What am I supposed to be looking for in terms of events log errors or
what? Would they be on the DNS server or on the serber in question. I am
taking my time with this since this is the into the 2nd month on this looking
for a fix. If I can't demote it then I will let it run till it dies and then
have to do metadata cleanup. I will try #1 and #3 to see what happens.
"Ryan Hanisco" wrote:
> Brian,
>
> You mention that the DNS is working correctly and that it is pointed in the
> right place.
>
> 1. Make sure that you can ping the domain by both its NetBIOS name as well
> as its FQDN -- not just that you are able to ping the DNS server itself.
> This should resolve to the PDCe role-holder in both cases.
>
> 2. If you are running AD-Integrated DNS, remember that your DCs running DNS
> should be pointing only to themselves as the DNS source. This means that
> if you are running AD-Integrated DNS on the server that you want to demote,
> it should only be pointing at itself for DNS resolution.
>
> 3. If you have resolved these and are still having problems, you will want
> to install the support tools and run both dcdiag /v and netdiag /v against
> the 2000 server. This will identify any Replication, FSMO, and DNS problems
> that you are having. Take another look at your Event Logs to make sure that
> there isn't something there that you are overlooking. It is easy to do,
> especially if you don't have large buffers in the logs.
>
> Take your time on this and work through it. Try not to get impatient and
> just kill the server planning to seize roles and do a metadata cleanup
> later. Working through this will make your AD healthier as well as keep you
> out of trouble.
>
> The frustration you will go through resolving something like this is much
> less than the potential frustration you might have if your whole
> organization grinds to a halt through messed up DNS/ FSMO replication.
> --
> Ryan Hanisco
> MCSE, MCDBA
> FlagShip Integration Services
> Chicago, IL
>
> "Brian" wrote in message
> news:E660DD53-8717-45F3-8B62-9A771B6B0E47@microsoft.com...
> > Trying to remove an old W2k DC from doamin. Ran depromo and get "The DSA
> > operation is unable to proceed because of a DNS lookup failure". Looked
> > at
> > KB 263624. DC can ping Wins and DNS servers just fine. Pointing to
> > correct
> > DNS. DNS is AD integrated. Believe problem to be with how this server
> > was
> > named. It is servername.anotherName while the reset of the DC in doamin
> > are
> > servername.dcname The server in question runs fine in the DC, it's just
> > too
> > slow to continue being a DC. Since I can't change name of DC server is
> > there
> > any other way short of rebuilding the server to correct this? Thanks
>
>
>