R7000 time synch repeating often all of a sudden?

JamesGL, I didn't think of that. Good suggestion.

I just looked at my Modem's log. Saw this:

--------------------

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.

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...

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:19

At 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.

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.

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:

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?

JamesGL, I've tried resetting the router and it just doesn't work? Settings never reset to default, both on V1.0.9.10 and V1.0.9.12.

I've done some searching and it IS the router providing the DHCP Server.  I can't find ANY settings in the Router that defines this other than the ADVANCED --> LAN SETUP which can be either ON or OFF (mine is ON).

However there is a clear mismatch between what the R7000 and W10 think the LEASE LENGHT is!

Windows 10 (IPCONGIF output for the Ethernet card):

Lease Obtained. . . . . . . . . . : Tuesday, November 28, 2017 7:33:06 AM
Lease Expires . . . . . . . . . . : Wednesday, November 29, 2017 7:33:05 AM

More normal, a 24 hour lease, and normally after 12 hours a new lease would be gotten.

Now what the R7000 thinks the lease period is:

So the question now becomes 'why' the difference?

You should also note that my post of 2017-11-27 08:39 AM above that these times were different as I did a few reboots and attempted resets after that posting.