Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



lamphax

Member
  • Content count

    3
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lamphax

  1. For those who run into this issue... My problem was solved by reading the diagnostic steps in the article referenced by Charlow: http://www.mmmug.co.uk/files/216/download.aspx Step Number 15 on Page 13: 15. Check the Default Domain Controllers group policy and the Default Domain group policy and any others that could affect the PDCe or other DCs. Check the following areas: Computer configuration/Administrative Templates /System/Windows Time service/Time Providers Ensure that all three settings listed are set to “not configured”. Sure enough, the first two entries where set to "Enabled" and after setting them to "Not Configured" and restarting the time service all was well and time was synced. Thank you very much to all who responded to this thread. Lamphax Windows_Time_and_the_W32TM_service.doc
  2. Ok I will schedule the reboot Monday and see if that helps, I need a good laugh so I sure hope this works LOL. Thanks for the reply and have a good weekend.
  3. Hello, I am resurecting this post because it seams to be the closest anyone has been to a resolution for this problem. tcpip.sys is version 5.2.3790.2709 As my trouble is to the letter the same as the first post, I would like to pick up where Charlie left off and do a trace but I am not sure how to do that; can someone explain? The output of w32tm /monitor from a client machine seems to show that all of my "BDC's" are synced to the PDC but the PDC is synced to its own internal clock: C:\>w32tm /monitor dc4.mydomain.com [172.16.2.5]: ICMP: 8ms delay. NTP: +0.0033296s offset from dc1.mydomain.com RefID: dc1.mydomain.com [10.1.1.1] dc3.mydomain.com [10.1.1.17]: ICMP: 0ms delay. NTP: -0.0384710s offset from dc1.mydomain.com RefID: dc1.mydomain.com [10.1.1.1] dc2.mydomain.com [10.1.1.23]: ICMP: 0ms delay. NTP: -0.0175720s offset from dc1.mydomain.com RefID: dc1.mydomain.com [10.1.1.1] dc1.mydomain.com *** PDC *** [10.1.1.1]: ICMP: 0ms delay. NTP: +0.0000000s offset from dc1.mydomain.com RefID: 'LOCL' [76.79.67.76] <-- shouldn't this be the IP of my time server time.mydomain.com [10.1.1.67] Thanks in advance for suggestions.
×