On 14 Feb 2006 15:24:05 -0800, "pstock" <(E-Mail Removed)> wrote:
>I did try the connection with WEP code turned off completely. No luck.
Well, if it didn't work with encryption disabled, then it's broken.
The problem is that I can't tell where it's broken. It can just as
easily be your WRT54G as your WUSB11. Methinks the only way to be
sure is by substitution. Try your WUSB11 with some other access
point, or wireless free hot spot. Verify that functions as expected.
Similarly, drag in a friend with a wireless laptop and have them
connect to your WRT54G.
>that was one hour on tech support Chat (seemed like a good idea at the
>time) but I soon realized that with the support person multitasking
>between three "callers" it was brutally inefficient.
Yep. I have a 3 minute limit for keyboard chat sessions. After that,
it's either switch to voice, or send me email.
>might be time for a telephone call to their tech support.
Might be worth a try. However, first I suggest you literally start
over. Reset the router to defaults, disable all enhancements, and
setup a very simple wireless network. Also, check your firmware and
driver versions. You can add encryption, filtering, and security
after it's working.
>Though as it is so common a problem, I would have expected Linksys to
>have posted the Top 10 fixes for poor folk like me to try.
The last time I discussed it with someone at Linksys in a position to
do something about it, I was told it was not a problem because nobody
has reported the WEP ASCII to Hex problem. Never mind that only a
small number of clients will work. Most people either switch to no
encryption, or use WPA instead.
>If (when) I figure it out, I will report.
>peter
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558
(E-Mail Removed)
#
http://802.11junk.com (E-Mail Removed)
#
http://www.LearnByDestroying.com AE6KS