Internet time

  • Thread starter Thread starter Rod Speed
  • Start date Start date
R

Rod Speed

Weird. I've just noticed that my laptop always synchs up 5 mins later
than the other systems on the lan and it has done that for months.

While its normally connected to the lan by wireless, I get
exactly the same result when its plugged into the lan too.

Makes no difference which time server I use.

Completely standard XP Home, and the manual resynchs
are quite happy, just gets the time wrong by 5 mins.
 
Rod Speed said:
Weird. I've just noticed that my laptop always synchs up 5 mins later
than the other systems on the lan and it has done that for months.

While its normally connected to the lan by wireless, I get
exactly the same result when its plugged into the lan too.

Makes no difference which time server I use.

Completely standard XP Home, and the manual resynchs
are quite happy, just gets the time wrong by 5 mins.

get a Mac.

sounds like more flakey intel/amd hardware
 
Weird. I've just noticed that my laptop always synchs up 5 mins later
than the other systems on the lan and it has done that for months.

Prolly not the same issue here, but accessing one proggy on one of the
servers at work always stops the clock on my pc until this proggy is
fully loaded.
 
Prolly not the same issue here, but accessing one proggy on one of the
servers at work always stops the clock on my pc until this proggy is
fully loaded.

****ing DUH!
 
DogFart said:
Prolly not the same issue here,
Correct.

but accessing one proggy on one of the servers at work always
stops the clock on my pc until this proggy is fully loaded.

Cant be that in this case, the time is fast 5 mins
immediately after its just got updated manually.
 
Rod said:
Cant be that in this case, the time is fast 5 mins
immediately after its just got updated manually.

Is this particular laptop 5 mins east of your other computers -
BWAHAHAHAHAHAAA! 5 mins east - get it? That would make it 5 mins fast
if you've set it to continuous timezone gradations. I guess for that to
work, you'd also need a GPS unit attached so it knows exactly where it
is. And for the GPS to work inside, you'd need a glass or open roof.
Then again, maybe your laptop is crowded with those hackers that don't
exist and couldn't possibly have successfully hacked one of your
wireless computers BWAHAHAHAAHAHA!

--
______ ___ __
/_ __/_ __/ _ )_______ ___ _/ /_____ ____
/ / / // / _ / __/ -_) _ `/ '_/ -_) __/
/_/ \_, /____/_/ \__/\_,_/_/\_\\__/_/
/___/

There are 10 types of people in this world; those who understand the
binary numbering system and those who don't.

There's no place like 127.0.0.1.

ASCII a silly question, get a silly ANSI.
 
TyBreaker said:
Rod Speed wrote
Is this particular laptop 5 mins east of your other computers -

Nope, and we have timezones, stupid.
BWAHAHAHAHAHAAA! 5 mins east - get it? That would make it 5 mins fast
if you've set it to continuous timezone gradations. I guess for that to
work, you'd also need a GPS unit attached so it knows exactly where it
is. And for the GPS to work inside, you'd need a glass or open roof.
Then again, maybe your laptop is crowded with those hackers that don't
exist and couldn't possibly have successfully hacked one of your wireless
computers BWAHAHAHAAHAHA!

Gone blind yet child ?
 
DogFart <[email protected]>, the babbling freeloader and older
brown-eye miner who likes blood-thirsty copulation with armadillos, and
whose partner is a cab-moll with a generous hair pie, wrote in

You dumb ****.



--
Lunch was Nice;
Lousy rooster hymen and offensive running sore with defective dolphin
infection, dished up in a randomly twitching pail containing medium-rare
artichoke, stringy bits of conch and cartilage, spit, a side of fruit
and a glass of sputum.
 
Weird. I've just noticed that my laptop always synchs up 5 mins later
than the other systems on the lan and it has done that for months.

While its normally connected to the lan by wireless, I get
exactly the same result when its plugged into the lan too.

Makes no difference which time server I use.

Completely standard XP Home, and the manual resynchs
are quite happy, just gets the time wrong by 5 mins.

I point my computers at au.pool.ntp.org and their web site mentions that
it is possible to come up with variations in time by a few minutes
because it depends on the accuracy of the publicly managed servers in
that pool. I was thinking that one scenario could be that your laptop
has picked up it's time from an NTP server that isn't accurate.

Then again, it could just be your laptop is like you, a few minutes
short of an hour BWAHAHAHAHAAHA!

--
______ ___ __
/_ __/_ __/ _ )_______ ___ _/ /_____ ____
/ / / // / _ / __/ -_) _ `/ '_/ -_) __/
/_/ \_, /____/_/ \__/\_,_/_/\_\\__/_/
/___/

There are 10 types of people in this world; those who understand the
binary numbering system and those who don't.

There's no place like 127.0.0.1.

ASCII a silly question, get a silly ANSI.
 
TyBreaker said:
(e-mail address removed) wrote
I point my computers at au.pool.ntp.org and their web site mentions that
it is possible to come up with variations in time by a few minutes
because it depends on the accuracy of the publicly managed servers in
that pool.

Cant be that, because all of the PCs/laptop are using the same
time server and particularly the one which alarms when the
ABC TV News starts, is always within a second of the real time.
I was thinking that one scenario could be that your laptop has picked up
it's time from an NTP server that isn't accurate.

Nope, its the same one that the others use.
 
Rod Speed said:
Cant be that, because all of the PCs/laptop are using the same
time server and particularly the one which alarms when the
ABC TV News starts, is always within a second of the real time.


Nope, its the same one that the others use.

Just at a guess, your CMOS time and system time are always different and
every time you reboot, the CMOS time resets the system time.
 
Whatcher? said:
Just at a guess, your CMOS time and system time are always different
and every time you reboot, the CMOS time resets the system time.

Doesnt explain why doing a manual update using the internet
time synch produces a system time thats 5 mins in advance.

Guess one possibility come to think of it is that the internet time
synch isnt actually updating the system time for some reason, in
other words the time returned by the synch is just ignored.

Hmm, just fixed it. To test that particular theory, I manually set
the time to about 5 mins earlier than the correct time. Then did
a manual synch with internet time, and its now got the correct time.

So presumably it was binning the internet time for some reason
until I manually set it earlier than the correct time. Weird.
 
Rod Speed said:
Doesnt explain why doing a manual update using the internet
time synch produces a system time thats 5 mins in advance.

It might actually but that goes WAY beyond my programming skills. I think it
depends on which takes priority.
Guess one possibility come to think of it is that the internet time
synch isnt actually updating the system time for some reason, in
other words the time returned by the synch is just ignored.

Hmm, just fixed it. To test that particular theory, I manually set
the time to about 5 mins earlier than the correct time. Then did
a manual synch with internet time, and its now got the correct time.

So presumably it was binning the internet time for some reason
until I manually set it earlier than the correct time. Weird.

So is it now ALWAYS OK? Eg, reboot and resync and is it correct?
 
It might actually

Nope. Easy to prove that its not that by not
rebooting the laptop and still seeing the problem.
but that goes WAY beyond my programming skills.

Its got nothing to do with programming, just basic diagnosis.

If the problem persists with manual internet time synchs
without a reboot of the laptop, it can be the cmos time
because the cmos time isnt being used in that situation.
I think it depends on which takes priority.

Nope, because there is no priority if you dont reboot.
So is it now ALWAYS OK?

Yes. I'll do some more tests tomorrow to see whether the problem
is just the difference between the system time and the internet time
that sees the update ignored. In other words if the amount of time
update is greater than a particular amount of time, it bins the net time.

I know that it does that when the system time is days
wrong, but in that case it does say that the synch has failed
and its hard to see why it would do that with just 5 mins.
Eg, reboot and resync and is it correct?

Yep. Tho if your possibility was what was happening, only a
reboot would be needed to see a reversion to the bad time.

Didnt happen with either a reboot or a resynch.
 
Rod Speed <[email protected]>, the very fat, unpaid employee who
voluntarily committed to working for 30 years in exchange for a
discarded, half-chewed hamburger, cried:
If the problem persists with manual internet time synchs
without a reboot of the laptop, it can be the cmos time
because the cmos time isnt being used in that situation.

****wit.



--
alt.usenet.kooks - Pierre Salinger Memorial Hook, Line & Sinker:
September 2005 and April 2006

ObHint: Just because you argue with a notorious ****wit netk0oK, it
does not necessarily follow that you are not also a ****wit netk0oK.
 
Yes. I'll do some more tests tomorrow to see whether the problem
is just the difference between the system time and the internet time
that sees the update ignored. In other words if the amount of time
update is greater than a particular amount of time, it bins the net time.

I know that it does that when the system time is days
wrong, but in that case it does say that the synch has failed
and its hard to see why it would do that with just 5 mins.

That rings a bell, NTP has a threshold margin. If within the threshold,
it will slow down/speed up the clock until synch is achieved but if
outside the threshold, it can simply fail but it does depend on how NTP
is implemented from O/S to O/S.

--
______ ___ __
/_ __/_ __/ _ )_______ ___ _/ /_____ ____
/ / / // / _ / __/ -_) _ `/ '_/ -_) __/
/_/ \_, /____/_/ \__/\_,_/_/\_\\__/_/
/___/

There are 10 types of people in this world; those who understand the
binary numbering system and those who don't.

There's no place like 127.0.0.1.

ASCII a silly question, get a silly ANSI.
 
TyBreaker said:
Rod Speed
That rings a bell, NTP has a threshold margin. If within the
threshold, it will slow down/speed up the clock until synch is
achieved but if outside the threshold, it can simply fail but it does
depend on how NTP is implemented from O/S to O/S.

Thats not how it works, it just changes the time, one jump of time.
 
Rod Speed said:
Nope. Easy to prove that its not that by not
rebooting the laptop and still seeing the problem.


Its got nothing to do with programming, just basic diagnosis.

If the problem persists with manual internet time synchs
without a reboot of the laptop, it can be the cmos time

I obviously meant it cant be the cmos time.
 
the make-up artist and wigmaker said:
I obviously meant it cant be the cmos time.

You're still a ****wit. It's an ACPI hardware issue, you less than useless
buttmop.



--
alt.usenet.kooks - Pierre Salinger Memorial Hook, Line & Sinker:
September 2005 and April 2006

ObHint: Just because you argue with a notorious ****wit netk0oK, it
does not necessarily follow that you are not also a ****wit netk0oK.
 
Back
Top