Hi All For the past couple of weeks I've been receiving emails from my NAS about its inability to "register the IP address 0.0.0.0" to its DDNS service. Since last week I've also had another NAS in the house for a client and it's doing the same. Checking the logs of these NASs (I don't always get the notification emails as they can't be sent unless a 'real' IP address has been assigned!) I see the incidents happening on: 09/05 03:02 15/05 14:01 17/05 07:21 20/05 14:36 21/05 02.22 The last one I've just now investigated by looking into the router's logs and the PPP connection was lost at 02:17:15 and was back up again at 02:17:44 so no major outage and to be honest I'd have never known if the NAS was not reporting. Should I be concerned about this? Why has it just started happening though? Cheers Andy
Hi there, I've posted a graph of your connection: <img src="http://ccgi.psmith12.plus.com/visradius/generated/image1369141722736.png"/> You're not dropping PPP as often as you've reported, your line is very stable. Have you changed anything on your network?
Hi Chris Thanks for looking into this. I see from the graph that a couple of the dates/times agree exactly, others don't. Most intriguing! No, nothing knowingly changed on the network. The second NAS was introduced last Thursday and has shown this 'error' twice (17/7 and 20/5) and my own NAS has been up for 12 days and shows four of these incidents. When it last restarted (9 May) it registered the IP address 87.115.208.196 but three hours later reported that it couldn't register the IP address 0.0.0.0! It's the 0.0.0.0 that takes my interest - this can only come from the router, yes? If my DDNS service is down at the server end, which it is occasionally, then I'll get a notification but with a valid IP address given (the service has a 'heartbeat' function) I don't have DDNS enabled on the router (TG852n) as the NAS takes care of that. The router doesn't have any logs far enough back to look at any other incidents beyond the one last night, but last night's was caused by a PPP drop. So what else do you think could cause this? And as I say I never had this problem before 9 May. Cheers Andy
@Anotherone. Good thinking that man. I wouldn't haven't made that connection. @jelv. Not a long enough log to see beyond last night. Also I'm on FTTC so don't have sync stats. Anyhow it's not a show stopper! More of a mystery. And as I say, without the NAS reporting I'd never have known. Cheers Andy
