Empathy List Archives

MS

Mike Suhar

Thu, May 17, 2007 12:59 AM

I am not familiar with the Meinberg software so I am guessing that if you
are running that NTP software you would not be using Windows time service?
If you don't need Windows time service, go into services and stop the
windows time service and set it to "manual" or "disabled". My thinking is
the Windows time service may be conflicting with your time software.

Mike
W8RKO

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Joseph Gray
Sent: Wednesday, May 16, 2007 7:20 PM
To: Discussion of precise time and frequency measurement
Subject: [time-nuts] NTP problem on Windows

I am running the Meinberg NTP software on two PCs. Both PCs are running
WinXP w/SP2, both are on the same network and both are syncing to servers at

pool.ntp.org. In the past, both clocks have shown that the two PCs had the
same time. Today, I just noticed that one of the PCs is running about 9
seconds fast, compared to my Casio WWVB watch.

As far as I know, nothing has changed to account for the difference. The PC
that is fast has been running without a reboot for three months. Does anyone

have any ideas?

time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

I am not familiar with the Meinberg software so I am guessing that if you are running that NTP software you would not be using Windows time service? If you don't need Windows time service, go into services and stop the windows time service and set it to "manual" or "disabled". My thinking is the Windows time service may be conflicting with your time software. Mike W8RKO -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Joseph Gray Sent: Wednesday, May 16, 2007 7:20 PM To: Discussion of precise time and frequency measurement Subject: [time-nuts] NTP problem on Windows I am running the Meinberg NTP software on two PCs. Both PCs are running WinXP w/SP2, both are on the same network and both are syncing to servers at pool.ntp.org. In the past, both clocks have shown that the two PCs had the same time. Today, I just noticed that one of the PCs is running about 9 seconds fast, compared to my Casio WWVB watch. As far as I know, nothing has changed to account for the difference. The PC that is fast has been running without a reboot for three months. Does anyone have any ideas? _______________________________________________ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

JG

Joseph Gray

Thu, May 17, 2007 1:12 AM

I am not familiar with the Meinberg software so I am guessing that if you
are running that NTP software you would not be using Windows time service?
If you don't need Windows time service, go into services and stop the
windows time service and set it to "manual" or "disabled". My thinking is
the Windows time service may be conflicting with your time software.

Mike
W8RKO

Already done. Thanks for trying.

>I am not familiar with the Meinberg software so I am guessing that if you > are running that NTP software you would not be using Windows time service? > If you don't need Windows time service, go into services and stop the > windows time service and set it to "manual" or "disabled". My thinking is > the Windows time service may be conflicting with your time software. > > Mike > W8RKO Already done. Thanks for trying.

BH

Bill Hawkins

Thu, May 17, 2007 2:45 AM

Ah, well. You seem to have all the bases covered, except for the 9
second error. How about using a freeware SNTP client with those IP
addresses. The client needs to keep a log; maybe you will need some
shareware. I use Tardis and YATS32.

The log will show you gross errors, like seconds. SNTP logs the
request time, the receipt time at the server, the sent time at the
server and the receipt time at your PC.

Dunno about Meinberg. Prefer the Brandenberg Concertos myself.

Bill Hawkins

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Joseph Gray
Sent: Wednesday, May 16, 2007 8:13 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] NTP problem on Windows

I am not familiar with the Meinberg software so I am guessing that if
you are running that NTP software you would not be using Windows time

service?

If you don't need Windows time service, go into services and stop the

windows time service and set it to "manual" or "disabled". My thinking

is the Windows time service may be conflicting with your time

software.

Mike
W8RKO

Already done. Thanks for trying.

time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

Ah, well. You seem to have all the bases covered, except for the 9 second error. How about using a freeware SNTP client with those IP addresses. The client needs to keep a log; maybe you will need some shareware. I use Tardis and YATS32. The log will show you gross errors, like seconds. SNTP logs the request time, the receipt time at the server, the sent time at the server and the receipt time at your PC. Dunno about Meinberg. Prefer the Brandenberg Concertos myself. Bill Hawkins -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Joseph Gray Sent: Wednesday, May 16, 2007 8:13 PM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] NTP problem on Windows >I am not familiar with the Meinberg software so I am guessing that if >you are running that NTP software you would not be using Windows time service? > If you don't need Windows time service, go into services and stop the >windows time service and set it to "manual" or "disabled". My thinking >is the Windows time service may be conflicting with your time software. > > Mike > W8RKO Already done. Thanks for trying. _______________________________________________ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

BG

Björn Gabrielsson

Thu, May 17, 2007 4:10 AM

The reference NTP implementation - of which Meinberg provides a packaged
M$WIN-version - is perfectly capable of logging.

Adding a few more servers to each PC and maybe adding the other PC as a
server would make faultfinding easier.

--

Björn

On Thu, May 17, 2007 4:45, Bill Hawkins said:

Ah, well. You seem to have all the bases covered, except for the 9
second error. How about using a freeware SNTP client with those IP
addresses. The client needs to keep a log; maybe you will need some
shareware. I use Tardis and YATS32.

The log will show you gross errors, like seconds. SNTP logs the
request time, the receipt time at the server, the sent time at the
server and the receipt time at your PC.

Dunno about Meinberg. Prefer the Brandenberg Concertos myself.

Bill Hawkins

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Joseph Gray
Sent: Wednesday, May 16, 2007 8:13 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] NTP problem on Windows

I am not familiar with the Meinberg software so I am guessing that if
you are running that NTP software you would not be using Windows time

service?

If you don't need Windows time service, go into services and stop the

windows time service and set it to "manual" or "disabled". My thinking

is the Windows time service may be conflicting with your time

software.

Mike
W8RKO

Already done. Thanks for trying.

time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

The reference NTP implementation - of which Meinberg provides a packaged M$WIN-version - is perfectly capable of logging. Adding a few more servers to each PC and maybe adding the other PC as a server would make faultfinding easier. -- Björn On Thu, May 17, 2007 4:45, Bill Hawkins said: > Ah, well. You seem to have all the bases covered, except for the 9 > second error. How about using a freeware SNTP client with those IP > addresses. The client needs to keep a log; maybe you will need some > shareware. I use Tardis and YATS32. > > The log will show you gross errors, like seconds. SNTP logs the > request time, the receipt time at the server, the sent time at the > server and the receipt time at your PC. > > Dunno about Meinberg. Prefer the Brandenberg Concertos myself. > > Bill Hawkins > > > -----Original Message----- > From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On > Behalf Of Joseph Gray > Sent: Wednesday, May 16, 2007 8:13 PM > To: Discussion of precise time and frequency measurement > Subject: Re: [time-nuts] NTP problem on Windows > >>I am not familiar with the Meinberg software so I am guessing that if >>you are running that NTP software you would not be using Windows time > service? >> If you don't need Windows time service, go into services and stop the > >>windows time service and set it to "manual" or "disabled". My thinking > >>is the Windows time service may be conflicting with your time > software. >> >> Mike >> W8RKO > > Already done. Thanks for trying. > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >

JG

Joseph Gray

Thu, May 17, 2007 4:23 AM

As a test, I just restarted the NTP service on the PC that was off. It is
now keeping the correct time. Strange.

----- Original Message -----
From: "Björn Gabrielsson" bg@lysator.liu.se
To: "Discussion of precise time and frequency measurement"
time-nuts@febo.com
Sent: Wednesday, May 16, 2007 10:10 PM
Subject: Re: [time-nuts] NTP problem on Windows

The reference NTP implementation - of which Meinberg provides a packaged
M$WIN-version - is perfectly capable of logging.

Adding a few more servers to each PC and maybe adding the other PC as a
server would make faultfinding easier.

--

Björn

On Thu, May 17, 2007 4:45, Bill Hawkins said:

Ah, well. You seem to have all the bases covered, except for the 9
second error. How about using a freeware SNTP client with those IP
addresses. The client needs to keep a log; maybe you will need some
shareware. I use Tardis and YATS32.

The log will show you gross errors, like seconds. SNTP logs the
request time, the receipt time at the server, the sent time at the
server and the receipt time at your PC.

Dunno about Meinberg. Prefer the Brandenberg Concertos myself.

Bill Hawkins

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Joseph Gray
Sent: Wednesday, May 16, 2007 8:13 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] NTP problem on Windows

I am not familiar with the Meinberg software so I am guessing that if
you are running that NTP software you would not be using Windows time

service?

If you don't need Windows time service, go into services and stop the

windows time service and set it to "manual" or "disabled". My thinking

is the Windows time service may be conflicting with your time

software.

Mike
W8RKO

Already done. Thanks for trying.

time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

As a test, I just restarted the NTP service on the PC that was off. It is now keeping the correct time. Strange. ----- Original Message ----- From: "Björn Gabrielsson" <bg@lysator.liu.se> To: "Discussion of precise time and frequency measurement" <time-nuts@febo.com> Sent: Wednesday, May 16, 2007 10:10 PM Subject: Re: [time-nuts] NTP problem on Windows The reference NTP implementation - of which Meinberg provides a packaged M$WIN-version - is perfectly capable of logging. Adding a few more servers to each PC and maybe adding the other PC as a server would make faultfinding easier. -- Björn On Thu, May 17, 2007 4:45, Bill Hawkins said: > Ah, well. You seem to have all the bases covered, except for the 9 > second error. How about using a freeware SNTP client with those IP > addresses. The client needs to keep a log; maybe you will need some > shareware. I use Tardis and YATS32. > > The log will show you gross errors, like seconds. SNTP logs the > request time, the receipt time at the server, the sent time at the > server and the receipt time at your PC. > > Dunno about Meinberg. Prefer the Brandenberg Concertos myself. > > Bill Hawkins > > > -----Original Message----- > From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On > Behalf Of Joseph Gray > Sent: Wednesday, May 16, 2007 8:13 PM > To: Discussion of precise time and frequency measurement > Subject: Re: [time-nuts] NTP problem on Windows > >>I am not familiar with the Meinberg software so I am guessing that if >>you are running that NTP software you would not be using Windows time > service? >> If you don't need Windows time service, go into services and stop the > >>windows time service and set it to "manual" or "disabled". My thinking > >>is the Windows time service may be conflicting with your time > software. >> >> Mike >> W8RKO > > Already done. Thanks for trying. > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > _______________________________________________ time-nuts mailing list time-nuts@febo.com https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

RN

Rasputin Novgorod

Thu, May 17, 2007 4:36 AM

--- Joseph Gray jgray@zianet.com wrote:

As a test, I just restarted the NTP service on the PC that was off.
It is now keeping the correct time. Strange.

Not so strange.

I routinely reboot all of our Windows machines; otherwise
they become flaky and unreliable. Win 98 needed to be
done about twice a day or they'd crash. Win 2000 will often
last several days. Linux boxes never need rebooting...

/b

____________________________________________________________________________________Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433

--- Joseph Gray <jgray@zianet.com> wrote: > As a test, I just restarted the NTP service on the PC that was off. > It is now keeping the correct time. Strange. Not so strange. I routinely reboot all of our Windows machines; otherwise they become flaky and unreliable. Win 98 needed to be done about twice a day or they'd crash. Win 2000 will often last several days. Linux boxes never need rebooting... /b ____________________________________________________________________________________Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433

JG

Joseph Gray

Thu, May 17, 2007 5:35 AM

I use Linux as well as Windows, where appropriate. In this case, I did not
reboot the Windows system in question. I only restarted the NTP service,
which is a port of the opensource NTP daemon by Meinberg. I know Windows
bashing is a popular sport, but in this case, I don't think it is
applicable. Over the years, I have had problems on Linux systems as well.

----- Original Message -----
From: "Rasputin Novgorod" priapulus@yahoo.com
To: "Discussion of precise time and frequency measurement"
time-nuts@febo.com
Sent: Wednesday, May 16, 2007 10:36 PM
Subject: Re: [time-nuts] NTP problem on Windows

--- Joseph Gray jgray@zianet.com wrote:

As a test, I just restarted the NTP service on the PC that was off.
It is now keeping the correct time. Strange.

Not so strange.

I routinely reboot all of our Windows machines; otherwise
they become flaky and unreliable. Win 98 needed to be
done about twice a day or they'd crash. Win 2000 will often
last several days. Linux boxes never need rebooting...

/b

____________________________________________________________________________________Be
a better Heartthrob. Get better relationship answers from someone who
knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433

time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

I use Linux as well as Windows, where appropriate. In this case, I did not reboot the Windows system in question. I only restarted the NTP service, which is a port of the opensource NTP daemon by Meinberg. I know Windows bashing is a popular sport, but in this case, I don't think it is applicable. Over the years, I have had problems on Linux systems as well. ----- Original Message ----- From: "Rasputin Novgorod" <priapulus@yahoo.com> To: "Discussion of precise time and frequency measurement" <time-nuts@febo.com> Sent: Wednesday, May 16, 2007 10:36 PM Subject: Re: [time-nuts] NTP problem on Windows > > --- Joseph Gray <jgray@zianet.com> wrote: > >> As a test, I just restarted the NTP service on the PC that was off. >> It is now keeping the correct time. Strange. > > Not so strange. > > I routinely reboot all of our Windows machines; otherwise > they become flaky and unreliable. Win 98 needed to be > done about twice a day or they'd crash. Win 2000 will often > last several days. Linux boxes never need rebooting... > > /b > > > > ____________________________________________________________________________________Be > a better Heartthrob. Get better relationship answers from someone who > knows. Yahoo! Answers - Check it out. > http://answers.yahoo.com/dir/?link=list&sid=396545433 > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > >

JH

Jack Hudler

Thu, May 17, 2007 3:46 PM

Nicely said! Beats my caustic thoughts!

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Joseph Gray
Sent: Thursday, May 17, 2007 12:35 AM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] NTP problem on Windows

I use Linux as well as Windows, where appropriate. In this case, I did not
reboot the Windows system in question. I only restarted the NTP service,
which is a port of the opensource NTP daemon by Meinberg. I know Windows
bashing is a popular sport, but in this case, I don't think it is
applicable. Over the years, I have had problems on Linux systems as well.

Nicely said! Beats my caustic thoughts! -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Joseph Gray Sent: Thursday, May 17, 2007 12:35 AM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] NTP problem on Windows I use Linux as well as Windows, where appropriate. In this case, I did not reboot the Windows system in question. I only restarted the NTP service, which is a port of the opensource NTP daemon by Meinberg. I know Windows bashing is a popular sport, but in this case, I don't think it is applicable. Over the years, I have had problems on Linux systems as well.

time-nuts@lists.febo.com

Re: [time-nuts] Looking for Wavecrest Visi