This is it, a winner. In WinXP, go to the Device Manager, Network adapters, Wireless adapter, Properties, Advanced tab, scroll down to Power Saving Mode, and change to CAM.

Yup.. I was having the same issues. I followed Dan’s instructions above and now, we are good to go.

It may not only be cheaper than “returning” your unit, but if you really like the Wind, and want to rid of your router problems, this may be the smartest little upgrade you’ll ever do.

http://discussions.apple.com/thread.jspa?messageID=8766006

Here’s the text:

“Going to the Ralink Wireless Configuration Utility and UNCHECK “Power Saving Mode” and ENABLE “CAM (Constantly Awake Mode)” really works. My airport extreme is not crashing anymore. The msi wind work fast and beautiful.I can go to websites without crashing the airport.
The steps are: go to control panel, click on systems. Click on hardware, click on device manager.Click on network adapter.Click on the wireless adapter. click on the advanced tab and under property, scroll down and find for “Power saving mode”, change the value to CAM(constantly Awake Mode). Click ok and That’s it. The msi wind will work now without crashing the airport extreme. Good Luck! ”

I tested it, and it worked. It also works if you are using the Windows configuration. Right click on your network connection in the notification area, choose ’status’ of your network connection. Click ‘properties’ in your status window, then ‘configure’ in the properties window that opens. Choose the ‘advanced’ tab, then the ‘power saving mode” item, then pick “CAM.”

(In fact, you can make the change using the Windows method even if you are running the RALINK config utility as your primary connection method – since it seems some versions of the RALINK utility don’t offer the power saving CAM option.)

In any case, it has been working for me!

- Dan

it would be newsworthy if dlink/linksys/netgear routers didnt crap out on a regular basis due to connection-overload, overheating, RFI

get used to it!

This is by definition a problem with the Apple router. The netbook might be triggering this problem, but the router should not be crashing under any circumstances. Keep in mind the 2.4GHz band is fair game for *anything.* Routers have to deal with analog phones, running microwaves, and other wireless networks. You could even think about this as a potential vulnerability to a DDoS attack.

Kevin,
Did you check that your Apple router and Dave’s were at the same firmware release level?
Some other things to try for people having a problem:
-Try no encryption, WPA and WPA2.
-Chances are that WPA can be used with either TKIP or AES, so try them both.
-WPA passwords can be up to 63 characters or so, but maybe there’s a bug, so try a short password as a test. Short passwords, in general, are bad things, I’m only suggesting it as a test in case there is a bug somewhere with very long passwords.
-Finally, there are some oddball parameters for a Wi-Fi network connection that I don’t understand. Things like the length of the header. All I can suggest, if nothing else works, is to experiment with these too.
-When testing things, its probably best to reboot the router between each test.

I honestly believe this is a Airport extreme problem. I have a Time Capsule and recently got a Aspire One netbook. Despite driver changes etc, my AAO will not maintain a constant connection to the apple router. It continually just stops working, yet shows everything is okay. My 2 other notebooks connect and maintain connections fine.
Thinking it was an AAO problem, I decided after multiple updates of drivers to try one last thing. I enabled the wireless on my DSL modem which has a built in wireless router that I had previously disabled, and voila, problem solved. No more disconnects. Reconnect to the Apple router, trouble again.
Even though not exactly the same as the Wind, very similar in that wireless problems are creeping up with netbooks. (The AAO uses Atheros drivers.) I think we need a firmware update soon to resolve these problems.

One more point of reference… I too run WPA2 and had no problems. The Wind I had was the b/g WiFi card, not the b/g/n. Not sure if it makes a difference.

How odd, I’ve been having an odd issue with my AEBS and it all started when my new Wind arrived a last week, so it seems this is not uncommon. The wifi connection basically melted down when the wind connected and its been wonky since.

Agree, this points to a bug in the AEBS, but I prefer having a protected network. As I use the AEBS for printer sharing & time machine backups, I didn’t want to swap the router.

I ended up voiding my Wind’s warranty and swapped the Wind’s Realtek mini-pci wifi with a Dell Trumobile 1500 card. Using this Broadcom based wifi card, the Wind works great both in XP and OS X 10.5.5.

Isn’t actually a problem of Apple rather than MSI? Winds have worked with other routers without such issues and Apple laptops have been working with non-Apple routers fine, so the problem must lie in Apple router, I guess.

I don’t know… My (former) MSI Wind and my AEBS worked fine together. Maybe he downloaded some malware onto XP or something.

Its an AirPort problem by definition. It should not be possible to crash a router no matter what junk is thrown at it.

I also had a P.O.S. PackardBell desktop that I bought when in South Africa and it always crashed my Airport Extreme.

Sorry, but I never figured out the problem in either case.