26-05-2019 03:25 PM
my BB2 has been giving me firewall problems because the system time is wrong.
I have the following Time Settings, but it does not auto update:
Automatically synchronise with an Internet time server.
NTP Server : ntp.readytoconnect.co.uk
Solved! See the answer below or view the solution in context.
10-06-2019 07:51 PM - edited 10-06-2019 08:00 PM
Yes, it was fixed but only completely today in the hour running up to 12:20:38.
It came on stream yesterday at 16:15:41 but didn't start syncing every hour until today at 12:20:38.
26-05-2019 03:44 PM - edited 26-05-2019 03:46 PM
These time servers are rubbish. I have similar issues with my routers.
I don't have EE fibre, but try changing your time zone to correspond with your current time, so +1 -1 etc.
I assume you cannot manually set the time.
26-05-2019 03:50 PM
It appears that you cannot change the BB2 time server settings other than to "Disable Automatic Time Server Maintenance", but even then it does not give an option of what time zone to set it to. (i.e the drop-down boxes are not functional)
26-05-2019 06:42 PM
My BB2 works fine with those settings. Try Disabling / Save / Enabling / Save.
26-05-2019 07:16 PM
It does have a connection to the Net? In that state it sounds as if it hasn't authenticated to EE.
Have you just joined EE BB or were you already with EE BB?
What does it say after you log into the router:
Obscure your names & numbers in the BB Username but post the 1st 2 parts of the IP addy.
26-05-2019 08:02 PM
It is connected to the internet OK and I have not had any trouble (until now) with it for the 12+ months I've been with EE.
It works fine but I can no longer use "Access Control" to switch the wifi off at certain times.
26-05-2019 09:05 PM
I should report it to EE as a faulty router, preventing you programming it to your requirements, & ask for a replacement.
27-05-2019 12:24 PM
I'm having the same issue, since the BB2 automagically restarted itself about 36 hours ago. I had never previously noticed an issue with the time sync...
27-05-2019 02:24 PM
Can you run tracert ntp.readytoconnect.co.uk ?
27-05-2019 03:26 PM
Yup, and I'd be happy to post the trace, but you're probably thinking that I don't have connectivity to that machine? (If I'm wrong, sorry! ;-))
In fact the ntp host is pingable and has been since I first noticed the time on the router being incorrect this morning. After verifying that it was pingable, I rebooted the router and still no time sync. I'm used to seeing "Time is synced to NTP server" in the system log, but for some reason it doesn't seem to be logging anything at all about its failure to sync, which is a bit... disappointing 😄
The only thing that I
haven't hadn't tried is to see if the NTP server is actually running on that machine. ** I just did so, from a Linux box elsewhere (i.e. not from my home) and it seems to be failing. Assuming that there's nothing funky (unusual port number?) about this particular NTP server, I'm tempted to conclude that it's unwell.
The readytoconnect.co.uk domain doesn't seem to be owned by EE, which makes it super-weird that they have chosen to make it the NTP server for the BB2 with no means for their users to change the server. It also means that I'm now clueless about how to proceed. EE probably can't fix the NTP server if they don't own it...?
27-05-2019 04:43 PM - edited 27-05-2019 04:44 PM
@Neilski : Well, I only asked 😉!
Once the router has synced to the NTP server it keeps it own time & no longer needs the NTP server. My BB2 last synced to it on 25 May & has been running happily & timely since then. This thread appeared since then on the 26 May. The server musta gone down around then & has not yet come back up. I seem to remember that this has happened once & twice before. All we can do is wait for it to come back up.
EE do own this domain for the time being having bought it from a leading domain host, Namesco. I suppose they wanted a domain to match the quasi-domain they use as the default BB Username of their routers, Of course, where the domain comes from & the server that hosts it needn't be the same. In this case the host is 188.8.131.52 belonging to Entanet. Nevertheless there must be someone in EE responsible for checking it & keeping it running.
31-05-2019 10:57 AM - edited 31-05-2019 12:35 PM
I have had the same problem since my BrightBox 2 router rebooted itself at midnight on 24/25th May. Previously, the router updated itself every hour (or so), the log contained the message "23:25:27 24 May. Time is synced to NTP server" when the router last updated its time.
It seems that since the reboot, the router is not requesting the time from the server.
I haven't noticed the router rebooting itself before; as it's dead on midnight, I assume it was a deliberate remote boot. Was there a firmware update by EE, and the new firmware doesn't request NTP updates?
There are previous discussions in the EE Community about NTP failure when the timeserver at ntp.readytoconnect.co.uk failed in some farcical manner. You cannot configure the router to use any other time service. The domain readytoconnect.co.uk is currently registered and responding to ping today.
31-05-2019 11:22 AM
Neilski points out that "ntp.readytoconnect.co.uk" is not responding to ntp requests. I think that I can confirm this, as I've just tried configuring Windows 10 to use it and it fails. Using "time.windows.com" to update my PC time is successful.
This is very odd. Is it coincidence the NTP server stops working at the same time as my router reboots, a few days ago?
31-05-2019 03:00 PM - edited 31-05-2019 03:06 PM
I've sent a PM to Leanne. I raised the fault with Customer Service (while raising a line quality fault).
To Leanne and anyone in EE - can you update this thread with progress please? Or post here if you don't hear anything?
By the way for xrayspex, here's the trace route from here: (this seems a bit unexpected to me)
C:\Users\ian> tracert ntp.readytoconnect.co.uk
Tracing route to ntp.readytoconnect.co.uk [184.108.40.206]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BrightBox.ee [192.168.1.1]
2 * * * Request timed out.
3 31 ms 31 ms 31 ms 220.127.116.11
4 31 ms 31 ms 31 ms 18.104.22.168
5 33 ms 36 ms 33 ms 22.214.171.124
6 45 ms 34 ms 34 ms te5-4.telehouse-east.core.enta.net [126.96.36.199]
7 32 ms 33 ms 33 ms bundle-ether100.interxion3.core.enta.net [188.8.131.52]
8 34 ms 33 ms 34 ms bundle-ether102.miltonkeynes.core.enta.net [184.108.40.206]
9 37 ms 37 ms 37 ms bundle-ether101.birmingham-te.core.enta.net [220.127.116.11]
10 37 ms 37 ms 36 ms 78-33-48-89.static.enta.net [18.104.22.168]
31-05-2019 03:24 PM
Unexpected in what way? It's the same route as mine & ends up at Entanet as I predicted.
The host computer is up & running; just the the NTP server on it isn't.
31-05-2019 04:10 PM
...unexpected only in that the Whois record has the IP address
22.214.171.124 (- 479,786 other sites hosted on this server)
But I don't understand name resolution etc fully. Is this the address of the top level domain (TLD) server for readytoconnect.co.uk, whereas 126.96.36.199 is the IP address for
Anyway, it's logged with tech support, and Louise is aware... I'm waiting for a call.
31-05-2019 06:51 PM
I thought I explained that earlier. Where the domain comes from & the servers that host its various services needn't be the same: