DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
2862 time always year 2000
- anparkinson
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 47
- Thank yous received: 0
19 Apr 2020 12:49 #95992
by anparkinson
2862 time always year 2000 was created by anparkinson
Every time I reboot the 2862 the time goes to 1 Jan 200 and doesn't update.
No time server address works and if I manually update from browser time by hitting the "inquire time" button it works.
How can I get to auto update time on reboot?
No time server address works and if I manually update from browser time by hitting the "inquire time" button it works.
How can I get to auto update time on reboot?
Please Log in or Create an account to join the conversation.
- hornbyp
- Offline
- Big Contributor
Less
More
- Posts: 1323
- Thank yous received: 0
19 Apr 2020 14:42 #95993
by hornbyp
Replied by hornbyp on topic Re: 2862 time always year 2000
Defaulting back to 1st Jan 2000 is normal - there's no clock hardware in the router.
If you put the address of a working NTP server in the relevant field, there's no obvious reason why it wouldn't work, that I can think of (other than underlying DNS problems etc).
The ideal server to use, is that run by your ISP (assuming they have one).
You can test your chosen server, with the "W32TM " command. For example :-
[note: It's /computer S , not /computer . (You can test several at once)]
Some ntp server addresses :-
Zen Internet : ntp0.zen.co.uk
Virginmedia : ntp.virginmedia.com (is accessible via my Zen connection)
Manchester Uni : ntp0.mcc.ac.uk,ntp1.mcc.ac.uk,ntp2.mcc.ac.uk,ntp3.mcc.ac.uk
Microsoft? : time.windows.com
(Time.windows.com and ntp.virginmedia.com don't respond to ICMP/aren't pingable, but that doesn't affect their NTP functionality)
If you put the address of a working
The ideal server to use, is that run by your ISP (assuming they have one).
You can test your chosen server, with the "W32TM
[note: It's /computer
Code:
c:\>w32tm /monitor /computers:ntp0.zen.co.uk
ntp0.zen.co.uk[212.23.8.6:123]:
ICMP: 14ms delay
NTP: +0.4071740s offset from local clock
RefID: ntp1.linx.net [195.66.241.3]
Stratum: 2
Warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses.
Some ntp server addresses :-
Zen Internet
Virginmedia
Manchester Uni
Microsoft?
(Time.windows.com and ntp.virginmedia.com don't respond to ICMP/aren't pingable, but that doesn't affect their NTP functionality)
Please Log in or Create an account to join the conversation.
- akwe-xavante
- Offline
- Member
Less
More
- Posts: 107
- Thank yous received: 0
27 Apr 2020 16:01 #96042
by akwe-xavante
Replied by akwe-xavante on topic Re: 2862 time always year 2000
On reboot and regaining internet access it can take a good few minutes for the time to correct itself. That's my experience.
Please Log in or Create an account to join the conversation.
Moderators: Chris
Copyright © 2025 DrayTek