DCDIAG Error and Solution Needed
Hi,
I configured the first domain controller of a domain (ad.test.com) which is
a peer domain to the forest domain (adroot.test.com) which is configured
already and working fine. After the implementation, while verifying the
installation of a DC (ad.test.com), dcdiag shows the following errors.
"
Starting test advertising...
Domain Controller not able to advertise as a Time
Server...advertising test failed.
Starting test fsmocheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 135
A Good Time Server could not be located."
Any Idea how to rectify the above errors?
Thanks,
Senthilkumaran B
RE: DCDIAG Error and Solution Needed
Tricky to troubleshoot. Are the following ok?
Name resolution to the authoritative time server ok?
Time service started?
Any firewall / router not allowing NTP through?
I'm sure others will have additional suggestions
"SENTHILKUMARAN B" wrote:
> Hi,
>
> I configured the first domain controller of a domain (ad.test.com) which is
> a peer domain to the forest domain (adroot.test.com) which is configured
> already and working fine. After the implementation, while verifying the
> installation of a DC (ad.test.com), dcdiag shows the following errors.
>
> "
> Starting test advertising...
> Domain Controller not able to advertise as a Time
> Server...advertising test failed.
> Starting test fsmocheck
> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
> A Time Server could not be located.
> The server holding the PDC role is down.
> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
> error 135
> A Good Time Server could not be located."
>
> Any Idea how to rectify the above errors?
>
> Thanks,
> Senthilkumaran B
>
Re: DCDIAG Error and Solution Needed
Hi
Sometimes all you need is to wait for replication or force it, and these
errors desapear. If not Start by checking name resolution (DNS)
configuration.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"SENTHILKUMARAN B" <SENTHILKUMARANB@discussions.microsoft.com> wrote in
message news:B42815AC-590B-4EEA-9C00-F0A52DAB71F0@microsoft.com...
> Hi,
>
> I configured the first domain controller of a domain (ad.test.com) which
> is
> a peer domain to the forest domain (adroot.test.com) which is configured
> already and working fine. After the implementation, while verifying the
> installation of a DC (ad.test.com), dcdiag shows the following errors.
>
> "
> Starting test advertising...
> Domain Controller not able to advertise as a Time
> Server...advertising test failed.
> Starting test fsmocheck
> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
> A Time Server could not be located.
> The server holding the PDC role is down.
> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
> error 135
> A Good Time Server could not be located."
>
> Any Idea how to rectify the above errors?
>
> Thanks,
> Senthilkumaran B
>
Re: DCDIAG Error and Solution Needed
> The server holding the PDC role is down
Type: nslookup -type=srv _ldap._tcp.pdc._msdcs.domain-name.com and look at
the returned DC.
Can you ping that box?
Or perhaps you don't get a positive result?
How is DNS configured in this new tree?
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
Re: DCDIAG Error and Solution Needed
Thanks to all for responding to my query...
I fixed the problem, time service was not registered properly...i
unregistered it and re-registered it.
Thanks,
Senthilkumaran B
"Paul Williams [MVP]" wrote:
> > The server holding the PDC role is down
>
> Type: nslookup -type=srv _ldap._tcp.pdc._msdcs.domain-name.com and look at
> the returned DC.
>
> Can you ping that box?
>
> Or perhaps you don't get a positive result?
>
> How is DNS configured in this new tree?
>
> --
> Paul Williams
> Microsoft MVP - Windows Server - Directory Services
> http://www.msresource.net | http://forums.msresource.net
>
>
>
>
Re: DCDIAG Error and Solution Needed
NETDOM QUERY PDC directly contacts the PDC. If not available it will fail
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Paul Williams [MVP]" <ptw2001@hotmail.com> wrote in message
news:%23iOCJsq0GHA.4580@TK2MSFTNGP05.phx.gbl...
>> The server holding the PDC role is down
>
> Type: nslookup -type=srv _ldap._tcp.pdc._msdcs.domain-name.com and look at
> the returned DC.
>
> Can you ping that box?
>
> Or perhaps you don't get a positive result?
>
> How is DNS configured in this new tree?
>
> --
> Paul Williams
> Microsoft MVP - Windows Server - Directory Services
> http://www.msresource.net | http://forums.msresource.net
>
>
>