Link to home
Start Free TrialLog in
Avatar of Michel P
Michel P

asked on

failed test FsmoCheck - A Time Server could not be located

Hi Everyone,

When doing an FSMO check on my PDC (BEZADC01) I am getting a time server error:

 
C:\Windows\system32>dcdiag /test:FSMOcheck

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = BEZADC01
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: BEZA\BEZADC01
      Starting test: Connectivity
         ......................... BEZADC01 passed test Connectivity

Doing primary tests

   Testing server: BEZA\BEZADC01


   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : intra

   Running enterprise tests on : intra.domain.be
      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
         1355
         A Good Time Server could not be located.
         ......................... intra.domain.be failed test FsmoCheck

C:\Windows\system32>
However BEZADC01 is synced with NTP

I tried the proposals in this article: http://clintboessen.blogspot.be/2013/11/the-server-holding-pdc-role-is-down.html and this thread: https://www.experts-exchange.com/questions/27322087/DCDiag-reports-'a-good-time-server-could-not-be-located'-and-'the-PDC-role-is-down'.html

I have enabled the announce flag, and set NTP.

But still no luck :(. How can I resolve this error?

Thanks for any help.
Avatar of John Tsioumpris
John Tsioumpris
Flag of Greece image

Maybe you have a firewall blocking NTP requests
ASKER CERTIFIED SOLUTION
Avatar of Satish Auti
Satish Auti
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Michel P
Michel P

ASKER

Hi,

I tried the commands as outlined in the great article:

net stop w32time
w32tm /unregister
w32tm /register
net start w32time
net time /setsntp:
net stop w32time & net start w32time
w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:yes /update
w32tm /resync /rediscover
net stop w32time & net start w32time

I have tun them the PDC only, but that didn't help. I have run them now on all the DC's, and now the dcdiag /test:FSMOcheck succeeds!
Al tough I don't get why this is. I would suspect that having the PDC NTP settings correct would be correct, as he is the FSMO holder
Glad to hear that!!!