MN-510 suddenly lost connection to network

After 6 months of working fine my MN-510 (Wireless USB
Adapter) recently stopped working. My wireless network is
available through both XP and the MBU for selection, but
after I select it the icon pops up in the
taskbar "wireless network available" and, if I mouse over
the MBU icon, the network name is gobbledegook (about
fourty random characters from the top of the unicode
table). I can select the network again but after I hit
the "apply" button its only seconds before it reverts to a
new string of gobbledegook. I've uninstalled the adapter,
reinstalled it, uninstalled MBU, reinstalled it, changed
the WEP settings on the router, disabled access control on
the router, checked and rechecked wireless
channel/mode/key/etc settings. No dice. I had the exact
same problems two weeks ago, and pulled my hair out for
several hours (while doing several system rollbacks, to no
avail) before they suddenly went away as quickly as they'd
come. This week, the problem seems to be more persistent
(7 days and counting without success). Any suggestions?

Patrick McKenzie

Sorry to say I don't have an answer to your problem, just a "Me too!"

The only difference is mine worked for about 1 year. Only 2 weeks longer
than the wireless on my MN-500

Because of the total breakdown, I have since replaced my whole network with,
what I think, is a more reliable setup. Unfortunately (or fortunately
depending on your outlook) that setup no longer includes any Microsoft
networking hardware.

In order to find some commonality, let me ask this: Do you leave your
computer on 24/7?

Regards
Brian W


"Patrick McKenzie" <(E-Mail Removed)> wrote in message
news:2f8201c3fcfa$c2303a70$(E-Mail Removed)...
> After 6 months of working fine my MN-510 (Wireless USB
> Adapter) recently stopped working. My wireless network is
> available through both XP and the MBU for selection, but
> after I select it the icon pops up in the
> taskbar "wireless network available" and, if I mouse over
> the MBU icon, the network name is gobbledegook (about
> fourty random characters from the top of the unicode
> table). I can select the network again but after I hit
> the "apply" button its only seconds before it reverts to a
> new string of gobbledegook. I've uninstalled the adapter,
> reinstalled it, uninstalled MBU, reinstalled it, changed
> the WEP settings on the router, disabled access control on
> the router, checked and rechecked wireless
> channel/mode/key/etc settings. No dice. I had the exact
> same problems two weeks ago, and pulled my hair out for
> several hours (while doing several system rollbacks, to no
> avail) before they suddenly went away as quickly as they'd
> come. This week, the problem seems to be more persistent
> (7 days and counting without success). Any suggestions?
>
> Patrick McKenzie

I have exactly the same problem with my MN 520 notebook
adapter. I use cable to connect. I suspect from talking
to equally befuddled Microsoft support on the phone that
a)this is a common problem and b) Microsoft needs to fix
it before taking any more of our money.
slobo
>-----Original Message-----
>After 6 months of working fine my MN-510 (Wireless USB
>Adapter) recently stopped working. My wireless network
is
>available through both XP and the MBU for selection, but
>after I select it the icon pops up in the
>taskbar "wireless network available" and, if I mouse
over
>the MBU icon, the network name is gobbledegook (about
>fourty random characters from the top of the unicode
>table). I can select the network again but after I hit
>the "apply" button its only seconds before it reverts to
a
>new string of gobbledegook. I've uninstalled the
adapter,
>reinstalled it, uninstalled MBU, reinstalled it, changed
>the WEP settings on the router, disabled access control
on
>the router, checked and rechecked wireless
>channel/mode/key/etc settings. No dice. I had the
exact
>same problems two weeks ago, and pulled my hair out for
>several hours (while doing several system rollbacks, to
no
>avail) before they suddenly went away as quickly as
they'd
>come. This week, the problem seems to be more
persistent
>(7 days and counting without success). Any suggestions?
>
>Patrick McKenzie
>.
>