NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
IrvSp
Nov 18, 2017Master
R7000 time synch repeating often all of a sudden?
This started a day or two ago.
===========
[Time synchronized with NTP server] Saturday, Nov 18,2017 06:22:06
.
[Time synchronized with NTP server] Saturday, Nov 18,2017 04:59:15
.
[Time synchronized with NTP server] Saturday, Nov 18,2017 03:28:57
.
[Time synchronized with NTP server] Saturday, Nov 18,2017 02:07:08
.
[Time synchronized with NTP server] Saturday, Nov 18,2017 00:35:39
.
[Time synchronized with NTP server] Friday, Nov 17,2017 23:15:14
.
[Time synchronized with NTP server] Friday, Nov 17,2017 21:42:08
.
[Time synchronized with NTP server] Friday, Nov 17,2017 20:23:31
.
[Time synchronized with NTP server] Friday, Nov 17,2017 18:48:24
.
[Time synchronized with NTP server] Friday, Nov 17,2017 17:21:36
.
[Time synchronized with NTP server] Friday, Nov 17,2017 15:55:48
.
[Time synchronized with NTP server] Friday, Nov 17,2017 14:28:53
.
[Time synchronized with NTP server] Friday, Nov 17,2017 13:03:12
.
[Time synchronized with NTP server] Friday, Nov 17,2017 11:36:08
.
[Time synchronized with NTP server] Friday, Nov 17,2017 10:10:37
.
[Time synchronized with NTP server] Friday, Nov 17,2017 08:45:27
.
[Internet disconnected] Tuesday, Oct 03,2017 12:32:01
.
[Initialized, firmware version: V1.0.9.12] Thursday, Jan 01,2015 00:00:08
===========
Usually a simple re-boot (which was done as you can see from the log) would 'cure' this. Not happening now? Problem only started a day or so ago. It seems to be doing it every 1 hour and 25 minutes or so. Before it was only 2 times per day. What changed?
Hi IrvSp,
If you reboot both router and the modem, will it have the same problem?
11 Replies
- JamesGLNETGEAR Employee Retired
Hi IrvSp,
If you reboot both router and the modem, will it have the same problem?
- IrvSpMaster
JamesGL, I didn't think of that. Good suggestion.
I just looked at my Modem's log. Saw this:
--------------------
Thu Nov 23 07:25:24 2017 Thu Nov 23 07:25:24 2017 Notice (6) Web user logged in from 67... Thu Nov 23 06:51:09 2017 Thu Nov 23 06:51:09 2017 Notice (6) DHCP Renew - lease parameters Time Protocol Servers modified;... Thu Nov 23 06:51:09 2017 Thu Nov 23 06:51:09 2017 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M... Thu Nov 23 05:51:09 2017 Thu Nov 23 05:51:09 2017 Notice (6) DHCP Renew - lease parameters Time Protocol Servers modified;... Thu Nov 23 05:51:09 2017 Thu Nov 23 05:51:09 2017 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M... Thu Nov 23 02:51:09 2017 Thu Nov 23 02:51:09 2017 Notice (6) DHCP Renew - lease parameters Time Protocol Servers modified;... Thu Nov 23 02:51:09 2017 Thu Nov 23 02:51:09 2017 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M... Wed Nov 22 21:51:09 2017 Wed Nov 22 21:51:09 2017 Notice (6) DHCP Renew - lease parameters Time Protocol Servers modified;... Wed Nov 22 21:51:09 2017 Wed Nov 22 21:51:09 2017 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M... Wed Nov 22 20:51:09 2017 Wed Nov 22 20:51:09 2017 Notice (6) DHCP Renew - lease parameters Time Protocol Servers modified;... Wed Nov 22 20:51:09 2017 Wed Nov 22 20:51:09 2017 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M... Wed Nov 22 19:51:09 2017 Wed Nov 22 19:51:09 2017 Notice (6) DHCP Renew - lease parameters Time Protocol Servers modified;... Wed Nov 22 19:51:09 2017 Wed Nov 22 19:51:09 2017 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-M...
Something IS going on with the ISP's modem or signal.
My router log shows this (modified not to show IP Address):
-------------
[Time synchronized with NTP server] Thursday, Nov 23,2017 06:49:17
[Internet connected] IP address: 67..., Thursday, Nov 23,2017 06:49:17
[Time synchronized with NTP server] Thursday, Nov 23,2017 05:22:10
[Internet connected] IP address: 67..., Thursday, Nov 23,2017 05:22:10
[Time synchronized with NTP server] Thursday, Nov 23,2017 03:56:44
[Internet connected] IP address: 67..., Thursday, Nov 23,2017 03:56:43
[Time synchronized with NTP server] Thursday, Nov 23,2017 02:29:23
[Internet connected] IP address: 67..., Thursday, Nov 23,2017 02:29:22
[Time synchronized with NTP server] Thursday, Nov 23,2017 01:04:13
[Internet connected] IP address: 67..., Thursday, Nov 23,2017 01:04:12
[Time synchronized with NTP server] Wednesday, Nov 22,2017 23:36:34
[Internet connected] IP address: 67..., Wednesday, Nov 22,2017 23:36:33
[Time synchronized with NTP server] Wednesday, Nov 22,2017 22:11:45
[Internet connected] IP address: 67..., Wednesday, Nov 22,2017 22:11:44
[Time synchronized with NTP server] Wednesday, Nov 22,2017 20:43:40------------
Note the time differences as well, a few minutes off. Can't see the Ubee's DVW3201B's time but it is probably off some. Router time is correct. ISP owns it so I think I'll call them before I reboot it.
Interesting in that we were gone for almost 3 weeks and the modem was left on but all the PC's and devices, as well as the router were powered off. When we returned we noticed we had a NEW IP Address starting with 67.xx.xx.xx. Have a completely different one before, like 184.xx.xx.xx I recall?
Thanks for the suggestion. Clearly this is not a router issue. I'll mark it solved.
- IrvSpMaster
JamesGL, looks like it isn't the ISP's modem.
I called the ISP and the first thing they did was REBOOT it (and I did the router). Didn't fix it. Next call I was told to RESET the modem to the shipped state. Didn't fix it, and actually unbeknownst to me, unbridged the modem. Next call the ISP bridged and rebooted the modem, didn't fix it.
So yesterday the ISP replaced the Ubee with an Arris modem. Not fixed either, still happening! Arris Log...
11/25/2017 18:26 4000960006 New time has been retrieved from ToD server. 11/25/2017 19:26 4000960006 New time has been retrieved from ToD server. 11/25/2017 20:59 16 MTA TFTP: Successful 11/25/2017 20:59 26 MTA PROV: Successful! 11/25/2017 20:59 3 Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS 11/25/2017 23:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 2:42 4000960006 New time has been retrieved from ToD server. 11/26/2017 3:43 4000960006 New time has been retrieved from ToD server. Not as often, but it does happen almost every hour when it does as you can see above. Router log is comparable (I can't see more of the Arris log):
[Time synchronized with NTP server] Sunday, Nov 26,2017 04:09:20
[Time synchronized with NTP server] Sunday, Nov 26,2017 02:44:47
[Time synchronized with NTP server] Sunday, Nov 26,2017 01:16:25
[Time synchronized with NTP server] Saturday, Nov 25,2017 23:52:25
[Time synchronized with NTP server] Saturday, Nov 25,2017 22:23:25
[Time synchronized with NTP server] Saturday, Nov 25,2017 21:00:08
[Time synchronized with NTP server] Saturday, Nov 25,2017 19:30:19At this point I do SUSPECT the router! I do get e-mailed the daily logs and keep them. On 11/15 it started to appear in the logs (1 PM).
[Time synchronized with NTP server] Wednesday, Nov 15,2017 06:15:02 [Internet connected] IP address: 67.x.x.x, Wednesday, Nov 15,2017 06:15:02 [DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:xx, Wednesday, Nov 15,2017 05:23:31 [Time synchronized with NTP server] Wednesday, Nov 15,2017 04:30:02 [Internet connected] IP address: 67.x.x.x, Wednesday, Nov 15,2017 04:30:01 [Time synchronized with NTP server] Wednesday, Nov 15,2017 02:45:01 [Internet connected] IP address: 67.x.x.x, Wednesday, Nov 15,2017 02:45:01 [DHCP IP: (192.168.1.2)] to MAC address 98:01:A7:05:5D:xx, Wednesday, Nov 15,2017 02:13:33 [DHCP IP: (192.168.1.4)] to MAC address 84:89:AD:71:97:xx, Wednesday, Nov 15,2017 02:12:20 [Time synchronized with NTP server] Wednesday, Nov 15,2017 01:00:01 [Internet connected] IP address: 67.x.x.x, Wednesday, Nov 15,2017 01:00:00 [DHCP IP: (192.168.1.3)] to MAC address 10:AE:60:57:25:xx, Tuesday, Nov 14,2017 21:12:57 [DHCP IP: (192.168.1.5)] to MAC address AC:63:BE:8E:E3:xx, Tuesday, Nov 14,2017 20:00:41 [DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:xx, Tuesday, Nov 14,2017 18:10:59 [DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:xx, Tuesday, Nov 14,2017 15:05:15 [DHCP IP: (192.168.1.35)] to MAC address 68:5D:43:23:9E:xx, Tuesday, Nov 14,2017 14:03:16 [DHCP IP: (192.168.1.4)] to MAC address 84:89:AD:71:97:xx, Tuesday, Nov 14,2017 14:02:31 [DHCP IP: (192.168.1.2)] to MAC address 98:01:A7:05:5D:xx, Tuesday, Nov 14,2017 14:01:12 [DHCP IP: (192.168.1.3)] to MAC address 10:AE:60:57:25:xx, Tuesday, Nov 14,2017 09:41:45 [DHCP IP: (192.168.1.5)] to MAC address AC:63:BE:8E:E3:xx, Tuesday, Nov 14,2017 08:00:41 [email sent to: ixxx@x.com] Tuesday, Nov 14,2017 07:01:03
That is the entire log I got for that day, after that, every day I've been getting those Time synch's every 2 hours or less. Before that it was once or twice a day, at least 15 hours apart but never the same amount, and never more than 23 hours?
I might go back in F/W but I'm not even sure that will fix it if something within the router has failed? I find my Wireless now is varying in speed of connection. Download can change on me, but the lowest if 40+Mbps on 100Mbps service which is fast enough anyway. At time it is 114Mbps which is 'normal' on the wired PC. However that test using OOKLA does seem to be possibly Server caused. Depend which Server it uses the results appear to be the same as the other tests at that server, so that could be server related but I didn't recall that happening before either?
When the ISP Tech was here he tested my cable line and it was fine...
Right now I don't know 'who' is initiating the time request? Assuming both the modem and router did get the same time (I can't see the time on the modem) there appears to be a slight delay when the Router logs the time change? Still, it is possible the router initiates the request, the modem goes to get the time and logs it, sends the time to the router which then logs it? If correct, the router is doing the request, not the modem.
- IrvSpMaster
JamesGL, I've tried these after the ISP replaced the modem and the problem remained:
- Going back a release of the F/W
- Ensured the settings were correct (they were)
- Checking after a few hours... still had the problem
- Did the 30-30-30 Reset.
- The router DID not really reset? That is the settings were retained?
- Went back to the latest release and followed the above steps again
Aren't the settings supposed to be wiped out with the 30-30-30 reset? I KNOW I've done it before and they have been? One easy way for me to tell is that I set the lights to be OFF, only the Power on. That doesn't change after the reset nor do any settings? This is on the V1.0.9.12_1.2.23 firmware.
Also I discovered something 'odd' on the Connection Status on the Advanced Tab.
Connection Status IP Address 67.xx.xx.xx Subnet Mask 255.255.248.0 Default Gateway 67.xx.xx.xx DHCP Server 10.120.0.1 DNS Server 75.114.81.1
209.18.47.62
75.114.81.2Lease Obtained 0 days,1 Hours,52 Minutes Lease Expires 0 days,1 Hours,44 Minutes What goes with that LEASE data? Who is doing this? The router only asking for a limited time or my ISP on providing limited time? I'd think that would explain the TIME SYNC's as the lines I've deleted shows the IP Address the router got from the ISP... consistent with the Lease renewal? Also, I've tried the 30-30-30 a few times and that Lease time changes on each reset, low of 1 hour and 20 minutes to a high as shown above.
Is this a FLASH problem? Router problem? ISP problem?
The new Modem is getting time at a completely difference schedule as well it seems:
11/25/2017 23:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 2:42 4000960006 New time has been retrieved from ToD server. 11/26/2017 3:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 6:42 4000960006 New time has been retrieved from ToD server. 11/26/2017 7:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 9:42 4000960006 New time has been retrieved from ToD server. 11/26/2017 10:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 12:42 4000960006 New time has been retrieved from ToD server. 11/26/2017 13:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 15:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 16:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 17:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 18:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 19:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 21:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 22:43 4000960006 New time has been retrieved from ToD server. 11/26/2017 23:43 4000960006 New time has been retrieved from ToD server. 11/27/2017 0:43 4000960006 New time has been retrieved from ToD server. 11/27/2017 1:43 4000960006 New time has been retrieved from ToD server. 11/27/2017 3:43 4000960006 New time has been retrieved from ToD server. 11/27/2017 6:43 4000960006 New time has been retrieved from ToD server. Heck, nothing is working even as we're asleep. NOTE they all end with :43 too?
Have any idea what is going on? Has my router failed in some way or should I be 'looking' at my ISP?
- apil1Apprentice
The data you show looks like the WAN DHCP, the public IP address your router gets from your ISP. The other DHCP would be your LAN, the private IP addresses your router gives to all your wired/wireless devices. DHCP should not need to renew the IP addresses for one day/day and a half/two days depending on your ISPs configuration.
Is the time zone set correctly on the router? This can cause issues with NTP, which may also cause the DHCP lease to time out early.
NTP should also typically only be about a once a day sync. NTP can also be triggered by the router losing the Internet connection. Because it's hard to know how much the clock has drifted while the device is "disconnected", it would immediately trigger a NTP sync. Yes, it would make sense to know how long you may have been disconnected to know if time needs to be synced, but its just easier to check time every time Internet is connected just in case the clock is wrong/broken.
- IrvSpMaster
Thanks, knew all that info.
I came here due to push-back from ISP. Took some doing and calling. I can access the Event Log on the Modem, and was able to 'ask' them to look at it. Conclusion was that I had an 'old' modem. Charter recently took over my ISP (Brighthouse) and they didn't use the Ubee DVW3201B modem/phone combo, so they replaced it with an Arris. Even that didn't solve the problem. Matter of fact, the Arris within 2 days started rebooting at least once a day. Another call and they 'discovered' that they still had my line running with the old Ubee configuration file. Changed that, still happened. Another visit and they discovered although everything looked good inside the house my line tap was bad. Replaced that, problems persisted. Another visit. Very thorough this time. Tech looked at all connections, discovered 3 that had some corrosion and replaced them. Also the Ground block had some discoloration so replaced that. I had a snapshot of the voltages and SNR before he started and all were better after he left.
It took a few days for the modem to stop rebooting after the last visit. From the modem logs it appears that was caused by the line tap problem. The probable cause of why the configuration files were not changed on the back-end when the modem was replaced. It might have taken a few times for the modem to get sync'ed with the back-end even.
Unfortunately the approximate time for a lease still is around 2 hours. ISP tells me that is on their end and they don't know why?
Since the other fixes have been done my browsing experience and other programs that use the internet is much smoother. Even with the DHCP and Time requests happening quite often.