An error occured synchronizing windows with time.windows.com

Okay so I've tried stopping/registering the win32tm service on this Windows Server 2008 Enterprise Computer.

C:\Users\Administrator>net stop w32time
The Windows Time service is stopping.
The Windows Time service was stopped successfully.

C:\Users\Administrator>w32tm /unregister
The following error occurred: Access is denied. (0x80070005)

C:\Users\Administrator>w32tm /unregister
W32Time successfully unregistered.

C:\Users\Administrator>w32tm /register
W32Time successfully registered.

C:\Users\Administrator>net start w32time
The Windows Time service is starting.
The Windows Time service was started successfully.

(Source : http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/9bdfc2cc-4775-4435-8868-57d214e1e3ba/)

And I get this error from the Date and Time, Internet Time tab (After also following the steps here).

_{(source: iforce.co.nz)}

I've even tried the Atomic Time Clock Worldtimeserver and I get the error The following error occurred: The specified module could not be found. (0x8007007E).

I've also disabled the Windows Firewall, that might of been blocking the synchronization.

_{(source: iforce.co.nz)}

I've done a file scan with sfc /scannow that came back with no errors.

C:\Users\Administrator>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\Administrator>

But I'm not having much luck. Is there anyway lo possibly solve this? or is the time.windows.com servers unsupported? because the software is from 2008? (I really don't know :/), My ping result to time.windows.com

C:\Users\Administrator>ping time.windows.com

Pinging time.microsoft.akadns.net [65.55.21.22] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 65.55.21.22:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

And tracert result

C:\Users\Administrator>tracert time.windows.com

Tracing route to time.microsoft.akadns.net [65.55.21.24] over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1 2 32 ms 31 ms 32 ms be2-100.bras1wtc.wlg.vf.net.nz [203.109.129.113]

3 31 ms 32 ms 31 ms be5-100.ppnzwtc01.wlg.vf.net.nz.129.109.203.in-a ddr.arpa [203.109.129.114] 4 31 ms 31 ms 31 ms gi0-2-0-3.ppnzwtc01.wlg.vf.net.nz.180.109.203.in -addr.arpa [203.109.180.210] 5 31 ms 31 ms 30 ms gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz [203.109.180.2 09] 6 167 ms 166 ms 166 ms ip-141.199.31.114.VOCUS.net.au [114.31.199.141]

7 175 ms 175 ms 175 ms microsoft.com.any2ix.coresite.com [206.223.143.1 43] 8 177 ms 180 ms 176 ms xe-7-0-2-0.by2-96c-1a.ntwk.msn.net [207.46.42.17 6] 9 205 ms 205 ms 204 ms xe-10-0-2-0.co1-96c-1b.ntwk.msn.net [207.46.45.3 1] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 ^C

And nslookup

C:\Users\Administrator>nslookup time.windows.com
Server:  UnKnown
Address:  192.168.1.1

Non-authoritative answer:
Name:    time.microsoft.akadns.net
Address:  65.55.21.22
Aliases:  time.windows.com

Its a little late, but you often get that error if your clock is wrong. Shockingly enough, you need to set the clock to a nearly correct time for it to synchronise properly.

Its probably so that if you DID get time related wierdness regularly , you will get off your rear and work out why its happening - its often due to a dead or weak bios battery.