cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
666
Views
10
Helpful
2
Replies

WAP351 - Wrong Firmware

Stefan M
Level 1
Level 1

I erratically uploaded a wrong Firmware into my new WAP351 (image 'WAP321_1.0.6.5.tar' instead of 'WAP351_WAP131_1.0.2.8.tar').

Now the device shows blue light, which means no error, but doesn't response at all. The manual says, that there is a backup image inside and in case of error one can restore the backup image and reset the device by connecting with fallback IP 192.168.1.245. But the thing does not respond on 192.168.1.245 or any other IP in the LAN (made an IP scan). It also does not request a DHCP IP.

The manual says, that pressing reset longer than 10 s one can factory restore the device, but the thing does not respond regardless of how long I press reset.

May it be possible to restore this device back into life? Maybe opening and jumpering anything like PC BIOS?

Thank you for any hint which not says this is electronic scrap now.

Best regards
Stefan

2 Replies 2

Ingrid Aragon
Level 1
Level 1

Hello Stefan, I am one of the engineers from the Small Business team.

I would say that you can try re-flashing the unit.
Perform a Hard Reset (30/30/30 reset):
- With the unit powered on, press and hold the reset button of unit for 30 seconds
- Without releasing the reset button, unplug the unit and hold reset for another 30 seconds
- Plug the unit back in STILL holding the reset button a final 30 seconds

Once this is completed, use a TFTP server (I can recommend you TFTPD32/TFTPD64) to upload the correct firmware file.
- DO NOT CONNECT THE WAP TO YOUR NETWORK YET.
- Only connect a computer, setup a static IP address on the subnet 192.168.1.X
- Confirm if you can ping to the default IP address of the WAP 192.168.1.245.
- If you can ping send the file through the TFTP.

Hello Ingrid

Thank you for your hints! The 30-30-30 hard reset sounds very promising. However in the meantime I made an RMA replacement through my dealer. So I have no more need to risk such a reset on a working device. Should I ever have the same issue again I will remember this post and give it a try.

Many thanks again!

Stefan