NTP warning

  • Thread starter Thread starter Canuck geoff
  • Start date Start date
C

Canuck geoff

Guest
Hi:

I have a series of Win2000 servers that were formerly connecting for NTP to
my client's site via a backend connection. A security finding meant they had
to be redirected internally to our UNIX server as an NTP source. The
machines are all stand alone machines, and they are regularly giving the
warning below. When I try a manual update using w32tm -once everthing
appears to work just fine as shown.

The documentation (and even the options) seem to be conflicting, and from
what I read net time is deprecated. Any assistance would be appreciated.

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 11
Date: 4/7/2008
Time: 6:44:35 PM
User: N/A
Computer: CAVCX102AVIV
Description:
The NTP server didn't respond
Data:
0000: 49 27 00 00 I'..

__________________________________________________________

w32tm -once
W32Time: BEGIN:InitAdjIncr
<snip>

W32Time: BEGIN:TimeDiff
W32Time: ClockError --37433
W32Time: END Line 2542
W32Time: BEGIN:FCheckTimeSanity
W32Time: Adjusting time by 37433 ms. No eventlog messages since time
diffe
rence is 0 <1 minute
W32Time: END Line 570
 
Re: NTP warning

What is it about the Event that you don't understand?

-Frank

"Canuck geoff" <Canuckgeoff@discussions.microsoft.com> wrote in message
news:4B1893D6-1E22-412A-952E-4CA517D43154@microsoft.com...
> Hi:
>
> I have a series of Win2000 servers that were formerly connecting for NTP
> to
> my client's site via a backend connection. A security finding meant they
> had
> to be redirected internally to our UNIX server as an NTP source. The
> machines are all stand alone machines, and they are regularly giving the
> warning below. When I try a manual update using w32tm -once everthing
> appears to work just fine as shown.
>
> The documentation (and even the options) seem to be conflicting, and from
> what I read net time is deprecated. Any assistance would be appreciated.
>
> Event Type: Warning
> Event Source: w32time
> Event Category: None
> Event ID: 11
> Date: 4/7/2008
> Time: 6:44:35 PM
> User: N/A
> Computer: CAVCX102AVIV
> Description:
> The NTP server didn't respond
> Data:
> 0000: 49 27 00 00 I'..
>
> __________________________________________________________
>
> w32tm -once
> W32Time: BEGIN:InitAdjIncr
> <snip>
>
> W32Time: BEGIN:TimeDiff
> W32Time: ClockError --37433
> W32Time: END Line 2542
> W32Time: BEGIN:FCheckTimeSanity
> W32Time: Adjusting time by 37433 ms. No eventlog messages since time
> diffe
> rence is 0 <1 minute
> W32Time: END Line 570
 
Re: NTP warning

What i don't understand is why I am getting NTP server not responding.
While i can apparently talk to the NTP server by manually launching an
update I am getting daily failures when it tries automatically. The size of
the offset convinces me that the automatic updates are not working (note that
I have drifted by 37 s over the last month since I made the change from a
different NTP server.

"Frankster" wrote:

> What is it about the Event that you don't understand?
>
> -Frank
>
> "Canuck geoff" <Canuckgeoff@discussions.microsoft.com> wrote in message
> news:4B1893D6-1E22-412A-952E-4CA517D43154@microsoft.com...
> > Hi:
> >
> > I have a series of Win2000 servers that were formerly connecting for NTP
> > to
> > my client's site via a backend connection. A security finding meant they
> > had
> > to be redirected internally to our UNIX server as an NTP source. The
> > machines are all stand alone machines, and they are regularly giving the
> > warning below. When I try a manual update using w32tm -once everthing
> > appears to work just fine as shown.
> >
> > The documentation (and even the options) seem to be conflicting, and from
> > what I read net time is deprecated. Any assistance would be appreciated.
> >
> > Event Type: Warning
> > Event Source: w32time
> > Event Category: None
> > Event ID: 11
> > Date: 4/7/2008
> > Time: 6:44:35 PM
> > User: N/A
> > Computer: CAVCX102AVIV
> > Description:
> > The NTP server didn't respond
> > Data:
> > 0000: 49 27 00 00 I'..
> >
> > __________________________________________________________
> >
> > w32tm -once
> > W32Time: BEGIN:InitAdjIncr
> > <snip>
> >
> > W32Time: BEGIN:TimeDiff
> > W32Time: ClockError --37433
> > W32Time: END Line 2542
> > W32Time: BEGIN:FCheckTimeSanity
> > W32Time: Adjusting time by 37433 ms. No eventlog messages since time
> > diffe
> > rence is 0 <1 minute
> > W32Time: END Line 570

>
>
 
Back
Top