NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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 syn...
Hi IrvSp,
If you reboot both router and the modem, will it have the same problem?
Hi IrvSp,
If you reboot both router and the modem, will it have the same problem?
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.