Repaired AD DC with CD setup/repair, now have "Endpoit Mapper" err

[Guest]

After having our only AD DC server crash (Used setup/repair option on CD to
restore missing files), I now get "There are no more endpoints available from
the endpoint mapper" when trying to join a workststion to the domain. I
reinstalled DNS and restored the Active State (the only copy I have was made
AFTER the crash). This worked for a few minutes, but then the problem
resurfaced. RPCDUMP shows 0 registered endpoints. PORTQRY shows port 135 as
listening. Event viewer (Directory Service) gives this error every hour :

id 1655 The attempt to communicate with global catalog \\pb-dc1.pinebelt.net
failed with the following status:
There are no more endpoints available from the endpoint mapper.

Also there are these event viewer errors:

id 13562 "Could not bind to a Domain Controller. Will try again at next
polling cycle."

id 1000 "Windows cannot determine the user or computer name. Return value
(1753). (This one is every few minutes)

Most assuredly, its a DNS issue, but I can't figure out how to fix it. I was
thinking of reinstalling DNS, using my Post-crash system state (to repopulate
DNS entries), and then reinstalling SP4 to update the OEM CD files that were
copied. Will this work??? (The only patches the server had on it originally
wer SP 4, and the Blaster and Sasser patch.) I know of others who are having
this problem, particularly after recovering from a crash and reinstalling DNS
on top of DNS, but none of the info from MS (it's slim on this one) has been
of any help. Any assistance would be appreciated! Thanks. --Therrel

 

[Steve Duff [MVP]]

That dog's hunting the wrong tree -- I don't see why you think you have a DNS problem. It looks like an issue with RPC services,
which will cause exactly the sort of errors you are seeing. Fix the RPC problem and I think things will look much better DNS-wise.

Run through the diagnostic steps in this very fine KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;839880

Pay special attention to the RPC ClientProtocols key contents. That key seems to have a very occasional but very nasty habit of
somehow getting deleted.

Report back what you find. (Before starting, you want to double-check that the server time and time zone are set correctly and the
server is sync-ing to an outside source.)

I also want to be sure your repair was the second (Windows-mode setup) repair, not the initial repair option which does not fix
missing critical registry entries.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.