NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Dave_Nelson
Jun 14, 2016Tutor
Manually updating firmware - asked often but threads closed
I have a WNDR4500 I received from a friend. The green power light blinks continiously which tells me that the firmware is corrupt. I know this question has been asked many times before but I am stuck in my attempts to update the firmware. As this problem is generic to all newer Netgear routers, I'm reasking the question asking for some clarifications in the instructions. I am on a Mac and so far:
I am following the instructions in NetGear's help system here:
http://kb.netgear.com/app/answers/detail/a_id/19841
1. I downloaded and unpacked the latest firmware WNDR4500-V1.0.1.40_1.0.68.chk
2. I downloaded TFTP Send
3. I connected my Mac's ethernet port to the LAN 1 port (also tried LAN 4) on the router
I don't understand Step 4 of the help file which says "
- Connect the computer to the router and assign a static IP of the router's default range (192.168.1.x or 192.168.0.x) on the LAN connection." How is that done on a Mac?
- In terminal I tried pinging 192.168.1.1 after connecting the Mac ethernet port to a router LAN port but I get no response. The router should be hard coded to have that address. When I plug in directly to the cable modem I can see its IP address but nothing shows up when cabled to the router even though I get a solid green light for the LAN port I'm connected to. I also tried the WAN port but didn't get anywhere.
4. Even without a successful ping, I tried the update anyway and get an Error 103 using the TFTP Send software Netgear recommended for the Mac. Of course I can't find where type 103 error is defined. I suspect it is that the target was not found. I used passwords of 'password' 'admin' and left blank. None worked.
5. I tried using the tftp command in terminal but that doesn't seem to recognize the -i option. Here is the command I used:
tftp -i 192.168.1.1 put wndr4500-v1.0.1.40_1.0.68.chk
I also tried without the -i, without the put, and with the path to the chk file included in the command and numerous combinations of variations. I suspect that I just cant see the router at 192.168.1.1
Bottom line, why can't I see the router? Do I have a hardware problem? Anybody have Mac specific instructions? Thanks!
The IP address and subnet mask you picked are not good choices. Try the following:
IP Address: 192.168.1.2
Subnet Mask: 255.255.255.0
Router: 192.168.1.1
Then retry step 4.
13 Replies
- Retired_Member
I dont' own a Mac but, I would think you could enter a static IP in the network card setup. The router cannot issue an IP if DHCP is not working so if you cannot set a IP in the MAC you're hosed.
That router is a lemon hands down give it back and buy a working one.
I would think that the IP address of the router is hard coded into the router. My Mac can see it as connected but for the life of me I can't figure out how to determine the IP address of what it sees. As far as giving it back, I knew it wasn't working when he gave it to me but I wanted to take the challenge to see if I could fix it. If I can't fix it, it goes into the trash. While working on the problem I realized that the router was going to be a problem based on the number of support topics I found on this site on that model. I'm open to suggestions regarding a reliable model.
- doraemonProdigy
Assign static through System Preference > Network > TCP/P > Configure IPv4 should set to Manually and type in your IP address
Make sure that the Router address is the default IP of the router (192.168.1.1).
- VE6CGXMaster
TFTP method can be used only when router CFE is intact and you can capture firmware bootloader time. First requirement for this is ability
to ping the router. You mentioned ping won't go thru. So TFTP won't work. People think TFTP will do wonders for bricked routers but not always.
So the bottom line is that the router is bricked?
The IP address and subnet mask you picked are not good choices. Try the following:
IP Address: 192.168.1.2
Subnet Mask: 255.255.255.0
Router: 192.168.1.1
Then retry step 4.
- doraemonProdigyOops! TheEther is right! It was the IP address!