Anyone can send a ping to a an IP address. That is unlikely the answer. Have the modem not registered properly certainly could be a solution. They might also have just been saying that as a placebo. Who knows; maybe they did something, maybe they just sent a restart. I haven't seen the issue on my router since Jul 11, but it happened many times on Jul 11, and just a few times before that. It possible merlin firmware updates have resolved the issue.SOLVED (for me): I had the same issue with comcast and an ASUS RT-N66U. Went through all the trouble shooting with comcast. Called ASUS and, after some testing, they told me the router wasn't compatible with my new Netgear Nighthawk CM1150V cable modem. Called comcast back, and two things were different. First, she said my modem wasn't registered properly (even though the online registration seemed to work and I had internet access if I plugged pc directly into modem). So she did a manual registration. Second, in addition to sending a Restart signal to my modem, she also sent a ping to my modem. Suddenly the error message went away and everything worked. No one else at comcast had sent the ping.