Incorrect WEP key

I've had an all-MS Broadband Network in my house for the last 9 months or so
and it has always worked just fine. I've got an MN-700 base station/router, an
MN-720 PC card wireless adapter in my notebook, and an MN-710 wireless USB
adapter for my desktop computer.

Recently, my desktop computer suffered a bout of spyware/virus/etc which caused
me no end of trouble. I had upgraded from WinXP SP1 to SP2 with no problem, but
now all of a sudden there were some Windows files missing (like the firewall
controls) and the computer would no longer connect to the network. I
uninstalled SP2 so now I'm back to SP1. The computer can see the network but it
won't connect; I get the "incorrect WEP key" error message, despite the fact
that I never changed the key.

In my troubleshooting I rebooted the router as well as my computer, and
uninstalled and reinstalled MSBN. I even went to the MSBN management tool and
set the Wireless Encryption to "none" to see if it would pick it up, but it
said that it still wasn't getting the right WEP key despite the fact that there
was no encryption (and the refreshed list showed "none" for security type
there). I've verified that the WEP key on the desktop is the same as the key on
my laptop (which has never stopped cooperating on the network).

So bottom line, I've got a computer that won't connect to the network (which it
sees) because the previously good WEP key is suddenly incorrect (even though it
matches the key on a good computer).

Help!

--
Michael R. Grabois # http://chili.cjb.net # http://wizardimps.blogspot.com
"People say losing builds character. That's the stupidest thing I ever
heard. All losing does is suck. " -- Charles Barkley, 9/29/96

I have this problem as well -- My desktop with wireless
PCI G card (MN-730) suddenly will not connect to my MN-
700 base station due to "incorrect wep key" despite the
fact that my two laptops running a cisco card and a MN-
520? (B) pcmcia card connect mo problem. XP SP2 and
latest firmware/update on ALL machines.

This is frustrating to NO END - please help

Thanks



>-----Original Message-----
>I've had an all-MS Broadband Network in my house for the
last 9 months or so
>and it has always worked just fine. I've got an MN-700
base station/router, an
>MN-720 PC card wireless adapter in my notebook, and an
MN-710 wireless USB
>adapter for my desktop computer.
>
>Recently, my desktop computer suffered a bout of
spyware/virus/etc which caused
>me no end of trouble. I had upgraded from WinXP SP1 to
SP2 with no problem, but
>now all of a sudden there were some Windows files
missing (like the firewall
>controls) and the computer would no longer connect to
the network. I
>uninstalled SP2 so now I'm back to SP1. The computer can
see the network but it
>won't connect; I get the "incorrect WEP key" error
message, despite the fact
>that I never changed the key.
>
>In my troubleshooting I rebooted the router as well as
my computer, and
>uninstalled and reinstalled MSBN. I even went to the
MSBN management tool and
>set the Wireless Encryption to "none" to see if it would
pick it up, but it
>said that it still wasn't getting the right WEP key
despite the fact that there
>was no encryption (and the refreshed list showed "none"
for security type
>there). I've verified that the WEP key on the desktop is
the same as the key on
>my laptop (which has never stopped cooperating on the
network).
>
>So bottom line, I've got a computer that won't connect
to the network (which it
>sees) because the previously good WEP key is suddenly
incorrect (even though it
>matches the key on a good computer).
>
>Help!
>
>--
>Michael R. Grabois # http://chili.cjb.net #
http://wizardimps.blogspot.com
>"People say losing builds character. That's the
stupidest thing I ever
> heard. All losing does is suck. " -- Charles Barkley,
9/29/96
>.
>

I fixed just such a problem by changing from chan. 6 to 11

Smooth at 54Mbps
>-----Original Message-----
>I have this problem as well -- My desktop with wireless
>PCI G card (MN-730) suddenly will not connect to my MN-
>700 base station due to "incorrect wep key" despite the
>fact that my two laptops running a cisco card and a MN-
>520? (B) pcmcia card connect mo problem. XP SP2 and
>latest firmware/update on ALL machines.
>
>This is frustrating to NO END - please help
>
>Thanks
>
>
>
>>-----Original Message-----
>>I've had an all-MS Broadband Network in my house for the
>last 9 months or so
>>and it has always worked just fine. I've got an MN-700
>base station/router, an
>>MN-720 PC card wireless adapter in my notebook, and an
>MN-710 wireless USB
>>adapter for my desktop computer.
>>
>>Recently, my desktop computer suffered a bout of
>spyware/virus/etc which caused
>>me no end of trouble. I had upgraded from WinXP SP1 to
>SP2 with no problem, but
>>now all of a sudden there were some Windows files
>missing (like the firewall
>>controls) and the computer would no longer connect to
>the network. I
>>uninstalled SP2 so now I'm back to SP1. The computer can
>see the network but it
>>won't connect; I get the "incorrect WEP key" error
>message, despite the fact
>>that I never changed the key.
>>
>>In my troubleshooting I rebooted the router as well as
>my computer, and
>>uninstalled and reinstalled MSBN. I even went to the
>MSBN management tool and
>>set the Wireless Encryption to "none" to see if it would
>pick it up, but it
>>said that it still wasn't getting the right WEP key
>despite the fact that there
>>was no encryption (and the refreshed list showed "none"
>for security type
>>there). I've verified that the WEP key on the desktop is
>the same as the key on
>>my laptop (which has never stopped cooperating on the
>network).
>>
>>So bottom line, I've got a computer that won't connect
>to the network (which it
>>sees) because the previously good WEP key is suddenly
>incorrect (even though it
>>matches the key on a good computer).
>>
>>Help!
>>
>>--
>>Michael R. Grabois # http://chili.cjb.net #
>http://wizardimps.blogspot.com
>>"People say losing builds character. That's the
>stupidest thing I ever
>> heard. All losing does is suck. " -- Charles Barkley,
>9/29/96
>>.
>>
>.
>