Sep 15, 2009
I was using WAP54G in our company in AP client mode to support "wired" connection to far workstation being part of Windows Domain (it needed network connection before logging to windows). It was working fine for a year, secured with WPA. this AP client was wirelessly connected to another WAP54G unit running regular AP mode.
View 9 Replies
Today was changing configuration on "AP client" , wanted to cvheck if WPA2 is supported while in AP client mode. well it wasn't, so ireverted the config back to what it was. after power cycle device stays in "bricked mode".
it doesn't boot up, LAN port inactive (like a cable unplugged), no WiFi, only 2 LEDs are lit permamently red POWER and yellow LINK. green ACT is dead. resetting is no luck, tried resetting it multiple times holding it with device powered on or off, tried 30/30/30 method, no luck.
finally took it apart (was out of warranty anyways) and shorted pin 16 (A18) on flash chip (Spansion) while powering up and it worked to the point when LAN interface becomes operational with 192.168.1.245 IP and i get ping response.
I thought that's it, would just re-load firware (original latest 3.04.03) and done. i was wrong. device takes fw via tftp, but immediately after tha it stops responding, green ACT never comes back online, reset still do not work. after power cycle LAN port is dead (as well as device) again. what has happened to it?