Re: help with windows time service

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 /manualpeerlist:peers /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


.

Relevant Pages

  • Re: Windows Server 2003 Windows Time Sync
    ... You have to configure in the domain only the PDCEmulator for the external time source. ... a time service provider, the time service will correct itself. ... I have basically configured window time sync on each server to ...
    (microsoft.public.windows.server.general)
  • Re: system hangs- logging w32time errors
    ... Ethernet adapter Local Area Connection: ... the time service shouldn't create this kind of errors. ... The errors occur because you server has no external time ... With "peers" you can set the time source, ...
    (microsoft.public.windows.server.general)
  • Re: system hangs- logging w32time errors
    ... the time service shouldn't create this kind of errors. ... The errors occur because you server has no external time source setup. ... So if you have internet available you can choose an external time server and sync the time. ... With "peers" you can set the time source, either DNS name or an ip address from a reliable time source. ...
    (microsoft.public.windows.server.general)
  • Re: time sync
    ... machines on my lan can sync to those sources, ... Is the Windows time service started? ... no, this is a stand alone workgroup file and print sharing, web server, ... it seems like the server is not sending the udp ...
    (microsoft.public.windows.server.setup)
  • Re: Windows Server 2003 Windows Time Sync
    ... "Meinolf Weber" wrote: ... to configure in the domain only the PDCEmulator for the external time source. ... a time service provider, the time service will correct itself. ... I have basically configured window time sync on each server to ...
    (microsoft.public.windows.server.general)