I have two domains, Li350.local and ens01.Li350.local. Each of them has a 2003 SP2 DC. Here is the result of dcdiag /test:dns /DnsBasic /e /v run insp5102000s (ens01.Li350.local DC).
I have only kept the lines related with an error.
- Domain Controller Diagnosis
- Performing initial setup: [Insp5102000s] Directory Binding Error 1722: Le serveur RPC n'est pas disponible.
- Doing initial required tests [INSP5102000S] DsBindWithSpnEx() failed with error 1722, Le serveur RPC n'est pas disponible.. Status is 1722: Le serveur RPC n'est pas disponible. Status is 10061: Aucune connexion n'a pu tre ‚tablie car l'ordinateur cible l'a express‚ment refus‚e. Status is 10061: Aucune connexion n'a pu tre ‚tablie car l'ordinateur cible l'a express‚ment refus‚e. ......................... INSP5102000S failed test Connectivity
- Doing primary tests
- DNS Tests are running and not hung. Please wait a few minutes... DC: insp5102000s.Ens01.Li350.local Domain: Ens01.Li350.local TEST: Basic (Basc) Error: No DS RPC connectivity Root zone on this DC/DNS server was not found
- Summary of DNS test results: Auth Basc Forw Del Dyn RReg Ext ________________________________________________________________ Domain: Ens01.Li350.local insp5102000s PASS FAIL n/a n/a n/a n/a n/a ......................... Li350.local failed test DNS
Apart from this, this machine (insp5102000s, ens01.Li350.local DC) runs perfectly.
Can you be of any help ?
Regards,
Baumic
Software/Hardware used:
dcdiag windows 2003 SP2
ASKED:
February 16, 2011 8:01 AM
UPDATED:
February 17, 2011 2:23 PM
A couple of things:
1. Check services to see if RPC is enabled.
2. Check your firewall to see if RPC is allowed.
There was an old bug (mostly Windows XP upgrading to SP2/3 from SP1) where the RPC service security descriptor could get corrupted. You can check for how to reset the security on the RPC service to the default.