for all of you that are having a hell of a time with the mn-740, i recommend
you check out the following link and tell M$ that they need to get their act
together.
http://support.microsoft.com/default...b;en-us;114491
first on my list of suggestions is to get a web interface to configure the
thing. i believe that half of your firmware update problems could be easily
resolved if you could update the firmware from a web interface. not to
mention that the majority of the problems i'm reading begin with getting the
device configured, and it's a pain to sit in front of an xbox to configure
it, especially WEP keys. ironically, i had no problems configuring the
device. from the get go. i enabled broadcast of ssid and disabled all
security settings on my router, as i figured like with all Micro$oft
products that there would be all kinds of problem if there was a hint of
concious security in a home network. Secondly, I would request support for
WPA. I see no reason why the MN-740 (actually I do, but that's another
rant), doesn't already have this in it, and it's a reflection once again of
Micro$oft's lack of concern for your privacy and security. The following is
the actual email I sent to M$, for which I did get a polite response saying
they value my suggesstions, yeah right :
************************************************** *****
1) In accordance with wi-fi certification WPA support should be added to
this device. I have to compromise the security of my entire wireless
network because of the lack of support for this within this adapter. At the
same time support for 4 wep keys should be added, as this is a basic feature
and requirement of all wep enabled devices. It appears no consideration was
given to security when releasing this product.
2) Ability to configure from any web browser. Configuring from the xbox
console is extremely limiting. In Canada this is a $200 device and this
seriously limits the ability to administer and limits this as being an xbox
exclusive product. The bottom line is that this is a wireless bridge, and
therefore it should be able to be administered it as such.
3) There is no way to configure the device without DHCP. You would think
again that this would be the most basic of features with any network
adapter. In fact, this is the only ethernet adapter that I know of that
absolutely requires DHCP. For security reason I prefer to not use DHCP on
my network. Once again I am forced to accomodate this by implenting DHCP.
Hopefully, the above suggestions will make it into a future firmware release
for this product as this product would be a much better product for it. I
would consider the above to be basic requirements for any product of this
type, and at $200 I would hope that Microsoft will implement these
recommendations as soon as possible.