>OK!! I turned off WEP and it worked, and then I entered the key again
>and everthing seems to be working now. (I can't believe it was
>something that simple.) I'm using WEP for now but plan on switching to
>WPA-PSK per your advice.
Cool. WEP problems are all too common. First there's the ASCII to
Hex problem. Then, if the user tries to type in the Hex key, it's
rather difficult to inscribe 26 characters of gibberish, without
seeing what one is typing. If one manages to do it correctly,
Microsoft stupidly insists that you do it twice (for no good reason).
WEP is rough. If possible, I strongly suggest you switch to WPA-PSK
instead of WEP.
Don't kick yourself for the simple fix. It's NOT commonly known. It's
not on any of the support knowledgebase sites. If you ask support
from any of the organizations you called about ASCII versus Hex for
WEP, they will not find anything because it's only a problem with
mixed vendor systems and support doesn't answer questions about mixed
vendor systems. Microsloth doesn't make it easy because of the lack
of connection progress diagnostics. Searching Google by keyword is
almost impossible because the failure mode description tends to be
vague and too broad. It's in the FAQ, but good luck finding it with a
search key that doesn't also include the answer:
>Thank you SO much! Someone should give you a raise!
Thanks. I get a karma recharge from being helpful, which balances the
decadent lifestyle and debauchery to which I have become accustomed.
Jeff Liebermann email@example.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558