Voltron-IU wrote:
Hello, Derek:
I have the WET200 and although it took me a few attempts, in the beginning, I was able to use WPA2 and it worked for about two-and-a-half years, until several weeks ago. I had it connected to a 2Wire 2701HG-B wireless gateway and the throughput was wonderful. When I was initially connecting it, it was not working, as I expected it to and it would not show any connection. Then, all of a sudden, it had made a connection, on its own, and has been working since. Then, several weeks ago, I noticed it flashing and acting strangely. Upon inspection, it had lost its connection with my wireless gateway and I have not been able to reconnect it to the 2Wire gateway since. I have re-flashed the WET200, with the same and latest firmware and performed several soft and hard resets, to no avail. Unlike before, I can see it making an attempt to connect to the 2Wire wireless gateway, as the wireless light (on the 2Wire) will briefly light, then, it goes out. This will continue, indefinitely, until I power off the WET200. I am desperate for Cisco/Linksys to create a new firmware, as we are far overdue for a great, stable firmware release for this unit, since it has been since August 8, 2008, since the last update. Also, Cisco/Linksys appears to have been updating firmware for many similar devices, moving these small-business devices to a strictly Cisco-branded firmware. I am hoping Cisco will soon do the same for the WET200, as this firmware is "flaky." It is a shame and such a disappointment that such a device, from such a respected and reputable company would be operating in such a condition.
One more note, while I appear to be one of a small handful that has been successful (lucky) to get WPA2 to work on the WET200, I was never able to get it to accept and pass DHCP requests/traffic, properly, onto the connected, wired clients. Once it would finally pass and allow DHCP to a connected client, things were fine. However, once that lease ended, it would take several minutes and/or several reboots of a connected client, before the WET200 would pass DHCP information onto the client, allowing for a proper network connection. It was so frustrating, I ended up using static IP addresses for my connected clients.
I hope this information helps you, in some way and further encourages Cisco/Linksys to update the WET200's firmware. Thank you.
--Dylan
Dylan,
you are much more patient than i am. having been a staunch defender and supporter of Linksys in the past, their consistent product quality issues and lack of firmware updates for any of the products i purchased and used (wrt600n, wrt54gx4, wet200, wvc200, etc.) i finally have given up hope. i've spent over well North of $5k with Linksys over the last 5 years, and cannot in good faith continue to support their apathy towards the customer base needs.
i have since pulled the wet200 out of production, and replaced it with a D-Link DAP-1522 to match up with the DIR-825 AP. I have switched over to doing what i wanted (N band / WPA2), performance has increased, stability has increased, and i can now see my windows media servers which were hidden when the WET was in production.
As a general statement to Linksys/Cisco, i think we were all hoping for better results (i.e. better products and improved support) after the acquisition. If possible, i think it's actuallu gotten worse.
Stepping down from soapbox now, and returning to obscurity.
