NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Netgear Nighthawk D8500 - Bricked / Boot cycle failure
Hi,
I purchased a Netgear D8500 approx 1 week back, originally had issues with the 2.4GHz wifi signal dropping out and had that resolved with a Firmware update, factory reset, then setting wifi...
Returned the NetGear D8500 back to the store and they replaced it with the D-Link AC5300 COBRA... which worked instantly, setup in 2 minutes and zero issues so far.
Disappointed with the D8500, compared to previous NetGear products. Suggest others to avoid this one, perhaps the NetGear Orbi (wifi mesh) would of been another high-end gaming / 4k streaming option, but they didn't have that in the store at the time for me.
> [...] The router has no lights on, except for the power light being
> Amber. [...]
You may be a candidate for the TFTP recovery scheme. See, for
example:
https://community.netgear.com/t5/x/x/m-p/1533866#M87578
> [...] I can't even go to RouterLogin.NET or //192.168.0.1 IP Address
> of the Router. [...]
Does "go to" mean using a web browser, or a Windows File Explorer, or
what? As usual, showing actual actions with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
> [...] When pinging the router's IP Address, it also is not responding,
> [...]
If your computer (running some version of Windows?) is configured to
get its IP configuration automatically from the (DHCP server on the)
router, and the router (or its DHCP server) is not working, then you
shouldn't expect much else to work, including "ping". (But showing the
actual "ping" command with its actual results would have been more
helpful than that description. Copy+paste is your friend.)
If we're talking about a Windows system, then open a Command Prompt
(CMD.EXE) window on the Windows system, and see what an "ipconfig"
command says about its "IPv4 address" and "Default Gateway" address.
The latter should be the router's LAN IP address.
If "ipconfig" results show a self-assigned ("169.254.x.y") address,
then that could be explained by a disfunctional router, and that would
explain many other possible failures. That Netgear KB article on the
TFTP recovery scheme explains how to configure your computer so that it
can work with a mostly-dead router.
Thanks for your reply, but I'm at my ends with this router...
Tried the TFTP firmware upload: https://kb.netgear.com/22688/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP
The router appears under the network and then disappears, reappears, and disappears. The TFTP fails 3 times, then gives up.
It's like the router is stuck in a rebooting cycle. Amber power light, then Wifi antenna ends glow blue. All goes off. All lights go white, then back to the power light being Amber again. Rinse and repeat.