Nighthawk AC 1900 WiFi Cable Modem Router

---

BobbyG58 wrote:

Yes, I have tried the 30,30,30 Press reset for 30, power down while holding reset for 30, apply power and hold reset for another 30, all without releasing the reset.

Doing it this way, I get flashing white power.

 

---

That is where you should be in order to do the TFTP thing.

Puzzling.

But there have been so many reports here of people having to do strange things – standing on one foot and reciting strange incantatiions – that nothing surprises me.

I am wondering if in the flashing white power light state if I should also have a Port light?

Although on one try to TFTP attempt with no port light, I got transfer successful but I waited an hour and the unit never rebooted.

At that point, I tried to connect through my browser and got cannot connect message.

After that I turned the power off and rebooted and I got orange power and orange port but no communication through my browser and could not ping the router.

So, that is the 2 modes I can get 1) flashing power light and no port light or 2) Orange power light and orange port light.

So, in the end, it seems the unit is not taking the firmware even though I did get the one "transfer successful" message that was still a failure.

I cannot find any other "tricks" that do not involve taking the unit apart. Which I might try but then again, I may just scrap it and buy another unit.

I could not attach the txt file for some reason. So here is a copy of the command prompt window with the attempts that I tried today.

First try flashing white power light reset mode. Using 192.168.1.10/ 255.255.255.0/ 192.168.1.2

c:\Users\Bob\Desktop\NetGear Fix>tftp -i 192.168.1.2 put R6900v2-V1.2.0.36_1.0.1.img
Connect request failed

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.

Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.10

Pinging 192.168.1.10 with 32 bytes of data
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here I Changed adapter back to 192.168.1.1

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.10: Destination host unreachable.
Reply from 192.168.1.10: Destination host unreachable.
Request timed out.
Reply from 192.168.1.10: Destination host unreachable.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

c:\Users\Bob\Desktop\NetGear Fix>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.10: Destination host unreachable.
Request timed out.
Reply from 192.168.1.10: Destination host unreachable.
Request timed out.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

c:\Users\Bob\Desktop\NetGear Fix>tftp -i 192.168.1.1 put R6900v2-V1.2.0.36_1.0.1.img
Connect request failed

Here I tried using Obtain IP Address Automatically

C:\Users\Bob\Desktop\NetGear Fix>ipconfig

Windows IP Configuration

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::2de1:4ccc:a1a0:8fd9%23
Autoconfiguration IPv4 Address. . : 169.254.143.217
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\Bob\Desktop\NetGear Fix>tftp -i 169.254.143.217 put R6900v2-V1.2.0.36_1.0.1.img
Connect request failed

C:\Users\Bob\Desktop\NetGear Fix>ping 169.254.143.217

Pinging 169.254.143.217 with 32 bytes of data
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64
Reply from 169.254.143.217: bytes=32 time<1ms TTL=64

Ping statistics for 169.254.143.217:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

> First try flashing white power light reset mode. Using
> 192.168.1.10/ 255.255.255.0/ 192.168.1.2

   Those are the Ethernet interface IP address, subnet mask, and
gateway?  The gateway setting shouldn't matter, but, if you're setting
it to anything, then why ".2"?  What's at ".2"?  Anything?

> c:\Users\Bob\Desktop\NetGear Fix>tftp -i 192.168.1.2 put
> R6900v2-V1.2.0.36_1.0.1.img
> Connect request failed

   That does not amaze me.  I'd expect the router to be at ".1", and
nothing to be at ".2".  Hence, no TFTP server at ".2".

> Pinging 192.168.1.2 with 32 bytes of data
> Reply from 192.168.1.10: Destination host unreachable.

   Same.  What's at ".2"?  "Nothing" is usually unreachable.

> Pinging 192.168.1.10 with 32 bytes of data
> Reply from 192.168.1.10: bytes=32 time<1ms TTL=64

   Also not amazing.  The computer's Ethernet interface (at
"192.168.1.10") can talk to itself.

> Here I Changed adapter back to 192.168.1.1

   Why?  If the router is at ".1", as it should be, then this could only
cause a conflict (and failure).

> Here I tried using Obtain IP Address Automatically

   Also doomed.  If the router's DHCP server is dead, and the
"169.254.x.y" address testifies to that, then there's little hope of
anything signifcant to work if it relies on DHCP.

> C:\Users\Bob\Desktop\NetGear Fix>tftp -i 169.254.143.217
> put R6900v2-V1.2.0.36_1.0.1.img

   Again, you're trying to send the file to the computer (where there's
no TFTP server), not to the router (where you hope that there is a TFTP
server).  The router is what needs the file.

   As the instructions say, set the computer's interface to
"192.168.1.10", and try to reach the router at "192.168.1.1".  If you
set the gateway, then set it to the same "192.168.1.1" where the router
should be.  Fiddling with these addresses (for no good reason) is much
more likely to induce failure than success.

   Fiddle with the reset operations, the command timing, and/or anything
else which is not certain to make trouble.

   Is the computer connected to the "LAN 1" port on the router?

If you had read one of my previous posts, I mentioned another user, with a similar problem, acheived the flash by using

192.168.10

255.255.255.0

192.168.1.2

It was worth a try.

I then switched it back to

192.168.10

255.255.0

192.168.1

When that did not work, then I tried Obtain IP Automatically.

Since I have not received any advice on what diagnostic steps to try, I have no choice but to try anything.

I made it clear that I do not have much knowlege on how routers communicate.

This forum to date has not been helpful with anything in the way of instruction or diagnostic help. Instead my posts are ridiculed with snide remarks and ZERO helpful information.

I came here for information, knowlege a possible solution or conclusion, not sarcastic comments.

I posted everything that I see on the router and what attempts I have made to rectify the issue with my router.

I ignored the "resident troll" remark but now, maybe I understand the comment. So far, I have not received any meaningful help and anything I try using my limited knowlege only begets snide remarks and no help whatsoever.

I think the adage "If you can't say anything nice, don't say anything at all" should be practiced.

My  adage: "if you can't help provide knowlege, solutions or conclusional help, don't "help" at all".