MN-730 PCI - Broken After SP2

I am starting a new thread because I originally posted
this problem of mine deep inside someone else's thread.

I use a MN-700 AP and a MN-730 PCI adapter. After
installing SP2 for XP, I got warning messages that I
needed to update my software (i.e. drivers). I downloaded
and installed the MSBNDownload.exe program from
Microsoft, and the software update was successful. The
wireless configuration in Windows found my wireless
network properly, and I thought I was on my way.

But then strange behavior started popping up. My
connection would get dropped after a minute or two of
being connected. Sometimes it would connect to the
wireless network, but the wireless connection icon in the
system tray would say that the network was unavailable-
yet I was able to browse the web perfectly for a short
while. Sometimes it wouldn't connect at all. It would
never reconnect after a reboot.

I tried turning on different layers of encryption, such
as WEP 128bit and WPA-PSK. Both encryption types did
nothing to solve my problem. I tried to run the network
without any security, and the same behavior was exhibited.

I went to my Device Manager, and I noticed that the
driver for my PCI card was listed as "Microsoft Wireless
Notebook Adapter". Since this is a desktop, I thought
maybe the MSBNDownload update installed the wrong driver
for my card. So I used the Update Driver utility to
select the old driver to use. This did not solve my
problem, as the old driver doesn't work with SP2, and I
ran into problems connecting to the network.

I am concerned that the driver update Microsoft released
is buggy. Can Microsoft provide me with a single download
of the most current driver for this device? My suspicion
is that the driver that was installed by the MSBNDownload
update was the wrong one.

I own two of these cards, although only one of them is in
use. Until I installed SP2 and the new device driver,
this card and my wireless network worked flawlessly, and
I told my friends to buy Microsoft's wireless hardware
because it was the easiest to setup and configure. But
now I'm stuck with a sucky network and problems that can
only be driver related.

Martin:

The MN 730 PCI card and the MN 720 notebook bus card adaptor use the same
driver. I ran into a weak signal problem using this particular driver when
I updated firmware and drivers from the "msbndownload.exe". Since I
installed the driver pre-SP2, the only problem I ran into was the weak
signal. (I'm using a MN 700 and MN 720) Rolling back the driver to the
previous version restored signal strength.

I have the full (266mb) installation of SP-2 ready to be deployed to several
machines. I'm not sure now I want to install SP-2 based on your post and
several others I've read in this group. You stated that the old driver
won't work at all with SP-2? That doesn't sound right but since I haven't
had a chance to test it, I can't verify that.

Regards.


"Martin" <(E-Mail Removed)> wrote in message
news:519501c480a3$f45dd070$(E-Mail Removed)...
> I am starting a new thread because I originally posted
> this problem of mine deep inside someone else's thread.
>
> I use a MN-700 AP and a MN-730 PCI adapter. After
> installing SP2 for XP, I got warning messages that I
> needed to update my software (i.e. drivers). I downloaded
> and installed the MSBNDownload.exe program from
> Microsoft, and the software update was successful. The
> wireless configuration in Windows found my wireless
> network properly, and I thought I was on my way.
>
> But then strange behavior started popping up. My
> connection would get dropped after a minute or two of
> being connected. Sometimes it would connect to the
> wireless network, but the wireless connection icon in the
> system tray would say that the network was unavailable-
> yet I was able to browse the web perfectly for a short
> while. Sometimes it wouldn't connect at all. It would
> never reconnect after a reboot.
>
> I tried turning on different layers of encryption, such
> as WEP 128bit and WPA-PSK. Both encryption types did
> nothing to solve my problem. I tried to run the network
> without any security, and the same behavior was exhibited.
>
> I went to my Device Manager, and I noticed that the
> driver for my PCI card was listed as "Microsoft Wireless
> Notebook Adapter". Since this is a desktop, I thought
> maybe the MSBNDownload update installed the wrong driver
> for my card. So I used the Update Driver utility to
> select the old driver to use. This did not solve my
> problem, as the old driver doesn't work with SP2, and I
> ran into problems connecting to the network.
>
> I am concerned that the driver update Microsoft released
> is buggy. Can Microsoft provide me with a single download
> of the most current driver for this device? My suspicion
> is that the driver that was installed by the MSBNDownload
> update was the wrong one.
>
> I own two of these cards, although only one of them is in
> use. Until I installed SP2 and the new device driver,
> this card and my wireless network worked flawlessly, and
> I told my friends to buy Microsoft's wireless hardware
> because it was the easiest to setup and configure. But
> now I'm stuck with a sucky network and problems that can
> only be driver related.

The old driver didn't work for me as soon as I installed
SP2; before I installed the MSBNDownload.exe, I was
unable to connect to my wireless network.

tonight, I'm planning to test out a Linksys USB adapter
that I bought to see if I can get that to work. If not,
then perhaps my problem is more at the OS level than at
the NIC level. I find that hard to believe, since the
rest of the machines seems to run fine, but I'm ready to
try anything at this point.
>-----Original Message-----
>Martin:
>
>The MN 730 PCI card and the MN 720 notebook bus card
adaptor use the same
>driver. I ran into a weak signal problem using this
particular driver when
>I updated firmware and drivers from
the "msbndownload.exe". Since I
>installed the driver pre-SP2, the only problem I ran
into was the weak
>signal. (I'm using a MN 700 and MN 720) Rolling back
the driver to the
>previous version restored signal strength.
>
>I have the full (266mb) installation of SP-2 ready to be
deployed to several
>machines. I'm not sure now I want to install SP-2 based
on your post and
>several others I've read in this group. You stated
that the old driver
>won't work at all with SP-2? That doesn't sound right
but since I haven't
>had a chance to test it, I can't verify that.
>
>Regards.
>
>
>"Martin" <(E-Mail Removed)> wrote in message
>news:519501c480a3$f45dd070$(E-Mail Removed)...
>> I am starting a new thread because I originally posted
>> this problem of mine deep inside someone else's thread.
>>
>> I use a MN-700 AP and a MN-730 PCI adapter. After
>> installing SP2 for XP, I got warning messages that I
>> needed to update my software (i.e. drivers). I
downloaded
>> and installed the MSBNDownload.exe program from
>> Microsoft, and the software update was successful. The
>> wireless configuration in Windows found my wireless
>> network properly, and I thought I was on my way.
>>
>> But then strange behavior started popping up. My
>> connection would get dropped after a minute or two of
>> being connected. Sometimes it would connect to the
>> wireless network, but the wireless connection icon in
the
>> system tray would say that the network was unavailable-
>> yet I was able to browse the web perfectly for a short
>> while. Sometimes it wouldn't connect at all. It would
>> never reconnect after a reboot.
>>
>> I tried turning on different layers of encryption, such
>> as WEP 128bit and WPA-PSK. Both encryption types did
>> nothing to solve my problem. I tried to run the network
>> without any security, and the same behavior was
exhibited.
>>
>> I went to my Device Manager, and I noticed that the
>> driver for my PCI card was listed as "Microsoft
Wireless
>> Notebook Adapter". Since this is a desktop, I thought
>> maybe the MSBNDownload update installed the wrong
driver
>> for my card. So I used the Update Driver utility to
>> select the old driver to use. This did not solve my
>> problem, as the old driver doesn't work with SP2, and I
>> ran into problems connecting to the network.
>>
>> I am concerned that the driver update Microsoft
released
>> is buggy. Can Microsoft provide me with a single
download
>> of the most current driver for this device? My
suspicion
>> is that the driver that was installed by the
MSBNDownload
>> update was the wrong one.
>>
>> I own two of these cards, although only one of them is
in
>> use. Until I installed SP2 and the new device driver,
>> this card and my wireless network worked flawlessly,
and
>> I told my friends to buy Microsoft's wireless hardware
>> because it was the easiest to setup and configure. But
>> now I'm stuck with a sucky network and problems that
can
>> only be driver related.
>
>
>.
>

I am pretty sure the new drivers are broken at least when
it comes to connecting to third party wireless AP's. I
can't connect to my D-Link DI-713P AP with the MN-730.
When I swap in an off-brand $30 802.11b card it connects
no problem. (This is NOT one of the AP's that supports
the D-Link non standard higher speed b protocol. It's way
older than that.)
The setup software sees the wireless network, senses that
that WEP is turned off and then complains that the WEP
key I've provided (which, of course the software does not
let me do) does not work. Same behavior with WEP on
except that it sees the WEP and lets me enter a key.

I have not tried to connect to an MS g AP yet. (I keep
forgetting to bring it home.)

>-----Original Message-----
>The old driver didn't work for me as soon as I installed
>SP2; before I installed the MSBNDownload.exe, I was
>unable to connect to my wireless network.
>
>tonight, I'm planning to test out a Linksys USB adapter
>that I bought to see if I can get that to work. If not,
>then perhaps my problem is more at the OS level than at
>the NIC level. I find that hard to believe, since the
>rest of the machines seems to run fine, but I'm ready to
>try anything at this point.
>>-----Original Message-----
>>Martin:
>>
>>The MN 730 PCI card and the MN 720 notebook bus card
>adaptor use the same
>>driver. I ran into a weak signal problem using this
>particular driver when
>>I updated firmware and drivers from
>the "msbndownload.exe". Since I
>>installed the driver pre-SP2, the only problem I ran
>into was the weak
>>signal. (I'm using a MN 700 and MN 720) Rolling back
>the driver to the
>>previous version restored signal strength.
>>
>>I have the full (266mb) installation of SP-2 ready to
be
>deployed to several
>>machines. I'm not sure now I want to install SP-2
based
>on your post and
>>several others I've read in this group. You stated
>that the old driver
>>won't work at all with SP-2? That doesn't sound right
>but since I haven't
>>had a chance to test it, I can't verify that.
>>
>>Regards.
>>
>>
>>"Martin" <(E-Mail Removed)> wrote in message
>>news:519501c480a3$f45dd070$(E-Mail Removed)...
>>> I am starting a new thread because I originally posted
>>> this problem of mine deep inside someone else's
thread.
>>>
>>> I use a MN-700 AP and a MN-730 PCI adapter. After
>>> installing SP2 for XP, I got warning messages that I
>>> needed to update my software (i.e. drivers). I
>downloaded
>>> and installed the MSBNDownload.exe program from
>>> Microsoft, and the software update was successful. The
>>> wireless configuration in Windows found my wireless
>>> network properly, and I thought I was on my way.
>>>
>>> But then strange behavior started popping up. My
>>> connection would get dropped after a minute or two of
>>> being connected. Sometimes it would connect to the
>>> wireless network, but the wireless connection icon in
>the
>>> system tray would say that the network was
unavailable-
>>> yet I was able to browse the web perfectly for a short
>>> while. Sometimes it wouldn't connect at all. It would
>>> never reconnect after a reboot.
>>>
>>> I tried turning on different layers of encryption,
such
>>> as WEP 128bit and WPA-PSK. Both encryption types did
>>> nothing to solve my problem. I tried to run the
network
>>> without any security, and the same behavior was
>exhibited.
>>>
>>> I went to my Device Manager, and I noticed that the
>>> driver for my PCI card was listed as "Microsoft
>Wireless
>>> Notebook Adapter". Since this is a desktop, I thought
>>> maybe the MSBNDownload update installed the wrong
>driver
>>> for my card. So I used the Update Driver utility to
>>> select the old driver to use. This did not solve my
>>> problem, as the old driver doesn't work with SP2, and
I
>>> ran into problems connecting to the network.
>>>
>>> I am concerned that the driver update Microsoft
>released
>>> is buggy. Can Microsoft provide me with a single
>download
>>> of the most current driver for this device? My
>suspicion
>>> is that the driver that was installed by the
>MSBNDownload
>>> update was the wrong one.
>>>
>>> I own two of these cards, although only one of them
is
>in
>>> use. Until I installed SP2 and the new device driver,
>>> this card and my wireless network worked flawlessly,
>and
>>> I told my friends to buy Microsoft's wireless hardware
>>> because it was the easiest to setup and configure. But
>>> now I'm stuck with a sucky network and problems that
>can
>>> only be driver related.
>>
>>
>>.
>>
>.
>

I have wireless routers and access points from Netgear, Linksys,
DLink, Buffalo, Motorola, 3Com and SMC and have no problems connecting
to them with the Microsoft NICs. I use WPA when available and WEP when
it is not. Using XP SP2 on all machines here.

On Thu, 12 Aug 2004 20:04:55 -0700, "Mike L"
<(E-Mail Removed)> wrote:

>I am pretty sure the new drivers are broken at least when
>it comes to connecting to third party wireless AP's. I
>can't connect to my D-Link DI-713P AP with the MN-730.
>When I swap in an off-brand $30 802.11b card it connects
>no problem. (This is NOT one of the AP's that supports
>the D-Link non standard higher speed b protocol. It's way
>older than that.)
>The setup software sees the wireless network, senses that
>that WEP is turned off and then complains that the WEP
>key I've provided (which, of course the software does not
>let me do) does not work. Same behavior with WEP on
>except that it sees the WEP and lets me enter a key.
>
>I have not tried to connect to an MS g AP yet. (I keep
>forgetting to bring it home.)
>
>>-----Original Message-----
>>The old driver didn't work for me as soon as I installed
>>SP2; before I installed the MSBNDownload.exe, I was
>>unable to connect to my wireless network.
>>
>>tonight, I'm planning to test out a Linksys USB adapter
>>that I bought to see if I can get that to work. If not,
>>then perhaps my problem is more at the OS level than at
>>the NIC level. I find that hard to believe, since the
>>rest of the machines seems to run fine, but I'm ready to
>>try anything at this point.
>>>-----Original Message-----
>>>Martin:
>>>
>>>The MN 730 PCI card and the MN 720 notebook bus card
>>adaptor use the same
>>>driver. I ran into a weak signal problem using this
>>particular driver when
>>>I updated firmware and drivers from
>>the "msbndownload.exe". Since I
>>>installed the driver pre-SP2, the only problem I ran
>>into was the weak
>>>signal. (I'm using a MN 700 and MN 720) Rolling back
>>the driver to the
>>>previous version restored signal strength.
>>>
>>>I have the full (266mb) installation of SP-2 ready to
>be
>>deployed to several
>>>machines. I'm not sure now I want to install SP-2
>based
>>on your post and
>>>several others I've read in this group. You stated
>>that the old driver
>>>won't work at all with SP-2? That doesn't sound right
>>but since I haven't
>>>had a chance to test it, I can't verify that.
>>>
>>>Regards.
>>>
>>>
>>>"Martin" <(E-Mail Removed)> wrote in message
>>>news:519501c480a3$f45dd070$(E-Mail Removed).. .
>>>> I am starting a new thread because I originally posted
>>>> this problem of mine deep inside someone else's
>thread.
>>>>
>>>> I use a MN-700 AP and a MN-730 PCI adapter. After
>>>> installing SP2 for XP, I got warning messages that I
>>>> needed to update my software (i.e. drivers). I
>>downloaded
>>>> and installed the MSBNDownload.exe program from
>>>> Microsoft, and the software update was successful. The
>>>> wireless configuration in Windows found my wireless
>>>> network properly, and I thought I was on my way.
>>>>
>>>> But then strange behavior started popping up. My
>>>> connection would get dropped after a minute or two of
>>>> being connected. Sometimes it would connect to the
>>>> wireless network, but the wireless connection icon in
>>the
>>>> system tray would say that the network was
>unavailable-
>>>> yet I was able to browse the web perfectly for a short
>>>> while. Sometimes it wouldn't connect at all. It would
>>>> never reconnect after a reboot.
>>>>
>>>> I tried turning on different layers of encryption,
>such
>>>> as WEP 128bit and WPA-PSK. Both encryption types did
>>>> nothing to solve my problem. I tried to run the
>network
>>>> without any security, and the same behavior was
>>exhibited.
>>>>
>>>> I went to my Device Manager, and I noticed that the
>>>> driver for my PCI card was listed as "Microsoft
>>Wireless
>>>> Notebook Adapter". Since this is a desktop, I thought
>>>> maybe the MSBNDownload update installed the wrong
>>driver
>>>> for my card. So I used the Update Driver utility to
>>>> select the old driver to use. This did not solve my
>>>> problem, as the old driver doesn't work with SP2, and
>I
>>>> ran into problems connecting to the network.
>>>>
>>>> I am concerned that the driver update Microsoft
>>released
>>>> is buggy. Can Microsoft provide me with a single
>>download
>>>> of the most current driver for this device? My
>>suspicion
>>>> is that the driver that was installed by the
>>MSBNDownload
>>>> update was the wrong one.
>>>>
>>>> I own two of these cards, although only one of them
>is
>>in
>>>> use. Until I installed SP2 and the new device driver,
>>>> this card and my wireless network worked flawlessly,
>>and
>>>> I told my friends to buy Microsoft's wireless hardware
>>>> because it was the easiest to setup and configure. But
>>>> now I'm stuck with a sucky network and problems that
>>can
>>>> only be driver related.
>>>
>>>
>>>.
>>>
>>.
>>

--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)

Barb,

I have tried connecting my MN-730 to both Microsoft's MN-
700 and an older SMC 802.11b router, and both times it
would either not connect or the connection would drop
after a few minutes.

Last night I bought a Linksys USB Wireless G adapter. I
installed it and it works perfectly with my MN-700 router-
I get a good, strong signal that doesn't break off. I am
now convinced that something is wrong with the driver for
my MN-730 adapter.

I suppose that the last thing I can try is completely
uninstalling and reinstalling the adapter and its
software. I'll try that tonight.

At the end of the day, Microsoft is dropping this entire
line of products, so I suppose it's for the best that we
all start transitioning away to other hardware vendors.
It's too bad, since I really love the performance of my
Microsoft adapters until this driver problem hit me.
>-----Original Message-----
>I have wireless routers and access points from Netgear,
Linksys,
>DLink, Buffalo, Motorola, 3Com and SMC and have no
problems connecting
>to them with the Microsoft NICs. I use WPA when
available and WEP when
>it is not. Using XP SP2 on all machines here.
>
>On Thu, 12 Aug 2004 20:04:55 -0700, "Mike L"
><(E-Mail Removed)> wrote:
>
>>I am pretty sure the new drivers are broken at least
when
>>it comes to connecting to third party wireless AP's. I
>>can't connect to my D-Link DI-713P AP with the MN-730.
>>When I swap in an off-brand $30 802.11b card it
connects
>>no problem. (This is NOT one of the AP's that supports
>>the D-Link non standard higher speed b protocol. It's
way
>>older than that.)
>>The setup software sees the wireless network, senses
that
>>that WEP is turned off and then complains that the WEP
>>key I've provided (which, of course the software does
not
>>let me do) does not work. Same behavior with WEP on
>>except that it sees the WEP and lets me enter a key.
>>
>>I have not tried to connect to an MS g AP yet. (I keep
>>forgetting to bring it home.)
>>
>>>-----Original Message-----
>>>The old driver didn't work for me as soon as I
installed
>>>SP2; before I installed the MSBNDownload.exe, I was
>>>unable to connect to my wireless network.
>>>
>>>tonight, I'm planning to test out a Linksys USB
adapter
>>>that I bought to see if I can get that to work. If
not,
>>>then perhaps my problem is more at the OS level than
at
>>>the NIC level. I find that hard to believe, since the
>>>rest of the machines seems to run fine, but I'm ready
to
>>>try anything at this point.
>>>>-----Original Message-----
>>>>Martin:
>>>>
>>>>The MN 730 PCI card and the MN 720 notebook bus card
>>>adaptor use the same
>>>>driver. I ran into a weak signal problem using this
>>>particular driver when
>>>>I updated firmware and drivers from
>>>the "msbndownload.exe". Since I
>>>>installed the driver pre-SP2, the only problem I ran
>>>into was the weak
>>>>signal. (I'm using a MN 700 and MN 720) Rolling
back
>>>the driver to the
>>>>previous version restored signal strength.
>>>>
>>>>I have the full (266mb) installation of SP-2 ready to
>>be
>>>deployed to several
>>>>machines. I'm not sure now I want to install SP-2
>>based
>>>on your post and
>>>>several others I've read in this group. You stated
>>>that the old driver
>>>>won't work at all with SP-2? That doesn't sound
right
>>>but since I haven't
>>>>had a chance to test it, I can't verify that.
>>>>
>>>>Regards.
>>>>
>>>>
>>>>"Martin" <(E-Mail Removed)> wrote in message
>>>>news:519501c480a3$f45dd070$(E-Mail Removed). ..
>>>>> I am starting a new thread because I originally
posted
>>>>> this problem of mine deep inside someone else's
>>thread.
>>>>>
>>>>> I use a MN-700 AP and a MN-730 PCI adapter. After
>>>>> installing SP2 for XP, I got warning messages that I
>>>>> needed to update my software (i.e. drivers). I
>>>downloaded
>>>>> and installed the MSBNDownload.exe program from
>>>>> Microsoft, and the software update was successful.
The
>>>>> wireless configuration in Windows found my wireless
>>>>> network properly, and I thought I was on my way.
>>>>>
>>>>> But then strange behavior started popping up. My
>>>>> connection would get dropped after a minute or two
of
>>>>> being connected. Sometimes it would connect to the
>>>>> wireless network, but the wireless connection icon
in
>>>the
>>>>> system tray would say that the network was
>>unavailable-
>>>>> yet I was able to browse the web perfectly for a
short
>>>>> while. Sometimes it wouldn't connect at all. It
would
>>>>> never reconnect after a reboot.
>>>>>
>>>>> I tried turning on different layers of encryption,
>>such
>>>>> as WEP 128bit and WPA-PSK. Both encryption types did
>>>>> nothing to solve my problem. I tried to run the
>>network
>>>>> without any security, and the same behavior was
>>>exhibited.
>>>>>
>>>>> I went to my Device Manager, and I noticed that the
>>>>> driver for my PCI card was listed as "Microsoft
>>>Wireless
>>>>> Notebook Adapter". Since this is a desktop, I
thought
>>>>> maybe the MSBNDownload update installed the wrong
>>>driver
>>>>> for my card. So I used the Update Driver utility to
>>>>> select the old driver to use. This did not solve my
>>>>> problem, as the old driver doesn't work with SP2,
and
>>I
>>>>> ran into problems connecting to the network.
>>>>>
>>>>> I am concerned that the driver update Microsoft
>>>released
>>>>> is buggy. Can Microsoft provide me with a single
>>>download
>>>>> of the most current driver for this device? My
>>>suspicion
>>>>> is that the driver that was installed by the
>>>MSBNDownload
>>>>> update was the wrong one.
>>>>>
>>>>> I own two of these cards, although only one of them
>>is
>>>in
>>>>> use. Until I installed SP2 and the new device
driver,
>>>>> this card and my wireless network worked
flawlessly,
>>>and
>>>>> I told my friends to buy Microsoft's wireless
hardware
>>>>> because it was the easiest to setup and configure.
But
>>>>> now I'm stuck with a sucky network and problems
that
>>>can
>>>>> only be driver related.
>>>>
>>>>
>>>>.
>>>>
>>>.
>>>
>
>--
>Barb Bowman
>Expert Zone Columnist
>http://www.microsoft.com/windowsxp/expertzone
>MS-MVP (Windows)
>.
>

Uninstall the BNU utility, reboot, and use only Windows XP's built in
application to configure and connect to these routers. Do you have a third
party firewall installed? Try uninstalling it.

Martin wrote:
> Barb,
>
> I have tried connecting my MN-730 to both Microsoft's MN-
> 700 and an older SMC 802.11b router, and both times it
> would either not connect or the connection would drop
> after a few minutes.
>
> Last night I bought a Linksys USB Wireless G adapter. I
> installed it and it works perfectly with my MN-700 router-
> I get a good, strong signal that doesn't break off. I am
> now convinced that something is wrong with the driver for
> my MN-730 adapter.
>
> I suppose that the last thing I can try is completely
> uninstalling and reinstalling the adapter and its
> software. I'll try that tonight.
>
> At the end of the day, Microsoft is dropping this entire
> line of products, so I suppose it's for the best that we
> all start transitioning away to other hardware vendors.
> It's too bad, since I really love the performance of my
> Microsoft adapters until this driver problem hit me.
>> -----Original Message-----
>> I have wireless routers and access points from Netgear,
> Linksys,
>> DLink, Buffalo, Motorola, 3Com and SMC and have no problems
>> connecting to them with the Microsoft NICs. I use WPA when available
>> and WEP when it is not. Using XP SP2 on all machines here.
>>
>> On Thu, 12 Aug 2004 20:04:55 -0700, "Mike L"
>> <(E-Mail Removed)> wrote:
>>
>>> I am pretty sure the new drivers are broken at least
> when
>>> it comes to connecting to third party wireless AP's. I
>>> can't connect to my D-Link DI-713P AP with the MN-730.
>>> When I swap in an off-brand $30 802.11b card it
> connects
>>> no problem. (This is NOT one of the AP's that supports
>>> the D-Link non standard higher speed b protocol. It's
> way
>>> older than that.)
>>> The setup software sees the wireless network, senses
> that
>>> that WEP is turned off and then complains that the WEP
>>> key I've provided (which, of course the software does
> not
>>> let me do) does not work. Same behavior with WEP on
>>> except that it sees the WEP and lets me enter a key.
>>>
>>> I have not tried to connect to an MS g AP yet. (I keep
>>> forgetting to bring it home.)
>>>
>>>> -----Original Message-----
>>>> The old driver didn't work for me as soon as I
> installed
>>>> SP2; before I installed the MSBNDownload.exe, I was
>>>> unable to connect to my wireless network.
>>>>
>>>> tonight, I'm planning to test out a Linksys USB
> adapter
>>>> that I bought to see if I can get that to work. If
> not,
>>>> then perhaps my problem is more at the OS level than
> at
>>>> the NIC level. I find that hard to believe, since the
>>>> rest of the machines seems to run fine, but I'm ready
> to
>>>> try anything at this point.
>>>>> -----Original Message-----
>>>>> Martin:
>>>>>
>>>>> The MN 730 PCI card and the MN 720 notebook bus card adaptor use
>>>>> the same driver. I ran into a weak signal problem using this
>>>>> particular driver when I updated firmware and drivers from the
>>>>> "msbndownload.exe". Since I installed the driver pre-SP2, the
>>>>> only problem I ran into was the weak signal. (I'm using a MN 700
>>>>> and MN 720) Rolling back the driver to the
>>>> the driver to the
>>>>> previous version restored signal strength.
>>>>>
>>>>> I have the full (266mb) installation of SP-2 ready to be deployed
>>>>> to several
>>>> deployed to several
>>>>> machines. I'm not sure now I want to install SP-2 based on your
>>>>> post and
>>>> on your post and
>>>>> several others I've read in this group. You stated that the old
>>>>> driver won't work at all with SP-2? That doesn't sound right but
>>>>> since I haven't
>>>> but since I haven't
>>>>> had a chance to test it, I can't verify that.
>>>>>
>>>>> Regards.
>>>>>
>>>>>
>>>>> "Martin" <(E-Mail Removed)> wrote in message
>>>>> news:519501c480a3$f45dd070$(E-Mail Removed)...
>>>>>> I am starting a new thread because I originally
> posted
>>>>>> this problem of mine deep inside someone else's
>>> thread.
>>>>>>
>>>>>> I use a MN-700 AP and a MN-730 PCI adapter. After
>>>>>> installing SP2 for XP, I got warning messages that I
>>>>>> needed to update my software (i.e. drivers). I
>>>> downloaded
>>>>>> and installed the MSBNDownload.exe program from
>>>>>> Microsoft, and the software update was successful.
> The
>>>>>> wireless configuration in Windows found my wireless
>>>>>> network properly, and I thought I was on my way.
>>>>>>
>>>>>> But then strange behavior started popping up. My
>>>>>> connection would get dropped after a minute or two
> of
>>>>>> being connected. Sometimes it would connect to the
>>>>>> wireless network, but the wireless connection icon in the
>>>> the
>>>>>> system tray would say that the network was
>>> unavailable-
>>>>>> yet I was able to browse the web perfectly for a
> short
>>>>>> while. Sometimes it wouldn't connect at all. It
> would
>>>>>> never reconnect after a reboot.
>>>>>>
>>>>>> I tried turning on different layers of encryption,
>>> such
>>>>>> as WEP 128bit and WPA-PSK. Both encryption types did
>>>>>> nothing to solve my problem. I tried to run the
>>> network
>>>>>> without any security, and the same behavior was
>>>> exhibited.
>>>>>>
>>>>>> I went to my Device Manager, and I noticed that the
>>>>>> driver for my PCI card was listed as "Microsoft
>>>> Wireless
>>>>>> Notebook Adapter". Since this is a desktop, I
> thought
>>>>>> maybe the MSBNDownload update installed the wrong
>>>> driver
>>>>>> for my card. So I used the Update Driver utility to
>>>>>> select the old driver to use. This did not solve my
>>>>>> problem, as the old driver doesn't work with SP2, and I
>>> I
>>>>>> ran into problems connecting to the network.
>>>>>>
>>>>>> I am concerned that the driver update Microsoft
>>>> released
>>>>>> is buggy. Can Microsoft provide me with a single
>>>> download
>>>>>> of the most current driver for this device? My
>>>> suspicion
>>>>>> is that the driver that was installed by the
>>>> MSBNDownload
>>>>>> update was the wrong one.
>>>>>>
>>>>>> I own two of these cards, although only one of them is in
>>>> in
>>>>>> use. Until I installed SP2 and the new device
> driver,
>>>>>> this card and my wireless network worked flawlessly, and
>>>> and
>>>>>> I told my friends to buy Microsoft's wireless
> hardware
>>>>>> because it was the easiest to setup and configure.
> But
>>>>>> now I'm stuck with a sucky network and problems that can
>>>> can
>>>>>> only be driver related.
>>>>>
>>>>>
>>>>> .
>>>>>
>>>> .
>>>>
>>
>> --
>> Barb Bowman
>> Expert Zone Columnist
>> http://www.microsoft.com/windowsxp/expertzone
>> MS-MVP (Windows)
>> .


--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)

For me, this was a completely fresh install of Media
Center Edition which has SP2 in it already. No other
wireless NIC had ever been in the system. Nothing to
uninstall and the only firewall was the native one.
>-----Original Message-----
>Uninstall the BNU utility, reboot, and use only Windows
XP's built in
>application to configure and connect to these routers.
Do you have a third
>party firewall installed? Try uninstalling it.
>
>Martin wrote:
>> Barb,
>>
>> I have tried connecting my MN-730 to both Microsoft's
MN-
>> 700 and an older SMC 802.11b router, and both times it
>> would either not connect or the connection would drop
>> after a few minutes.
>>
>> Last night I bought a Linksys USB Wireless G adapter. I
>> installed it and it works perfectly with my MN-700
router-
>> I get a good, strong signal that doesn't break off. I
am
>> now convinced that something is wrong with the driver
for
>> my MN-730 adapter.
>>
>> I suppose that the last thing I can try is completely
>> uninstalling and reinstalling the adapter and its
>> software. I'll try that tonight.
>>
>> At the end of the day, Microsoft is dropping this
entire
>> line of products, so I suppose it's for the best that
we
>> all start transitioning away to other hardware vendors.
>> It's too bad, since I really love the performance of my
>> Microsoft adapters until this driver problem hit me.
>>> -----Original Message-----
>>> I have wireless routers and access points from
Netgear,
>> Linksys,
>>> DLink, Buffalo, Motorola, 3Com and SMC and have no
problems
>>> connecting to them with the Microsoft NICs. I use WPA
when available
>>> and WEP when it is not. Using XP SP2 on all machines
here.
>>>
>>> On Thu, 12 Aug 2004 20:04:55 -0700, "Mike L"
>>> <(E-Mail Removed)> wrote:
>>>
>>>> I am pretty sure the new drivers are broken at least
>> when
>>>> it comes to connecting to third party wireless AP's.
I
>>>> can't connect to my D-Link DI-713P AP with the MN-
730.
>>>> When I swap in an off-brand $30 802.11b card it
>> connects
>>>> no problem. (This is NOT one of the AP's that
supports
>>>> the D-Link non standard higher speed b protocol. It's
>> way
>>>> older than that.)
>>>> The setup software sees the wireless network, senses
>> that
>>>> that WEP is turned off and then complains that the
WEP
>>>> key I've provided (which, of course the software does
>> not
>>>> let me do) does not work. Same behavior with WEP on
>>>> except that it sees the WEP and lets me enter a key.
>>>>
>>>> I have not tried to connect to an MS g AP yet. (I
keep
>>>> forgetting to bring it home.)
>>>>
>>>>> -----Original Message-----
>>>>> The old driver didn't work for me as soon as I
>> installed
>>>>> SP2; before I installed the MSBNDownload.exe, I was
>>>>> unable to connect to my wireless network.
>>>>>
>>>>> tonight, I'm planning to test out a Linksys USB
>> adapter
>>>>> that I bought to see if I can get that to work. If
>> not,
>>>>> then perhaps my problem is more at the OS level than
>> at
>>>>> the NIC level. I find that hard to believe, since
the
>>>>> rest of the machines seems to run fine, but I'm
ready
>> to
>>>>> try anything at this point.
>>>>>> -----Original Message-----
>>>>>> Martin:
>>>>>>
>>>>>> The MN 730 PCI card and the MN 720 notebook bus
card adaptor use
>>>>>> the same driver. I ran into a weak signal problem
using this
>>>>>> particular driver when I updated firmware and
drivers from the
>>>>>> "msbndownload.exe". Since I installed the driver
pre-SP2, the
>>>>>> only problem I ran into was the weak signal. (I'm
using a MN 700
>>>>>> and MN 720) Rolling back the driver to the
>>>>> the driver to the
>>>>>> previous version restored signal strength.
>>>>>>
>>>>>> I have the full (266mb) installation of SP-2 ready
to be deployed
>>>>>> to several
>>>>> deployed to several
>>>>>> machines. I'm not sure now I want to install SP-2
based on your
>>>>>> post and
>>>>> on your post and
>>>>>> several others I've read in this group. You
stated that the old
>>>>>> driver won't work at all with SP-2? That doesn't
sound right but
>>>>>> since I haven't
>>>>> but since I haven't
>>>>>> had a chance to test it, I can't verify that.
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>>
>>>>>> "Martin" <(E-Mail Removed)> wrote in
message
>>>>>> news:519501c480a3$f45dd070$(E-Mail Removed)...
>>>>>>> I am starting a new thread because I originally
>> posted
>>>>>>> this problem of mine deep inside someone else's
>>>> thread.
>>>>>>>
>>>>>>> I use a MN-700 AP and a MN-730 PCI adapter. After
>>>>>>> installing SP2 for XP, I got warning messages
that I
>>>>>>> needed to update my software (i.e. drivers). I
>>>>> downloaded
>>>>>>> and installed the MSBNDownload.exe program from
>>>>>>> Microsoft, and the software update was successful.
>> The
>>>>>>> wireless configuration in Windows found my
wireless
>>>>>>> network properly, and I thought I was on my way.
>>>>>>>
>>>>>>> But then strange behavior started popping up. My
>>>>>>> connection would get dropped after a minute or two
>> of
>>>>>>> being connected. Sometimes it would connect to the
>>>>>>> wireless network, but the wireless connection
icon in the
>>>>> the
>>>>>>> system tray would say that the network was
>>>> unavailable-
>>>>>>> yet I was able to browse the web perfectly for a
>> short
>>>>>>> while. Sometimes it wouldn't connect at all. It
>> would
>>>>>>> never reconnect after a reboot.
>>>>>>>
>>>>>>> I tried turning on different layers of encryption,
>>>> such
>>>>>>> as WEP 128bit and WPA-PSK. Both encryption types
did
>>>>>>> nothing to solve my problem. I tried to run the
>>>> network
>>>>>>> without any security, and the same behavior was
>>>>> exhibited.
>>>>>>>
>>>>>>> I went to my Device Manager, and I noticed that
the
>>>>>>> driver for my PCI card was listed as "Microsoft
>>>>> Wireless
>>>>>>> Notebook Adapter". Since this is a desktop, I
>> thought
>>>>>>> maybe the MSBNDownload update installed the wrong
>>>>> driver
>>>>>>> for my card. So I used the Update Driver utility
to
>>>>>>> select the old driver to use. This did not solve
my
>>>>>>> problem, as the old driver doesn't work with SP2,
and I
>>>> I
>>>>>>> ran into problems connecting to the network.
>>>>>>>
>>>>>>> I am concerned that the driver update Microsoft
>>>>> released
>>>>>>> is buggy. Can Microsoft provide me with a single
>>>>> download
>>>>>>> of the most current driver for this device? My
>>>>> suspicion
>>>>>>> is that the driver that was installed by the
>>>>> MSBNDownload
>>>>>>> update was the wrong one.
>>>>>>>
>>>>>>> I own two of these cards, although only one of
them is in
>>>>> in
>>>>>>> use. Until I installed SP2 and the new device
>> driver,
>>>>>>> this card and my wireless network worked
flawlessly, and
>>>>> and
>>>>>>> I told my friends to buy Microsoft's wireless
>> hardware
>>>>>>> because it was the easiest to setup and configure.
>> But
>>>>>>> now I'm stuck with a sucky network and problems
that can
>>>>> can
>>>>>>> only be driver related.
>>>>>>
>>>>>>
>>>>>> .
>>>>>>
>>>>> .
>>>>>
>>>
>>> --
>>> Barb Bowman
>>> Expert Zone Columnist
>>> http://www.microsoft.com/windowsxp/expertzone
>>> MS-MVP (Windows)
>>> .
>
>
>--
> Barb Bowman
> Expert Zone Columnist
> http://www.microsoft.com/windowsxp/expertzone
> MS-MVP (Windows)
>
>
>.
>

there is no version of Media Center Edition that has SP2 already in
it. you can install Media Center and then update to SP2. If you
install SP2 to a MCE machine, and have not previously upgraded to MCE
2004, you will get the MCE upgrade.

I have a HP 873n MCE with a MN-730 in it. I previously upgrade the
machine to MCE 2004. I have install SP2. I've installed all the
updated bits for the MS hardware. It worked fine with the MN-700 (and
other brands of wifi routers).

On Fri, 13 Aug 2004 08:25:01 -0700, "Mike L"
<(E-Mail Removed)> wrote:

>For me, this was a completely fresh install of Media
>Center Edition which has SP2 in it already. No other
>wireless NIC had ever been in the system. Nothing to
>uninstall and the only firewall was the native one.
>>-----Original Message-----
>>Uninstall the BNU utility, reboot, and use only Windows
>XP's built in
>>application to configure and connect to these routers.
>Do you have a third
>>party firewall installed? Try uninstalling it.
>>
>>Martin wrote:
>>> Barb,
>>>
>>> I have tried connecting my MN-730 to both Microsoft's
>MN-
>>> 700 and an older SMC 802.11b router, and both times it
>>> would either not connect or the connection would drop
>>> after a few minutes.
>>>
>>> Last night I bought a Linksys USB Wireless G adapter. I
>>> installed it and it works perfectly with my MN-700
>router-
>>> I get a good, strong signal that doesn't break off. I
>am
>>> now convinced that something is wrong with the driver
>for
>>> my MN-730 adapter.
>>>
>>> I suppose that the last thing I can try is completely
>>> uninstalling and reinstalling the adapter and its
>>> software. I'll try that tonight.
>>>
>>> At the end of the day, Microsoft is dropping this
>entire
>>> line of products, so I suppose it's for the best that
>we
>>> all start transitioning away to other hardware vendors.
>>> It's too bad, since I really love the performance of my
>>> Microsoft adapters until this driver problem hit me.
>>>> -----Original Message-----
>>>> I have wireless routers and access points from
>Netgear,
>>> Linksys,
>>>> DLink, Buffalo, Motorola, 3Com and SMC and have no
>problems
>>>> connecting to them with the Microsoft NICs. I use WPA
>when available
>>>> and WEP when it is not. Using XP SP2 on all machines
>here.
>>>>
>>>> On Thu, 12 Aug 2004 20:04:55 -0700, "Mike L"
>>>> <(E-Mail Removed)> wrote:
>>>>
>>>>> I am pretty sure the new drivers are broken at least
>>> when
>>>>> it comes to connecting to third party wireless AP's.
>I
>>>>> can't connect to my D-Link DI-713P AP with the MN-
>730.
>>>>> When I swap in an off-brand $30 802.11b card it
>>> connects
>>>>> no problem. (This is NOT one of the AP's that
>supports
>>>>> the D-Link non standard higher speed b protocol. It's
>>> way
>>>>> older than that.)
>>>>> The setup software sees the wireless network, senses
>>> that
>>>>> that WEP is turned off and then complains that the
>WEP
>>>>> key I've provided (which, of course the software does
>>> not
>>>>> let me do) does not work. Same behavior with WEP on
>>>>> except that it sees the WEP and lets me enter a key.
>>>>>
>>>>> I have not tried to connect to an MS g AP yet. (I
>keep
>>>>> forgetting to bring it home.)
>>>>>
>>>>>> -----Original Message-----
>>>>>> The old driver didn't work for me as soon as I
>>> installed
>>>>>> SP2; before I installed the MSBNDownload.exe, I was
>>>>>> unable to connect to my wireless network.
>>>>>>
>>>>>> tonight, I'm planning to test out a Linksys USB
>>> adapter
>>>>>> that I bought to see if I can get that to work. If
>>> not,
>>>>>> then perhaps my problem is more at the OS level than
>>> at
>>>>>> the NIC level. I find that hard to believe, since
>the
>>>>>> rest of the machines seems to run fine, but I'm
>ready
>>> to
>>>>>> try anything at this point.
>>>>>>> -----Original Message-----
>>>>>>> Martin:
>>>>>>>
>>>>>>> The MN 730 PCI card and the MN 720 notebook bus
>card adaptor use
>>>>>>> the same driver. I ran into a weak signal problem
>using this
>>>>>>> particular driver when I updated firmware and
>drivers from the
>>>>>>> "msbndownload.exe". Since I installed the driver
>pre-SP2, the
>>>>>>> only problem I ran into was the weak signal. (I'm
>using a MN 700
>>>>>>> and MN 720) Rolling back the driver to the
>>>>>> the driver to the
>>>>>>> previous version restored signal strength.
>>>>>>>
>>>>>>> I have the full (266mb) installation of SP-2 ready
>to be deployed
>>>>>>> to several
>>>>>> deployed to several
>>>>>>> machines. I'm not sure now I want to install SP-2
>based on your
>>>>>>> post and
>>>>>> on your post and
>>>>>>> several others I've read in this group. You
>stated that the old
>>>>>>> driver won't work at all with SP-2? That doesn't
>sound right but
>>>>>>> since I haven't
>>>>>> but since I haven't
>>>>>>> had a chance to test it, I can't verify that.
>>>>>>>
>>>>>>> Regards.
>>>>>>>
>>>>>>>
>>>>>>> "Martin" <(E-Mail Removed)> wrote in
>message
>>>>>>> news:519501c480a3$f45dd070$(E-Mail Removed)...
>>>>>>>> I am starting a new thread because I originally
>>> posted
>>>>>>>> this problem of mine deep inside someone else's
>>>>> thread.
>>>>>>>>
>>>>>>>> I use a MN-700 AP and a MN-730 PCI adapter. After
>>>>>>>> installing SP2 for XP, I got warning messages
>that I
>>>>>>>> needed to update my software (i.e. drivers). I
>>>>>> downloaded
>>>>>>>> and installed the MSBNDownload.exe program from
>>>>>>>> Microsoft, and the software update was successful.
>>> The
>>>>>>>> wireless configuration in Windows found my
>wireless
>>>>>>>> network properly, and I thought I was on my way.
>>>>>>>>
>>>>>>>> But then strange behavior started popping up. My
>>>>>>>> connection would get dropped after a minute or two
>>> of
>>>>>>>> being connected. Sometimes it would connect to the
>>>>>>>> wireless network, but the wireless connection
>icon in the
>>>>>> the
>>>>>>>> system tray would say that the network was
>>>>> unavailable-
>>>>>>>> yet I was able to browse the web perfectly for a
>>> short
>>>>>>>> while. Sometimes it wouldn't connect at all. It
>>> would
>>>>>>>> never reconnect after a reboot.
>>>>>>>>
>>>>>>>> I tried turning on different layers of encryption,
>>>>> such
>>>>>>>> as WEP 128bit and WPA-PSK. Both encryption types
>did
>>>>>>>> nothing to solve my problem. I tried to run the
>>>>> network
>>>>>>>> without any security, and the same behavior was
>>>>>> exhibited.
>>>>>>>>
>>>>>>>> I went to my Device Manager, and I noticed that
>the
>>>>>>>> driver for my PCI card was listed as "Microsoft
>>>>>> Wireless
>>>>>>>> Notebook Adapter". Since this is a desktop, I
>>> thought
>>>>>>>> maybe the MSBNDownload update installed the wrong
>>>>>> driver
>>>>>>>> for my card. So I used the Update Driver utility
>to
>>>>>>>> select the old driver to use. This did not solve
>my
>>>>>>>> problem, as the old driver doesn't work with SP2,
>and I
>>>>> I
>>>>>>>> ran into problems connecting to the network.
>>>>>>>>
>>>>>>>> I am concerned that the driver update Microsoft
>>>>>> released
>>>>>>>> is buggy. Can Microsoft provide me with a single
>>>>>> download
>>>>>>>> of the most current driver for this device? My
>>>>>> suspicion
>>>>>>>> is that the driver that was installed by the
>>>>>> MSBNDownload
>>>>>>>> update was the wrong one.
>>>>>>>>
>>>>>>>> I own two of these cards, although only one of
>them is in
>>>>>> in
>>>>>>>> use. Until I installed SP2 and the new device
>>> driver,
>>>>>>>> this card and my wireless network worked
>flawlessly, and
>>>>>> and
>>>>>>>> I told my friends to buy Microsoft's wireless
>>> hardware
>>>>>>>> because it was the easiest to setup and configure.
>>> But
>>>>>>>> now I'm stuck with a sucky network and problems
>that can
>>>>>> can
>>>>>>>> only be driver related.
>>>>>>>
>>>>>>>
>>>>>>> .
>>>>>>>
>>>>>> .
>>>>>>
>>>>
>>>> --
>>>> Barb Bowman
>>>> Expert Zone Columnist
>>>> http://www.microsoft.com/windowsxp/expertzone
>>>> MS-MVP (Windows)
>>>> .
>>
>>
>>--
>> Barb Bowman
>> Expert Zone Columnist
>> http://www.microsoft.com/windowsxp/expertzone
>> MS-MVP (Windows)
>>
>>
>>.
>>

--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)