rebuilding a DC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We bought a new server to replace our BDC. In doing so, we demoted the
current machine to a member server, removed the static IP's (it had 2 nics)
and shut it down. We built the new server with the same name as the old one,
used 2 nics again (one is for web services to a client firewall, other is for
shared printing). We proceded to go through DCPROMO to make it a BDC. After
completing, I've been unable to verify any 13509 messages for FRS. No
metadata cleanup was done post the demotion of the old server. Did we mess
things up by not cleaning up the metadata prior to adding a new BDC with the
same server name but different IP's? I've tried using FRsdiag to
troubleshoot. The ntfrs logs display "EPT_S_NOT_REGISTERED(This may indicate
that DNS returns the IP address of the wrong computer" and also
"RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but
there was a failure to send RPC call package." Any help in moving in the
right direction would be appreciated. I'm stuck as to the next steps to take
(with minimal impact).

AC
 
It may never have completed promotion at all. The first place to check for
that would be to run a DCDIAG /V (DCDIAG.EXE is from the Support Tools) and
look at the Advertising test to see if it passes. A common failure on
incomplete promotion will appear as "reached server X when trying to reach
server Y" (badly paraphrased). If you gather the DCDIAG /V feel free to
post it and I'll check back to look it over...
 
Back
Top