![]() by: jimmym August 13th, 2007 |
It´s now 2083, August 25
This is the log from my most recent sync attempt:
SYNC-ATTEMPT Host: time.nist.gov Aug-13-2007 08:20:16 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: ben.cs.wisc.edu Aug-13-2007 08:20:23 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: bigben.cac.washington.edu Aug-13-2007 08:20:31 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: bitsy.mit.edu Aug-13-2007 08:20:38 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: canon.inria.fr Aug-13-2007 08:20:45 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: chronos.univ-rennes1.fr Aug-13-2007 08:20:52 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: clepsydra.dec.com Aug-13-2007 08:20:59 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: clock.cmc.ec.gc.ca Aug-13-2007 08:21:06 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: clock.isc.org Aug-13-2007 08:21:14 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: clock.llnl.gov Aug-13-2007 08:21:21 FAIL: Response From Time Server Timed Out SYNC-ATTEMPT Host: clock.nc.fukuoka-u.ac.jp Aug-13-2007 08:21:28 SUCCESS 67078.8981597222 39307.5149209606 -27771.3832387616! I´m running XP Pro, and WT ver 5.5.5.478. Please tell me how I should address this problem, as it screws up all my site licenses, etc., Much TIA Jimmy |
![]() by: rodgould@netscape.ne August 17th, 2007 |
It´s now 2083, August 25
Thank you Jimmy. Well done. I am a bit of a novice here and would never have worked out how to achieve the fix. I did not realise that such files were held on our own systems rather than on the WT server.
Thanks again . . . Rod |
![]() by: jimmym August 15th, 2007 |
It´s now 2083, August 25
At risk of breaching netiquette by responding to my own post, I wrote: "Now all we have to do is figure out how to get it out of the server list?".
This worked: with Notepad, open wtservers.wtd in your World Time folder. Delete the line containing "clock.nc.fukuoka-u.ac.jp" (no quotes) and save the file. WT won´t check the time against this inaccurate server again. Leave the "over 45 minutes" box checked, in case there my be other grossly inaccurate servers in the list. Jimmy |
![]() by: sbaker August 14th, 2007 |
It´s now 2083, August 25
It sounds to me like that server has a problem - I´d suggest removing it from your list.
It´s for precisely this reason that the more then 45min warning is there - don´t click "Yes" when it´s obvious that the time will be set incorrectly by the time server. --
Fair Winds, and watch for squalls from leeward. |
![]() by: jimmym August 14th, 2007 |
It´s now 2083, August 25
Thanks, Rod, I had set the 45-minute warning, too, and did what you did, with the same result, happily, so it´s still 2007 :-).
I guess it had to be the time server in Japan? Now all we have to do is figure out how to get it out of the server list? Jimmy |
![]() by: rodgould@netscape.ne August 13th, 2007 |
It´s now 2083, August 25
This is happening to me also. When I do a synch, it stops at the Fukuoka clock and tells me the time will change by more than 45 minutes, do I wish to continue? ´Yes´ takes me to 2083, ´No´ continues cycling thru the clocks and correctly completes the synchronisation.
|
RSS feed | Feed Description |
---|---|
![]() |
Complete RSS feed |
![]() |
RSS feed for: WorldTime Support |
A Rich Site Summary (RSS) feed is an xml data file that provides a summary of the information contained here. It is not designed to be viewed in your browser, but instead by rss reader software. If you do not know what this means - you can safely ignore it, as it is provided for advanced users with rss reader software only. |