Configuring Domain Time

Time on my Domain is often incorrect. Clients are either correct or 3 minutes off.  Apparently when off, they are syncing to the BDC.  I've attempted syncing with NTP servers, but so far NG. everything stays the same.  Here are the results of command w32tm /monitor:

From HSIAD01  (PDC  server 2003)

C:\Users\administrator.HSINJ>w32tm /monitor
HSIEX2.hsinj[192.168.1.23:123]:
    ICMP: 1ms delay
    NTP: -1.7156790s offset from hsiad01.hsinj
        RefID: 'LOCL' [0x4C434F4C]
        Stratum: 1
hsiad01.hsinj *** PDC ***[192.168.1.11:123]:
    ICMP: 0ms delay
    NTP: +0.0000000s offset from hsiad01.hsinj
        RefID: 'LOCL' [0x4C434F4C]
        Stratum: 1
HSIAD02.hsinj[[fe80::c4a8:68c5:cb99:9357%12]:123]:
    ICMP: 0ms delay
    NTP: -191.2808937s offset from hsiad01.hsinj
        RefID: 80.84.77.86.rev.sfr.net [86.77.84.80]
        Stratum: 2


From HSIAD02: (SDC  Virtualized 2012 Server)

C:\Users\administrator.HSINJ>w32tm /monitor
HSIEX2.hsinj[192.168.1.23:123]:
    ICMP: 1ms delay
    NTP: -1.7156790s offset from hsiad01.hsinj
        RefID: 'LOCL' [0x4C434F4C]
        Stratum: 1
hsiad01.hsinj *** PDC ***[192.168.1.11:123]:
    ICMP: 0ms delay
    NTP: +0.0000000s offset from hsiad01.hsinj
        RefID: 'LOCL' [0x4C434F4C]
        Stratum: 1
HSIAD02.hsinj[[fe80::c4a8:68c5:cb99:9357%12]:123]:
    ICMP: 0ms delay
    NTP: -191.2808937s offset from hsiad01.hsinj
        RefID: 80.84.77.86.rev.sfr.net [86.77.84.80]
        Stratum: 2
       

From HSIEX2  (2003 Exchange Server)  


C:\Users\administrator.HSINJ>w32tm /monitor
HSIEX2.hsinj[192.168.1.23:123]:
    ICMP: 1ms delay
    NTP: -1.7156790s offset from hsiad01.hsinj
        RefID: 'LOCL' [0x4C434F4C]
        Stratum: 1
hsiad01.hsinj *** PDC ***[192.168.1.11:123]:
    ICMP: 0ms delay
    NTP: +0.0000000s offset from hsiad01.hsinj
        RefID: 'LOCL' [0x4C434F4C]
        Stratum: 1
HSIAD02.hsinj[[fe80::c4a8:68c5:cb99:9357%12]:123]:
    ICMP: 0ms delay
    NTP: -191.2808937s offset from hsiad01.hsinj
        RefID: 80.84.77.86.rev.sfr.net [86.77.84.80]
        Stratum: 2
adone36Asked:
Who is Participating?
 
rick81Commented:
have you corrected the time on your server?
0
 
Tony GiangrecoCommented:
Take these commands and save them in a batch file. Add a daily scheduled task to run the file and it will keep your server's time up to date.

net stop w32time
net start w32time
w32tm /config /manualpeerlist:129.6.15.28,0x8 /syncfromflags:MANUAL /reliable:yes /update
w32tm /resync /rediscover
net stop w32time
net start w32time

I've used it before for the same problem.
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
Tony GiangrecoCommented:
Did the script work for you?
0
 
adone36Author Commented:
I haven't had a chance to try it yet. Previously I had tried something from Microsoft's tech pages that used a 3 server manual peer list. I ran it on these 3 servers, commands were said to have succeeded, but still some computers were 3 min off.
0
 
Tony GiangrecoCommented:
I have that script running on one of my clients servers everyday. It takes a minute to create the batch file.  Just double click the file and it runs in 15 seconds. It's that quick to test. It doesn't affect anything else.
0
 
adone36Author Commented:
My problems are coming from HSIAD02 the SDC. If I run the script it says each command is successful and withing a second or two the time reverts to 3 minutes off again.
0
 
Tony GiangrecoCommented:
Create a manual ad cd replication script. Run it on that dc right before and right after the time sync script completes
0
 
Tony GiangrecoCommented:
That's dc not cd
0
 
adone36Author Commented:
The problem is worse. Client pcs cannot run reports because of the time difference between them and our sequel servers.

HSIAD01 (PDC) shows it is syncing with windows.time.com and time.nist.gov. It has the correct time.

HSIEX2 (Exch Serv) shows correct time.

HSIAD02 (SDC) is off by 8 minutes. Even if I stop the time service, time is off. I've used the commands:

net stop w32time
net start w32time
w32tm /config /syncfromflags:MANUAL /manualpeerlist:"time.windows.com,0x1 time.nist.gov,0x1" /reliable:yes /update
w32tm /resync /rediscover
net stop w32time
net start w32time

Both HSIAD02 and HSIEX2 registries say parameters for time sync type is NTP (the 2 time servers in the above command), so how can they have different times??

How can I find where this machine and the incorrect clients are getting this 8 min off time from???
0
 
Tony GiangrecoCommented:
Update the time on one dc and run all the repl commands that sync the dc's. It works perfect for my  3 dc's, two member servers and. 45 workstations
0
 
adone36Author Commented:
Issue fixed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.