Re: Time server
- From: connie <connie@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Jun 2005 03:00:02 -0700
Paul,
Cheers for taking the time to answer.
If I try to put the time on the DC that has a different time to all PC's and
main server to a closer time range, it will revert away back to 7 minutes out
again after a few hours. This seems to show that the DC acting as the PDC
emulator is holding the wrong time as are all the PC's . The only machine
holding the correct time is the machine that is not in sync with the rest,
and this server seems to be syncing externally fine.
The w32tm /config /syncfromflags....doesn't seem to run on the 2000 server,
but if I run
w32tm -s
I get
RPC to local server returned 0x0
Thanks for thinking about this
I haven't had to fiddle with this but I would suggest you get the difference
between the two, to less than 5 minutes. DC's need to protect themselves
from things such as replay attacks.
Go to the system tray, double click on the time and try adjusting the clock
ahead three minutes and wait a day. See if after that time frame the two
don't sync up.
How to Synchronize an Internal Time Server with an External Source
1. Click Start, point to All Programs, point to Accessories, and then
click Command Prompt.
2. Type the following line, where peerlist is a comma-separated list
of Domain Name System (DNS) names or IP addresses of the appropriate time
sources, and then press ENTER:
w32tm /config /syncfromflags:manual /manualpeerlist:peerlist
3. Type w32tm /config /update, and then press ENTER.
Notes: . The most common use of this procedure is to synchronize the
internal network's authoritative time source with a very precise external
time source. However, you can run this procedure on any Windows XP-based
computer.
.. If the computer cannot reach the servers, the procedure does not
succeed and an entry is written to the Event log.
.. You can use computers on the Internet to provide accurate time
information. For example, use the National Institute of Standards and
Technology (NIST), which provides the NIST Network Time service.
--
"Paul Bergson" wrote:
> I haven't had to fiddle with this but I would suggest you get the difference
> between the two, to less than 5 minutes. DC's need to protect themselves
> from things such as replay attacks.
>
> Go to the system tray, double click on the time and try adjusting the clock
> ahead three minutes and wait a day. See if after that time frame the two
> don't sync up.
>
> How to Synchronize an Internal Time Server with an External Source
> 1. Click Start, point to All Programs, point to Accessories, and then
> click Command Prompt.
> 2. Type the following line, where peerlist is a comma-separated list
> of Domain Name System (DNS) names or IP addresses of the appropriate time
> sources, and then press ENTER:
> w32tm /config /syncfromflags:manual /manualpeerlist:peerlist
> 3. Type w32tm /config /update, and then press ENTER.
> Notes: . The most common use of this procedure is to synchronize the
> internal network's authoritative time source with a very precise external
> time source. However, you can run this procedure on any Windows XP-based
> computer.
> . If the computer cannot reach the servers, the procedure does not
> succeed and an entry is written to the Event log.
> . You can use computers on the Internet to provide accurate time
> information. For example, use the National Institute of Standards and
> Technology (NIST), which provides the NIST Network Time service.
>
>
> --
>
>
> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "connie" <connie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:DEED6191-85B3-4365-8332-EB0C337FA4BA@xxxxxxxxxxxxxxxx
> >I wonder if anyone can help. I have 2 DC's in an windows 2000 active
> > directory forest, both DC's have different times, 7 minutes apart. I am
> > unable to get them to synchronise. The DC that holds the PDC fsmo has the
> > incorrect time, as do all pc's on the domain. The other DC, which is
> > holding
> > no roles has the correct time.
> > I have set the incorrect Dc to get it's time from the net using the
> > following
> > net time \\dc-name /setsntp :ntp.cs.tcd.ie
> > This runs succesfully but the time does not correct itself,
> >
> > I have tried to syncronise the DC with the correct time, to the other DC
> > by
> > using the w32tm but it keeps the correct times.
> > The DC with the PDC role is giving the following error
> >
> >
> > Because of repeated network problems, the time service has not been able
> > to
> > find a domain controller to synchronize with for a long time. To reduce
> > network traffic, the time service will wait 960 minutes before trying
> > again.
> > No synchronization will take place during this interval, even if network
> > connectivity is restored. Accumulated time errors may cause certain
> > network
> > operations to fail. To tell the time service that network connectivity has
> > been restored and that it should resynchronize, execute "w32tm /s" from
> > the
> > command line.
> >
> > The DC with the PDC role is giving the following error
> >
> >
> > any help would be much appreciated
>
>
>
.
- Follow-Ups:
- Re: Time server
- From: Paul Bergson
- Re: Time server
- References:
- Time server
- From: connie
- Re: Time server
- From: Paul Bergson
- Time server
- Prev by Date: Re: ADAM Error: "A referral was returned..."
- Next by Date: Re: Controlling object visibility
- Previous by thread: Re: Time server
- Next by thread: Re: Time server
- Index(es):
Relevant Pages
|
