help with windows time service

Hi all,
my desktops are not syncing right with the server time.
I followed instructions to edit Windows 2003 SP2 registry and change path :
Windows Time Service
Logon
Local Account
interact with desktops box is checked (tried with and without check)
path: %systemroot%\system32\svchost_w32time.exe -k Local Service
This got rid of the 1079 error I was receiving and started the windows Time
Service.
Also made sure Local Service was in the dc policy permissions
Workstation is Windows Xp Pro SP3:
when I typed in net time:
current time at serverx is 4/8/2009 1:35pm
Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm

The correct time was 2:35pm but the workstation time was showing 1:35pm
In the event log :
The time service is now synchronizing the system time with the time source
serverx.xxxx.org
ntp.d 192.168.1.xxx:123->192.168.1.server address
What am I missing??? The workstation does not have the set daylight time
auto checked.
This was setup and worked before I installed SP1 and SP2 on 2003 server. I
also have a 2000 server that is running AD and acting as a DC too.
Windows Time is setup on it also.
Can someone point me in the right direction? Does group policies have
something to do with it. I think I am just using the system clock for the
time.
Thanks in advance,
Sher

 

Hello Sher,

Make sure no firewall is blocking port 123 UDP which the time service needs.
In a domain the PDCEmulator is the time source, best is to sync that one
with an external time server. All other DC's sync with that one and member
servers and workstations sync with one available DC.

To find the PDCEmulator in your domain run:

netdom query fsmo

in a command prompt.



To sync the PDCEmulator with an external time source choose this:

w32tm /config /manualpeerlisteers /syncfromflags:manual /reliable:yes /update

With "peers" you can set the time source, either DNS name (time.windows.com)
or an ip address from a reliable time source.

Here you can find some of them:
http://www.pool.ntp.org/


To reconfigure a client computer for automatic domain time synchronization:

w32tm /config /syncfromflags:domhier /update

After that run:
net stop w32time
net start w32time

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi all,
> my desktops are not syncing right with the server time.
> I followed instructions to edit Windows 2003 SP2 registry and change
> path :
> Windows Time Service
> Logon
> Local Account
> interact with desktops box is checked (tried with and without
> check)
> path: %systemroot%\system32\svchost_w32time.exe -k Local Service
> This got rid of the 1079 error I was receiving and started the windows
> Time
> Service.
> Also made sure Local Service was in the dc policy permissions
> Workstation is Windows Xp Pro SP3:
> when I typed in net time:
> current time at serverx is 4/8/2009 1:35pm
> Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
> The correct time was 2:35pm but the workstation time was showing
> 1:35pm
> In the event log :
> The time service is now synchronizing the system time with the time
> source
> serverx.xxxx.org
> ntp.d 192.168.1.xxx:123->192.168.1.server address
> What am I missing??? The workstation does not have the set daylight
> time
> auto checked.
> This was setup and worked before I installed SP1 and SP2 on 2003
> server. I
> also have a 2000 server that is running AD and acting as a DC too.
> Windows Time is setup on it also.
> Can someone point me in the right direction? Does group policies have
> something to do with it. I think I am just using the system clock for
> the
> time.
> Thanks in advance,
> Sher

 

Thanks for your answer. I found that my server1 which is a Windows 2000 SP4
server dc is the one running FSMO. I also have a 2003 SP2 dc.
What I found out after testing is:
The computer does not sync until I check the auto daylight savings box on
the workstation. I have to manually set the correct time. Then if I change
the time to the wrong time within a few minutes the time syncs with the
server time.
It appears that the syncing is working but changing the daylight time is not.
What I mean is that this week the computers reset their time as if the
daylight savings time had changed even though the daylights savings box was
not checked. I manually changed the server1 and the 2003 server to the
correct time, but the workstations would not sync with them until I checked
the daylight savings time on the workstation (the workstations already had
central time as the time zone).
This is what happened in the fall when the time changes took place and I had
to uncheck the daylight savings time button.
The workstation has windows time set to logon as local account but the box
is not checked that says allow service to interact with desktop.
My server1 does not appear to be using an outside time source but that is
not a problem as I can always manually change that server for now.
Any thoughts on why the syncing seems to work but not the daylight time. Do
I have something set wrong (like the box to allow service to interact with
desktop. It is checked on both servers but not on the workstations.
Thanks again for your help
Sher



"Meinolf Weber [MVP-DS]" wrote:

> Hello Sher,
>
> Make sure no firewall is blocking port 123 UDP which the time service needs.
> In a domain the PDCEmulator is the time source, best is to sync that one
> with an external time server. All other DC's sync with that one and member
> servers and workstations sync with one available DC.
>
> To find the PDCEmulator in your domain run:
>
> netdom query fsmo
>
> in a command prompt.
>
>
>
> To sync the PDCEmulator with an external time source choose this:
>
> w32tm /config /manualpeerlisteers /syncfromflags:manual /reliable:yes /update
>
> With "peers" you can set the time source, either DNS name (time.windows.com)
> or an ip address from a reliable time source.
>
> Here you can find some of them:
> http://www.pool.ntp.org/
>
>
> To reconfigure a client computer for automatic domain time synchronization:
>
> w32tm /config /syncfromflags:domhier /update
>
> After that run:
> net stop w32time
> net start w32time
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hi all,
> > my desktops are not syncing right with the server time.
> > I followed instructions to edit Windows 2003 SP2 registry and change
> > path :
> > Windows Time Service
> > Logon
> > Local Account
> > interact with desktops box is checked (tried with and without
> > check)
> > path: %systemroot%\system32\svchost_w32time.exe -k Local Service
> > This got rid of the 1079 error I was receiving and started the windows
> > Time
> > Service.
> > Also made sure Local Service was in the dc policy permissions
> > Workstation is Windows Xp Pro SP3:
> > when I typed in net time:
> > current time at serverx is 4/8/2009 1:35pm
> > Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
> > The correct time was 2:35pm but the workstation time was showing
> > 1:35pm
> > In the event log :
> > The time service is now synchronizing the system time with the time
> > source
> > serverx.xxxx.org
> > ntp.d 192.168.1.xxx:123->192.168.1.server address
> > What am I missing??? The workstation does not have the set daylight
> > time
> > auto checked.
> > This was setup and worked before I installed SP1 and SP2 on 2003
> > server. I
> > also have a 2000 server that is running AD and acting as a DC too.
> > Windows Time is setup on it also.
> > Can someone point me in the right direction? Does group policies have
> > something to do with it. I think I am just using the system clock for
> > the
> > time.
> > Thanks in advance,
> > Sher
>
>
>

 

Ok, I found out that when I try to telnet to the server1 192.168.1.x 123 that
I can't connect on port 123 but my sonicwall device is not blocking that port
and windows firewall is turned off on the workstations. Where else would I
look? I did a netstat on the server and a port 123 did not show up.
Any suggestions?
Thanks,
Sherrry

"Sher" wrote:

> Thanks for your answer. I found that my server1 which is a Windows 2000 SP4
> server dc is the one running FSMO. I also have a 2003 SP2 dc.
> What I found out after testing is:
> The computer does not sync until I check the auto daylight savings box on
> the workstation. I have to manually set the correct time. Then if I change
> the time to the wrong time within a few minutes the time syncs with the
> server time.
> It appears that the syncing is working but changing the daylight time is not.
> What I mean is that this week the computers reset their time as if the
> daylight savings time had changed even though the daylights savings box was
> not checked. I manually changed the server1 and the 2003 server to the
> correct time, but the workstations would not sync with them until I checked
> the daylight savings time on the workstation (the workstations already had
> central time as the time zone).
> This is what happened in the fall when the time changes took place and I had
> to uncheck the daylight savings time button.
> The workstation has windows time set to logon as local account but the box
> is not checked that says allow service to interact with desktop.
> My server1 does not appear to be using an outside time source but that is
> not a problem as I can always manually change that server for now.
> Any thoughts on why the syncing seems to work but not the daylight time. Do
> I have something set wrong (like the box to allow service to interact with
> desktop. It is checked on both servers but not on the workstations.
> Thanks again for your help
> Sher
>
>
>
> "Meinolf Weber [MVP-DS]" wrote:
>
> > Hello Sher,
> >
> > Make sure no firewall is blocking port 123 UDP which the time service needs.
> > In a domain the PDCEmulator is the time source, best is to sync that one
> > with an external time server. All other DC's sync with that one and member
> > servers and workstations sync with one available DC.
> >
> > To find the PDCEmulator in your domain run:
> >
> > netdom query fsmo
> >
> > in a command prompt.
> >
> >
> >
> > To sync the PDCEmulator with an external time source choose this:
> >
> > w32tm /config /manualpeerlisteers /syncfromflags:manual /reliable:yes /update
> >
> > With "peers" you can set the time source, either DNS name (time.windows.com)
> > or an ip address from a reliable time source.
> >
> > Here you can find some of them:
> > http://www.pool.ntp.org/
> >
> >
> > To reconfigure a client computer for automatic domain time synchronization:
> >
> > w32tm /config /syncfromflags:domhier /update
> >
> > After that run:
> > net stop w32time
> > net start w32time
> >
> > Best regards
> >
> > Meinolf Weber
> > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> > no rights.
> > ** Please do NOT email, only reply to Newsgroups
> > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >
> >
> > > Hi all,
> > > my desktops are not syncing right with the server time.
> > > I followed instructions to edit Windows 2003 SP2 registry and change
> > > path :
> > > Windows Time Service
> > > Logon
> > > Local Account
> > > interact with desktops box is checked (tried with and without
> > > check)
> > > path: %systemroot%\system32\svchost_w32time.exe -k Local Service
> > > This got rid of the 1079 error I was receiving and started the windows
> > > Time
> > > Service.
> > > Also made sure Local Service was in the dc policy permissions
> > > Workstation is Windows Xp Pro SP3:
> > > when I typed in net time:
> > > current time at serverx is 4/8/2009 1:35pm
> > > Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
> > > The correct time was 2:35pm but the workstation time was showing
> > > 1:35pm
> > > In the event log :
> > > The time service is now synchronizing the system time with the time
> > > source
> > > serverx.xxxx.org
> > > ntp.d 192.168.1.xxx:123->192.168.1.server address
> > > What am I missing??? The workstation does not have the set daylight
> > > time
> > > auto checked.
> > > This was setup and worked before I installed SP1 and SP2 on 2003
> > > server. I
> > > also have a 2000 server that is running AD and acting as a DC too.
> > > Windows Time is setup on it also.
> > > Can someone point me in the right direction? Does group policies have
> > > something to do with it. I think I am just using the system clock for
> > > the
> > > time.
> > > Thanks in advance,
> > > Sher
> >
> >
> >

 

Meinolf Weber thanks,
Ok now I understand your solution but does this work on a Windows server
2000 sp4 as my FMSO is one. Or do I need to do this on my 2003 dc and not
run windows time on my 2000 FMSO server?
If I set the peers to time.windows.com then do I need to add this to my dns
list?
Sorry I got really confused as to what I was seeing happen and then got off
track as to the solution.

"Sher" wrote:

> Hi all,
> my desktops are not syncing right with the server time.
> I followed instructions to edit Windows 2003 SP2 registry and change path :
> Windows Time Service
> Logon
> Local Account
> interact with desktops box is checked (tried with and without check)
> path: %systemroot%\system32\svchost_w32time.exe -k Local Service
> This got rid of the 1079 error I was receiving and started the windows Time
> Service.
> Also made sure Local Service was in the dc policy permissions
> Workstation is Windows Xp Pro SP3:
> when I typed in net time:
> current time at serverx is 4/8/2009 1:35pm
> Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
>
> The correct time was 2:35pm but the workstation time was showing 1:35pm
> In the event log :
> The time service is now synchronizing the system time with the time source
> serverx.xxxx.org
> ntp.d 192.168.1.xxx:123->192.168.1.server address
> What am I missing??? The workstation does not have the set daylight time
> auto checked.
> This was setup and worked before I installed SP1 and SP2 on 2003 server. I
> also have a 2000 server that is running AD and acting as a DC too.
> Windows Time is setup on it also.
> Can someone point me in the right direction? Does group policies have
> something to do with it. I think I am just using the system clock for the
> time.
> Thanks in advance,
> Sher

 

Hi Cher

For 2000 DC's, they use ntp, not NT5DS like 2003/xp. Run in CMD "net time
/sentsntpDCemulatorname.F.Q.D.N

You can run net time /querysntp to see the current situ
--
Garry Starck
MCITP, MCTS AD, MCSE 2003 Messaging, MCDBA


"Sher" wrote:

> Meinolf Weber thanks,
> Ok now I understand your solution but does this work on a Windows server
> 2000 sp4 as my FMSO is one. Or do I need to do this on my 2003 dc and not
> run windows time on my 2000 FMSO server?
> If I set the peers to time.windows.com then do I need to add this to my dns
> list?
> Sorry I got really confused as to what I was seeing happen and then got off
> track as to the solution.
>
> "Sher" wrote:
>
> > Hi all,
> > my desktops are not syncing right with the server time.
> > I followed instructions to edit Windows 2003 SP2 registry and change path :
> > Windows Time Service
> > Logon
> > Local Account
> > interact with desktops box is checked (tried with and without check)
> > path: %systemroot%\system32\svchost_w32time.exe -k Local Service
> > This got rid of the 1079 error I was receiving and started the windows Time
> > Service.
> > Also made sure Local Service was in the dc policy permissions
> > Workstation is Windows Xp Pro SP3:
> > when I typed in net time:
> > current time at serverx is 4/8/2009 1:35pm
> > Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
> >
> > The correct time was 2:35pm but the workstation time was showing 1:35pm
> > In the event log :
> > The time service is now synchronizing the system time with the time source
> > serverx.xxxx.org
> > ntp.d 192.168.1.xxx:123->192.168.1.server address
> > What am I missing??? The workstation does not have the set daylight time
> > auto checked.
> > This was setup and worked before I installed SP1 and SP2 on 2003 server. I
> > also have a 2000 server that is running AD and acting as a DC too.
> > Windows Time is setup on it also.
> > Can someone point me in the right direction? Does group policies have
> > something to do with it. I think I am just using the system clock for the
> > time.
> > Thanks in advance,
> > Sher

 

Sher wrote:
>Hi all,
>my desktops are not syncing right with the server time.
>I followed instructions to edit Windows 2003 SP2 registry and change path :
>Windows Time Service
>Logon
> Local Account
> interact with desktops box is checked (tried with and without check)
>path: %systemroot%\system32\svchost_w32time.exe -k Local Service
>This got rid of the 1079 error I was receiving and started the windows Time
>Service.
>Also made sure Local Service was in the dc policy permissions
>Workstation is Windows Xp Pro SP3:
>when I typed in net time:
>current time at serverx is 4/8/2009 1:35pm
>Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
>
>The correct time was 2:35pm but the workstation time was showing 1:35pm
>In the event log :
>The time service is now synchronizing the system time with the time source
>serverx.xxxx.org
>ntp.d 192.168.1.xxx:123->192.168.1.server address
>What am I missing??? The workstation does not have the set daylight time
>auto checked.
>This was setup and worked before I installed SP1 and SP2 on 2003 server. I
>also have a 2000 server that is running AD and acting as a DC too.
>Windows Time is setup on it also.
>Can someone point me in the right direction? Does group policies have
>something to do with it. I think I am just using the system clock for the
>time.
>Thanks in advance,
>Sher

Solution: Please change the CMOS battrey of client machine.

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-server/200904/1

 

Hello Sher,

If you have newer OS DC i would first move the FSMO roles to the newest one,
not a must but most admins i know doing it that way.

You can do it according to this, no downtime or reboot needed:
http://support.microsoft.com/kb/324801

For the new PDCEmulator check this ones:
http://technet.microsoft.com/en-us/library/cc786897.aspx

On the 2000 DC use the command Garry provided you:
net time /setsntpDCemulatorname.F.Q.D.N

then restart the time service on it.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Meinolf Weber thanks,
> Ok now I understand your solution but does this work on a Windows
> server
> 2000 sp4 as my FMSO is one. Or do I need to do this on my 2003 dc and
> not
> run windows time on my 2000 FMSO server?
> If I set the peers to time.windows.com then do I need to add this to
> my dns
> list?
> Sorry I got really confused as to what I was seeing happen and then
> got off
> track as to the solution.
> "Sher" wrote:
>
>> Hi all,
>> my desktops are not syncing right with the server time.
>> I followed instructions to edit Windows 2003 SP2 registry and change
>> path :
>> Windows Time Service
>> Logon
>> Local Account
>> interact with desktops box is checked (tried with and without check)
>> path: %systemroot%\system32\svchost_w32time.exe -k Local Service
>> This got rid of the 1079 error I was receiving and started the
>> windows Time
>> Service.
>> Also made sure Local Service was in the dc policy permissions
>> Workstation is Windows Xp Pro SP3:
>> when I typed in net time:
>> current time at serverx is 4/8/2009 1:35pm
>> Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
>> The correct time was 2:35pm but the workstation time was showing
>> 1:35pm
>> In the event log :
>> The time service is now synchronizing the system time with the time
>> source
>> serverx.xxxx.org
>> ntp.d 192.168.1.xxx:123->192.168.1.server address
>> What am I missing??? The workstation does not have the set daylight
>> time
>> auto checked.
>> This was setup and worked before I installed SP1 and SP2 on 2003
>> server. I
>> also have a 2000 server that is running AD and acting as a DC too.
>> Windows Time is setup on it also.
>> Can someone point me in the right direction? Does group policies
>> have
>> something to do with it. I think I am just using the system clock
>> for the
>> time.
>> Thanks in advance,
>> Sher

 

Hello Sher,

If the local computer has problems with the time, check the CMOS battery.
Very often this causes time problems when it is empty.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks for your answer. I found that my server1 which is a Windows
> 2000 SP4
> server dc is the one running FSMO. I also have a 2003 SP2 dc.
> What I found out after testing is:
> The computer does not sync until I check the auto daylight savings box
> on
> the workstation. I have to manually set the correct time. Then if I
> change
> the time to the wrong time within a few minutes the time syncs with
> the
> server time.
> It appears that the syncing is working but changing the daylight time
> is not.
> What I mean is that this week the computers reset their time as if the
> daylight savings time had changed even though the daylights savings
> box was
> not checked. I manually changed the server1 and the 2003 server to the
> correct time, but the workstations would not sync with them until I
> checked
> the daylight savings time on the workstation (the workstations
> already had
> central time as the time zone).
> This is what happened in the fall when the time changes took place and
> I had
> to uncheck the daylight savings time button.
> The workstation has windows time set to logon as local account but the
> box
> is not checked that says allow service to interact with desktop.
> My server1 does not appear to be using an outside time source but
> that is
> not a problem as I can always manually change that server for now.
> Any thoughts on why the syncing seems to work but not the daylight
> time. Do
> I have something set wrong (like the box to allow service to interact
> with
> desktop. It is checked on both servers but not on the workstations.
> Thanks again for your help
> Sher
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello Sher,
>>
>> Make sure no firewall is blocking port 123 UDP which the time service
>> needs. In a domain the PDCEmulator is the time source, best is to
>> sync that one with an external time server. All other DC's sync with
>> that one and member servers and workstations sync with one available
>> DC.
>>
>> To find the PDCEmulator in your domain run:
>>
>> netdom query fsmo
>>
>> in a command prompt.
>>
>> To sync the PDCEmulator with an external time source choose this:
>>
>> w32tm /config /manualpeerlisteers /syncfromflags:manual
>> /reliable:yes /update
>>
>> With "peers" you can set the time source, either DNS name
>> (time.windows.com) or an ip address from a reliable time source.
>>
>> Here you can find some of them:
>> http://www.pool.ntp.org/
>> To reconfigure a client computer for automatic domain time
>> synchronization:
>>
>> w32tm /config /syncfromflags:domhier /update
>>
>> After that run:
>> net stop w32time
>> net start w32time
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hi all,
>>> my desktops are not syncing right with the server time.
>>> I followed instructions to edit Windows 2003 SP2 registry and change
>>> path :
>>> Windows Time Service
>>> Logon
>>> Local Account
>>> interact with desktops box is checked (tried with and without
>>> check)
>>> path: %systemroot%\system32\svchost_w32time.exe -k Local Service
>>> This got rid of the 1079 error I was receiving and started the
>>> windows
>>> Time
>>> Service.
>>> Also made sure Local Service was in the dc policy permissions
>>> Workstation is Windows Xp Pro SP3:
>>> when I typed in net time:
>>> current time at serverx is 4/8/2009 1:35pm
>>> Local Time (GMT-05:00) at serverx is 4/8/2009 2:35pm
>>> The correct time was 2:35pm but the workstation time was showing
>>> 1:35pm
>>> In the event log :
>>> The time service is now synchronizing the system time with the time
>>> source
>>> serverx.xxxx.org
>>> ntp.d 192.168.1.xxx:123->192.168.1.server address
>>> What am I missing??? The workstation does not have the set daylight
>>> time
>>> auto checked.
>>> This was setup and worked before I installed SP1 and SP2 on 2003
>>> server. I
>>> also have a 2000 server that is running AD and acting as a DC too.
>>> Windows Time is setup on it also.
>>> Can someone point me in the right direction? Does group policies
>>> have
>>> something to do with it. I think I am just using the system clock
>>> for
>>> the
>>> time.
>>> Thanks in advance,
>>> Sher