NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
insanesquirle
Sep 21, 2017Initiate
DHCP Not working
My once fine-working cable modem has randomly stopped assigning IPV4 addresses to all of my devices. IPV6 is on auto-assign and works fine. I verified that IPV4 is set up for DHCP, but none of my d...
Bryansix
Jan 20, 2018Aspirant
The telnet thing is interesting. I'll have to check that out when I have time.
I rebooted the router at least 6 times. I tried both a hard power cycle by taking out the power cable and a soft reboot via the web interface. I had connectivity to the router via ethernet and wifi on my computer and neither were getting a DHCP address. ipconfig / release && ipconfig /renew did nothing. Only once I disabled DHCP, rebooted, enabled it, and rebooted again did it finally start assigning IP addresses again.
One thing to note is that the router seems to have lost its time as some point because some of the logs look like they are from 1970.
antinode
Jan 20, 2018Guru
> One thing to note is that the router seems to have lost its time as
> some point because some of the logs look like they are from 1970.
Hmmm. That sounds like a wholly other problem (can't contact
Netgear's NTP servers?).
If this thing's little brain is sufficiently scrambled, then it may
be time to try the usual panacea: a full reset and (manual)
reconfiguration of the router. Or the super-panacea: reload the
firmware (and then apply the ordinary panacea).
> The telnet thing is interesting. [...]
It might be educational to poke around, and try to see what's
happening before geting brutal. But even knowing that, say, the DHCP
server dies spontaneously may not actually tell you what to do about the
problem.