NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
piotr_dobrogost
Mar 06, 2021Aspirant
Nighthawk R8000 DHCP on WAN port not working
I replaced Netgear WNR3500L with Netgear R8000. I had WNR3500L's WAN port connected to TP-LINK TD-W8960N DSL modem (setup in router mode) and obtaining IP address and DNS servers from it using DHCP. ...
- Mar 06, 2021
> [...] I have "Internet IP Address" set to "Get Dynamically from ISP"
> in "Internet Setup". [...]What about all the other Internet Setup settings? Did you try
letting the set-up wizard do what it does?> [...] Why?
Who knows? With my weak psychic powers, I can't see any of the LED
indicators on any of your devices, or any of the R8000 Internet Setup
settings (save one), or the configuration of your old WNR3500L. Could
be a bad Ethernet cable, for all I know.If you connect a computer to the TD-W8960N, does _it_ get good IP
parameters? (Namely?)> [...] TD-W8960N DSL modem (setup in router mode) [...] "I connected
> R8000 the same way [...]
Why, exactly, are you arranging a cascade of routers, instead of
using one router (modem and router, or modem+router and wireless access
point)? Cascading multiple routers can cause multiple problems (double
NAT, for example), even when you get such an arrangement to work.
ColoradoSlim
Mar 21, 2021Aspirant
cross posting from the R7000 series, but when the WAN port doesn't pick an IP address via DHCP from the internet router it is attached to I just downloaded the firmware and did a web firmware upload. That fixed it. First I tried to factory reset it but that did NOT fix the problem.
- piotr_dobrogostMar 21, 2021Aspirant
ColoradoSlim wrote:cross posting from the R7000 series, but when the WAN port doesn't pick an IP address via DHCP from the internet router it is attached to I just downloaded the firmware and did a web firmware upload. That fixed it. First I tried to factory reset it but that did NOT fix the problem.
Thanks for sharing this info here.
However as I described in my previous post even computer connected to the "internet router" (in place of R8000) was not getting IP address which demonstrated that the problem was on the sending side ("internet router") and not on the receiveing side (R8000 or temporarily connected computer).