I have two windows 2003 server and i have been troubleshooting this for
weeks. No matter what i do the time goes back four minutes. The following is
below.
Master 2003 Server
Primary 2003 Server (getting source time from Master)
Ran these steps on the master:
1. Log on to the domain controller.
2. 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.
3. 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. The time is update to the internal
NTP box, but within 20- 30 seconds it goes back to the original time that's
about 4 minutes behind. Crazy.
Please let me know if you can assist me on this.
John
W32tm /config /syncfromflags:domhier /update
net stop w32time && net start w32time
W32tm /resync /rediscover
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"John" <Jo...@discussions.microsoft.com> wrote in message
news:E9DB055B-0711-4F7C...@microsoft.com...
Should i run this on both domain controllers? also i dont now if this is my
problem but I have 7 other windows 2003 servers that are part of the domain
should i stop the time service on them?
thanks for your help.
John
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
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
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" <Jo...@discussions.microsoft.com> wrote in message
news:4D05F2C9-31C7-4188...@microsoft.com...
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
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"John" <Jo...@discussions.microsoft.com> wrote in message
news:54E70F99-30F1-4EF3...@microsoft.com...
thanks for all your help on this issue.
I figured out the issue with the time. The resolution was MS Virtual Server
was overriding the NTP server. Unchecked the time setting on VS and woola the
time on the DC did not go back. YAHOOOOOOO
John
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"John" <Jo...@discussions.microsoft.com> wrote in message
news:01326CB4-C4BC-4927...@microsoft.com...