Announcement

Collapse
No announcement yet.

Warning: Server is not advertising as a time server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Warning: Server is not advertising as a time server

    That it seems to me that my server (former PDC) is not functioning well. There is in addition problem with NTP service. Running netstat I could see that udp port is iopen on 123.

    C:\Program Files\Support Tools>w32tm /monitor
    SERVERX.fplus.local [192.168.0.2]:
    ICMP: 0ms delay.
    NTP: error ERROR_TIMEOUT - no response from server in 1000ms
    SERVER4-1-DC.fplus.local *** PDC *** [192.168.200.14]:
    ICMP: 0ms delay.
    NTP: +0.0000000s offset from SERVER4-1-DC.fplus.local
    RefID: (unknown) [207.46.232.182]
    sdc.fplus.local [192.168.0.17]:
    ICMP: 0ms delay.
    NTP: -0.0261423s offset from SERVER4-1-DC.fplus.local
    RefID: SERVER4-1-DC.fplus.local [192.168.200.14]

    And


    ......................... SERVERX passed test NetLogons
    Starting test: Advertising
    Warning: `SERVERX is not advertising as a time server.
    ......................... SERVERX failed test Advertising

    It says that FPDC is not advertising as a time server, I have try everything with net sart and w32tm but on no avail. Besides my DNS is functiong but I could see some sporadic poblems here and there.

    What I would like know is how to redesgn former PDC wich is not only on eof DCs.

  • #2
    Re: Warning: Server is not advertising as a time server

    try w32tm /resync /rediscover
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Warning: Server is not advertising as a time server

      C:\Documents and Settings\aleksandar>w32tm /resync
      Sending resync command to local computer...
      The computer did not resync because no time data was available.

      I might have solved my problem. I have put MaxNegPhaseCorrection and
      MaxPosPhaseCorrection to maximum value ffffffffff (somewhere I have read that
      is default), and it works. Then I decreased these values, the old message
      reappaer. Therefore I had to go back, and I have run (it is strange I had
      to do that several times or it migh be some time delay to comply with):

      net stop w32time && net start w32time
      w32tm /resync /rediscover
      w32 /monitor

      My question is why is that? They recomend 48 hours?

      I do not have any GPO in relation with windows timing... I am not sure that
      I have done that in proper way.

      Comment


      • #4
        Re: Warning: Server is not advertising as a time server

        not sure sorry buddy
        Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

        Comment

        Working...
        X