MN-740 Firmware Upgrade to 1.0.2.21

Want to burn firmware 1.0.2.21 to enable non-broadcast of
SSID. Downloaded the bundle and have tried many, many
times but without success for firmware; boot is already
current. Using both a WinXP Pro and a WinME box, this is
what I tried:

1. WinX box and MN-740 cabled to standalone hub
2. WinX box direct connected to MN-740 via crossover

In all cases, the utility sees the device fine but won't
upgrade the firmware. I've tried resetting MN-740 to
factory defaults, power on/off, etc. ad nauseum. None of
the boxes in question were running any sort of virus,
popup, etc. protection or firewall. Any ideas much
appreciated. Thx.

Check the update readme file:
http://www.microsoft.com/hardware/br..._mn740_102.htm
Instructions are listed there.
--
Chris H.
Microsoft Windows MVP/Tablet PC
Tablet Creations - http://nicecreations.us/
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone


"Phil" <(E-Mail Removed)> wrote in message
news:043a01c4f038$31623110$(E-Mail Removed)...
> Want to burn firmware 1.0.2.21 to enable non-broadcast of
> SSID. Downloaded the bundle and have tried many, many
> times but without success for firmware; boot is already
> current. Using both a WinXP Pro and a WinME box, this is
> what I tried:
>
> 1. WinX box and MN-740 cabled to standalone hub
> 2. WinX box direct connected to MN-740 via crossover
>
> In all cases, the utility sees the device fine but won't
> upgrade the firmware. I've tried resetting MN-740 to
> factory defaults, power on/off, etc. ad nauseum. None of
> the boxes in question were running any sort of virus,
> popup, etc. protection or firewall. Any ideas much
> appreciated. Thx.
>

Thanks Chris.

Followed the instructions to the 'T' several times, as did
several other buds. Just don't work.


>-----Original Message-----
>Check the update readme file:
>http://www.microsoft.com/hardware/br..._mn740_102.htm

>Instructions are listed there.
>--
>Chris H.
>Microsoft Windows MVP/Tablet PC
>Tablet Creations - http://nicecreations.us/
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>
>"Phil" <(E-Mail Removed)> wrote in message
>news:043a01c4f038$31623110$(E-Mail Removed)...
>> Want to burn firmware 1.0.2.21 to enable non-broadcast of
>> SSID. Downloaded the bundle and have tried many, many
>> times but without success for firmware; boot is already
>> current. Using both a WinXP Pro and a WinME box, this is
>> what I tried:
>>
>> 1. WinX box and MN-740 cabled to standalone hub
>> 2. WinX box direct connected to MN-740 via crossover
>>
>> In all cases, the utility sees the device fine but won't
>> upgrade the firmware. I've tried resetting MN-740 to
>> factory defaults, power on/off, etc. ad nauseum. None of
>> the boxes in question were running any sort of virus,
>> popup, etc. protection or firewall. Any ideas much
>> appreciated. Thx.
>>
>
>
>.
>

Chris,

Tricky little beggar this one! When you reset the MN-740,
it reverts to its default IP address--in my case (yours may
vary?) 169.254.194.195. I found this out by running the
Microsoft Broadband Networking software (v2.2.0.731), which
displayed the device and its IP. OK, reasoned I, would the
firmware upgrade software running on my XP box, on a
192.168.x.x network, be able to talk to the MN-740? Not
bloody likely. Changed my box's IP to 169.254.194.194
(mask 255.255.255.0) cabled MN-740 and the box to a hub
and, viola!, the upgrade went in slick as snot. Cheers!

Phil


>-----Original Message-----
>Check the update readme file:
>http://www.microsoft.com/hardware/br..._mn740_102.htm

>Instructions are listed there.
>--
>Chris H.
>Microsoft Windows MVP/Tablet PC
>Tablet Creations - http://nicecreations.us/
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>
>"Phil" <(E-Mail Removed)> wrote in message
>news:043a01c4f038$31623110$(E-Mail Removed)...
>> Want to burn firmware 1.0.2.21 to enable non-broadcast of
>> SSID. Downloaded the bundle and have tried many, many
>> times but without success for firmware; boot is already
>> current. Using both a WinXP Pro and a WinME box, this is
>> what I tried:
>>
>> 1. WinX box and MN-740 cabled to standalone hub
>> 2. WinX box direct connected to MN-740 via crossover
>>
>> In all cases, the utility sees the device fine but won't
>> upgrade the firmware. I've tried resetting MN-740 to
>> factory defaults, power on/off, etc. ad nauseum. None of
>> the boxes in question were running any sort of virus,
>> popup, etc. protection or firewall. Any ideas much
>> appreciated. Thx.
>>
>
>
>.
>

Good for the time being, except you're now outside your own LAN. The
192.*.*.* addresses are reserved IP numbers for local area networks. The
169.254.*.* addresses you're working with now are auto assigned when the
network adapter cannot find the DHCP feed from the router.

Do you happen to be running any Norton (Symantec) software on your computer?
Some of those products, unless properly configured, can cause this issue and
block one system from another.

If a computer on your system happens to pop up the 169 address, it is a good
idea to reboot and see if it'll automatically pick up the feed. And
sometimes you simply need to power-down the router, let it sit a minute, and
then it'll correct itself. Hopefully, you've now righted the ship. 8-)

The reason the MN-740 probably wouldn't upgrade is the 169 address isn't
part of the LAN, and therefore wasn't seen by the other computer.
--
Chris H.
Microsoft Windows MVP/Tablet PC
Tablet Creations - http://nicecreations.us/
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone


"Phil" <(E-Mail Removed)> wrote in message
news:0c3701c4f153$7ffb9430$(E-Mail Removed)...
Chris,

Tricky little beggar this one! When you reset the MN-740,
it reverts to its default IP address--in my case (yours may
vary?) 169.254.194.195. I found this out by running the
Microsoft Broadband Networking software (v2.2.0.731), which
displayed the device and its IP. OK, reasoned I, would the
firmware upgrade software running on my XP box, on a
192.168.x.x network, be able to talk to the MN-740? Not
bloody likely. Changed my box's IP to 169.254.194.194
(mask 255.255.255.0) cabled MN-740 and the box to a hub
and, viola!, the upgrade went in slick as snot. Cheers!

Phil


>-----Original Message-----
>Check the update readme file:
>http://www.microsoft.com/hardware/br..._mn740_102.htm

>Instructions are listed there.
>--
>Chris H.
>Microsoft Windows MVP/Tablet PC
>Tablet Creations - http://nicecreations.us/
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>
>"Phil" <(E-Mail Removed)> wrote in message
>news:043a01c4f038$31623110$(E-Mail Removed)...
>> Want to burn firmware 1.0.2.21 to enable non-broadcast of
>> SSID. Downloaded the bundle and have tried many, many
>> times but without success for firmware; boot is already
>> current. Using both a WinXP Pro and a WinME box, this is
>> what I tried:
>>
>> 1. WinX box and MN-740 cabled to standalone hub
>> 2. WinX box direct connected to MN-740 via crossover
>>
>> In all cases, the utility sees the device fine but won't
>> upgrade the firmware. I've tried resetting MN-740 to
>> factory defaults, power on/off, etc. ad nauseum. None of
>> the boxes in question were running any sort of virus,
>> popup, etc. protection or firewall. Any ideas much
>> appreciated. Thx.
>>
>
>
>.
>

>-----Original Message-----
>Good for the time being, except you're now outside your
own LAN. The
>192.*.*.* addresses are reserved IP numbers for local area
networks. The
>169.254.*.* addresses you're working with now are auto
assigned when the
>network adapter cannot find the DHCP feed from the router.
>

No DHCP on my local LAN, only static 192.x.x.x IPs.

>Do you happen to be running any Norton (Symantec) software
on your computer?
>Some of those products, unless properly configured, can
cause this issue and
>block one system from another.

No, no Norton, or Cramden for that matter :^)

>
>If a computer on your system happens to pop up the 169
address, it is a good
>idea to reboot and see if it'll automatically pick up the
feed. And
>sometimes you simply need to power-down the router, let it
sit a minute, and
>then it'll correct itself. Hopefully, you've now righted
the ship. 8-)
>
Yep, normally I wouldn't 'see' a 169.x.x.x address, but the
MS Broadband Networking software detected the MN-740 and
picked it up. Upon seeing this, I immediately tried
upgrading the firmware but once again to no avail. I had
taken the router and my local LAN out of the loop, just the
XP box and MN-740 hooked to a dump hub.

>The reason the MN-740 probably wouldn't upgrade is the 169
address isn't
>part of the LAN, and therefore wasn't seen by the other
computer.
>--

That was the ticket alright. Once they were on the same
LAN, all was well. Does this mean that, if you're not
using DHCP, the update instructions should be modified? Tks.


>Chris H.
>Microsoft Windows MVP/Tablet PC
>Tablet Creations - http://nicecreations.us/
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>
>"Phil" <(E-Mail Removed)> wrote in message
>news:0c3701c4f153$7ffb9430$(E-Mail Removed)...
>Chris,
>
>Tricky little beggar this one! When you reset the MN-740,
>it reverts to its default IP address--in my case (yours may
>vary?) 169.254.194.195. I found this out by running the
>Microsoft Broadband Networking software (v2.2.0.731), which
>displayed the device and its IP. OK, reasoned I, would the
>firmware upgrade software running on my XP box, on a
>192.168.x.x network, be able to talk to the MN-740? Not
>bloody likely. Changed my box's IP to 169.254.194.194
>(mask 255.255.255.0) cabled MN-740 and the box to a hub
>and, viola!, the upgrade went in slick as snot. Cheers!
>
>Phil
>
>
>>-----Original Message-----
>>Check the update readme file:
>>http://www.microsoft.com/hardware/br..._mn740_102.htm
>
>>Instructions are listed there.
>>--
>>Chris H.
>>Microsoft Windows MVP/Tablet PC
>>Tablet Creations - http://nicecreations.us/
>>Associate Expert
>>Expert Zone - www.microsoft.com/windowsxp/expertzone
>>
>>
>>"Phil" <(E-Mail Removed)> wrote in message
>>news:043a01c4f038$31623110$(E-Mail Removed)...
>>> Want to burn firmware 1.0.2.21 to enable non-broadcast of
>>> SSID. Downloaded the bundle and have tried many, many
>>> times but without success for firmware; boot is already
>>> current. Using both a WinXP Pro and a WinME box, this is
>>> what I tried:
>>>
>>> 1. WinX box and MN-740 cabled to standalone hub
>>> 2. WinX box direct connected to MN-740 via crossover
>>>
>>> In all cases, the utility sees the device fine but won't
>>> upgrade the firmware. I've tried resetting MN-740 to
>>> factory defaults, power on/off, etc. ad nauseum. None of
>>> the boxes in question were running any sort of virus,
>>> popup, etc. protection or firewall. Any ideas much
>>> appreciated. Thx.
>>>
>>
>>
>>.
>>
>
>
>.
>

I believe you said your Xbox had the 169 address, which I guessed was not
part of your LAN. As such, whatever machine you had the upgrade on wouldn't
see the device until you moved into the same realm with it.
--
Chris H.
Microsoft Windows MVP/Tablet PC
Tablet Creations - http://nicecreations.us/
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone


"Phil" <(E-Mail Removed)> wrote in message
news:117c01c4f15d$9b76e750$(E-Mail Removed)...

>-----Original Message-----
>Good for the time being, except you're now outside your
own LAN. The
>192.*.*.* addresses are reserved IP numbers for local area
networks. The
>169.254.*.* addresses you're working with now are auto
assigned when the
>network adapter cannot find the DHCP feed from the router.
>

No DHCP on my local LAN, only static 192.x.x.x IPs.

>Do you happen to be running any Norton (Symantec) software
on your computer?
>Some of those products, unless properly configured, can
cause this issue and
>block one system from another.

No, no Norton, or Cramden for that matter :^)

>
>If a computer on your system happens to pop up the 169
address, it is a good
>idea to reboot and see if it'll automatically pick up the
feed. And
>sometimes you simply need to power-down the router, let it
sit a minute, and
>then it'll correct itself. Hopefully, you've now righted
the ship. 8-)
>
Yep, normally I wouldn't 'see' a 169.x.x.x address, but the
MS Broadband Networking software detected the MN-740 and
picked it up. Upon seeing this, I immediately tried
upgrading the firmware but once again to no avail. I had
taken the router and my local LAN out of the loop, just the
XP box and MN-740 hooked to a dump hub.

>The reason the MN-740 probably wouldn't upgrade is the 169
address isn't
>part of the LAN, and therefore wasn't seen by the other
computer.
>--

That was the ticket alright. Once they were on the same
LAN, all was well. Does this mean that, if you're not
using DHCP, the update instructions should be modified? Tks.


>Chris H.
>Microsoft Windows MVP/Tablet PC
>Tablet Creations - http://nicecreations.us/
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>
>"Phil" <(E-Mail Removed)> wrote in message
>news:0c3701c4f153$7ffb9430$(E-Mail Removed)...
>Chris,
>
>Tricky little beggar this one! When you reset the MN-740,
>it reverts to its default IP address--in my case (yours may
>vary?) 169.254.194.195. I found this out by running the
>Microsoft Broadband Networking software (v2.2.0.731), which
>displayed the device and its IP. OK, reasoned I, would the
>firmware upgrade software running on my XP box, on a
>192.168.x.x network, be able to talk to the MN-740? Not
>bloody likely. Changed my box's IP to 169.254.194.194
>(mask 255.255.255.0) cabled MN-740 and the box to a hub
>and, viola!, the upgrade went in slick as snot. Cheers!
>
>Phil
>
>
>>-----Original Message-----
>>Check the update readme file:
>>http://www.microsoft.com/hardware/br..._mn740_102.htm
>
>>Instructions are listed there.
>>--
>>Chris H.
>>Microsoft Windows MVP/Tablet PC
>>Tablet Creations - http://nicecreations.us/
>>Associate Expert
>>Expert Zone - www.microsoft.com/windowsxp/expertzone
>>
>>
>>"Phil" <(E-Mail Removed)> wrote in message
>>news:043a01c4f038$31623110$(E-Mail Removed)...
>>> Want to burn firmware 1.0.2.21 to enable non-broadcast of
>>> SSID. Downloaded the bundle and have tried many, many
>>> times but without success for firmware; boot is already
>>> current. Using both a WinXP Pro and a WinME box, this is
>>> what I tried:
>>>
>>> 1. WinX box and MN-740 cabled to standalone hub
>>> 2. WinX box direct connected to MN-740 via crossover
>>>
>>> In all cases, the utility sees the device fine but won't
>>> upgrade the firmware. I've tried resetting MN-740 to
>>> factory defaults, power on/off, etc. ad nauseum. None of
>>> the boxes in question were running any sort of virus,
>>> popup, etc. protection or firewall. Any ideas much
>>> appreciated. Thx.
>>>
>>
>>
>>.
>>
>
>
>.
>