Re: Time Sync on a Windows 2003 Server

check if the following links help you with the problem:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/maintain/opsguide/part1/adogd15.mspx
http://technet2.microsoft.com/windowsserver/en/library/ad131391-c018-4016-b61f-cd2ab0d8e0f71033.mspx?mfr=true
http://technet2.microsoft.com/windowsserver/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx?mfr=true


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:54E70F99-30F1-4EF3-B298-2E087C9B50CB@xxxxxxxxxxxxxxxx
Jorge or Paul

Ok, still lost on this issue.

What I have done on this issue so far.

2003 Domain Controller A

w32tm /configure /manualpeerlist:192.168.X.X /syncfromflags:manual /update
net stop w32time && net start w23time
w32tm /resync /rediscover

The time does sync to my ntp server (which is current) 192.168.x.x for about
20 seconds and goes back about 4 minutes.

Setup debug and the only thing i noticed is that it sync with external ntp
cisco and two or three statements down i saw that the time stamp changed but
i didnt see any errors.

Figuring that it might be my internal NTP server issue. I ran the above
commands and pointed to tock.usno.navy.mil with the same results.

I verified that the GPO at Expand Computer Configuration / Administrative
Templates / System / Windows Time Service.
Windows NTP Client, Configure Windows NTP Client, Windows NTP Server all
were selected not Configured.


2003 Domain Controller B and 2003 Member Servers
Have not touch it yet, do to the fact that I can get first domain to work.

I appreciate your help with this. I know that i have faith to narrow this
issue out.

John



"John" wrote:

thanks, i will try this and let you know.

"Jorge Silva" wrote:

> The CMD
>
> w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes
> /update
>
> is to run on PDCe at Root Level f your forest, the other ones (that I > gave
> you) are to be run in all others.
>
> You can use the w32tm /monitor switch to check from wich server are the
> machines sync.
>
> -- > I hope that the information above helps you.
> Have a Nice day.
>
> Jorge Silva
> MCSE, MVP Directory Services
> "John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4D05F2C9-31C7-4188-97CC-F6EC0A2D78B7@xxxxxxxxxxxxxxxx
> > Paul,
> >
> > thanks for reply. what i've done so far I ran on the domain > > controller.
> >
> > Type the following command to display the time difference between the
> > local computer and a target computer, and then press ENTER:
> >
> > w32tm /stripchart /computer:target/samples:1/dataonly
> >
> > target specifies the internal NTP server on the network.
> >
> > Type the following command to configure the PDC emulator and then > > press
> > ENTER:
> >
> > w32tm /config /manualpeerlist:peers /syncfromflags:manual > > /reliable:yes
> > /update
> >
> > Peers i enter the IP address of the internal NTP server.
> >
> > Then I type w32tm /resync /rediscover.
> >
> > on the other domain controller. i Just entered at a dos prombt net > > time to
> > make sure it's pulling the time from mastersecondary 2003 server > > which it
> > was. the other 2003 servers I did nothing yet. So I believe from both
> > responses. I need to ensure that my primary domain controller is in > > sync
> > with
> > my internal NTP server and run
> > the command below on the second domain controller and all other > > Windows
> > 2003
> > servers.
> >
> > W32tm /config /syncfromflags:domhier /update
> > net stop w32time && net start w32time
> > W32tm /resync /rediscover
> >
> >
> > the problem is that the main domain controller is configured to point > > to
> > the
> > internal NTP box and it updates to the correct time then in 20 - 30
> > seconds
> > it just goes back to 4 to 5 minutes.
> >
> > I'm lost.
> >
> > John
> >
> >
> > "Paul Williams [MVP]" wrote:
> >
> >> The commands that Jorge gave you only need to be run on machines > >> that are
> >> configured to synchronise time when they shouldn't be. So, you > >> don't run
> >> this command on your PDCe. You run this command on any machines > >> that are
> >> configured to use an NTP server as opposed to the domain hierarchy
> >> (Nt5Ds).
> >>
> >> Have you tried configuring time on all your servers, or just on the
> >> second
> >> DC?
> >>
> >> -- > >> Paul Williams
> >> Microsoft MVP - Windows Server - Directory Services
> >> http://www.msresource.net | http://forums.msresource.net
> >>
> >>
> >>
> >>
> >>
>
>

.

Relevant Pages

  • Re: Time Sync on a Windows 2003 Server
    ... Jorge Silva ... MCSE, MVP Directory Services ... was overriding the NTP server. ... > 2003 Domain Controller B and 2003 Member Servers ...
    (microsoft.public.windows.server.active_directory)
  • Re: w32tm - Missing registry keys
    ... I am trying to set my SBS2000 domain controller to ... This is the procedure I follow to configure my SBS server to ... synchronize with the U.S. NTP server pool and to act as an NTP server ... Enable the NTP client with the following command: ...
    (microsoft.public.windows.server.sbs)
  • Re: Time Sync on a Windows 2003 Server
    ... Figuring that it might be my internal NTP server issue. ... I verified that the GPO at Expand Computer Configuration / Administrative ... Windows NTP Client, Configure Windows NTP Client, Windows NTP Server all ... 2003 Domain Controller B and 2003 Member Servers ...
    (microsoft.public.windows.server.active_directory)
  • RE: [Maybe SPAM] Re: how to set time on the cluster nodes
    ... "scshutdown" command, rebooted in non-cluster mode & set the same time ... Subject: Re: how to set time on the cluster nodes ... Hi Sanjay, ... as an ntp server, you can use the ntpdate command... ...
    (SunManagers)
  • Re: win xp pro sp3, dst, file timestamps also changed
    ... Mike Lynch ... If you have internet access, you should use a public NTP server to set ... bring up a command prompt and enter the following ...
    (microsoft.public.windowsxp.help_and_support)
Quantcast