Windows Clock gains 24 hours

[Guest]

Before I describe the problem, let me say that I have done a scan of the
machine with Spybot, AdAware and VET Antivirus. I'm running Windows XP Home
SP2

The Windows clock will GAIN exactly 24 hours at random - the machine is on
24/7 via a ZyXel 660H DSL router. My time zone is correctly set (GMT +8h no
daylight saving), and I have tried enabling and disabling the time server
synchronisation option in the Time & Date properties without success. I have
manually synchronised the clock using a free program called WebTime that
connects to atomic clock time servers, but this makes no difference. When the
Windows clock is wrong, the wrong time is also displayed in the BIOS
settings. The router also synchronises to a time server (a different one),
but the router time is never incorrect. Interestingly, the clock told me that
today was Thursday instead of Wednesday, and when I chose 'update now' to
synchronise with time.windows.com in the time/date properties, it says that
time has successfully been synchronised with time.windows.com , yet STILL
gave me Thursday 9th as the synchronised date. The computer is only six
months old, so I don't immediately suspect the clock battery - particularly
as the clock leaps forward exactly one day and doesn't accrue several minutes
over a period of time.

For those who know what these things mean, I have included some additional
info below. Any help would be appreciated. Thanks

SNTP value is: time.windows.com,0x1

Windows IP Configuration

Host Name . . . . . . . . . . . . : xxx
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Eth
ernet NIC
Physical Address. . . . . . . . . : xxx
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Thursday, 9 March 2006 8:26:04 PM
Lease Expires . . . . . . . . . . : Sunday, 12 March 2006 8:26:04 PM

 

[Carey Frisch [MVP]]

Open your BIOS and make sure the day, date and time
are set correctly therein.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

---------------------------------------------------------------------------­----------------

:

| Before I describe the problem, let me say that I have done a scan of the
| machine with Spybot, AdAware and VET Antivirus. I'm running Windows XP Home
| SP2
|
| The Windows clock will GAIN exactly 24 hours at random - the machine is on
| 24/7 via a ZyXel 660H DSL router. My time zone is correctly set (GMT +8h no
| daylight saving), and I have tried enabling and disabling the time server
| synchronisation option in the Time & Date properties without success. I have
| manually synchronised the clock using a free program called WebTime that
| connects to atomic clock time servers, but this makes no difference. When the
| Windows clock is wrong, the wrong time is also displayed in the BIOS
| settings. The router also synchronises to a time server (a different one),
| but the router time is never incorrect. Interestingly, the clock told me that
| today was Thursday instead of Wednesday, and when I chose 'update now' to
| synchronise with time.windows.com in the time/date properties, it says that
| time has successfully been synchronised with time.windows.com , yet STILL
| gave me Thursday 9th as the synchronised date. The computer is only six
| months old, so I don't immediately suspect the clock battery - particularly
| as the clock leaps forward exactly one day and doesn't accrue several minutes
| over a period of time.
|
| For those who know what these things mean, I have included some additional
| info below. Any help would be appreciated. Thanks
|
| SNTP value is: time.windows.com,0x1
|
| Windows IP Configuration
|
| Host Name . . . . . . . . . . . . : xxx
| Primary Dns Suffix . . . . . . . :
| Node Type . . . . . . . . . . . . : Unknown
| IP Routing Enabled. . . . . . . . : No
| WINS Proxy Enabled. . . . . . . . : No
|
| Ethernet adapter Local Area Connection:
|
| Connection-specific DNS Suffix . :
| Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
| Eth
| ernet NIC
| Physical Address. . . . . . . . . : xxx
| Dhcp Enabled. . . . . . . . . . . : Yes
| Autoconfiguration Enabled . . . . : Yes
| IP Address. . . . . . . . . . . . : 192.168.1.33
| Subnet Mask . . . . . . . . . . . : 255.255.255.0
| Default Gateway . . . . . . . . . : 192.168.1.1
| DHCP Server . . . . . . . . . . . : 192.168.1.1
| DNS Servers . . . . . . . . . . . : 192.168.1.1
| Lease Obtained. . . . . . . . . . : Thursday, 9 March 2006 8:26:04 PM
| Lease Expires . . . . . . . . . . : Sunday, 12 March 2006 8:26:04 PM

 

[Guest]

Open your BIOS and make sure the day, date and time
are set correctly therein.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

Thanks Carey

I've just checked the BIOS day, date and time are correct.

Nigel

 

[Guest]

You can try running the following commands:

Start / Run / CMD
Net stop w32time
w32tm /unregister
w32tm /unregister
w32tm /register
Net start w32time

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

 

[Guest]

You can try running the following commands:

Start / Run / CMD
Net stop w32time
w32tm /unregister
w32tm /unregister
w32tm /register
Net start w32time

Hi Carey

I've just run those commands and it all seemed to go OK, so what has that
sequence done? I take it I just wait and see how it goes over the next few
days?

Thanks

Nigel

 

[Guest]

One other thing that I have only just noticed is that within the Privacy tab
of Windows Media Player 10 Options, there is a check box 'set clock on
devices automatically' - it was checked and I've now unchecked it, but
whether it has any bearing on this problem I don't know.