Wireless network “appears compromised”

by garth on January 19, 2008

I’m seeing a lot of this disturbing little error message: “The wireless network appears to have been compromised and will be disabled for about a minute.”

The wireless network appears to have been compromised...

A poke around the Internet doesn’t show much other than other people complaining about the same problem. Some find the only way to solve the problem is to disable WPA. I’m not so sure that’s a smart idea. I hope there’s a fix for this in 10.5.2.

[If you’re getting this on what you think is a Django-only feed, it’s because the community feed administrators haven’t yet updated their subscription to point to my Django posts only. Sorry about that.]


m 01.19.08 at 11:18 pm

do you have the same problems with wpa2?

zero 01.20.08 at 2:32 am

Django compromises wireless networks! Everyone panic! :)

James 02.17.08 at 10:30 am

I had the same issue – a move to WPA2 made it go away.

Ghostdriver 04.27.08 at 7:42 am

I had the same thing. The last thing I installed before it started was Azureus (torrent client). It’s java based.

I use WPA-TKIP for encryption and have 10.5.2 (just bought my Macbook Pro earlier this month (April).

Ideas on other ways to fix/disable the prompt?


garth 04.28.08 at 12:38 pm

It seemed to go away after I upgraded to 10.5.2.

R3dFox 04.30.08 at 8:19 pm

Nope, i got 10.5.2 as well – and just got it again :-@

Monkeyrobot 05.09.08 at 3:50 am

yep I get this daily on new macbook pro, 10.5.2, and it drives me nuts.. I think it’s down to the flakey signal from my router.. I know the signal hasn’t been compromised, like hacked, as I’m in the middle of nowhere, rural sticksville, and the cows aint using wifi

Samuli 06.12.08 at 3:27 am

I had this problem constantly with WPA. Changing to WPA2 took away the problem, but my other computer wasn’t able to deal with WPA2.

10.5.3. has now been released and installed it a couple of hours ago. At least so far the problem has disappeared even with WPA. Fingers crossed..

Patrick Hooper - Wireless Data Solutions 07.03.08 at 10:36 am

Yes, WPA2 is the way to go.

Kari Penttilä 08.21.08 at 11:26 pm

I have cracked this – if you have tried to access the wireless using wrong wireless autentication protocol say WEP personal instead WEP2 personal – and entered password – for both – THEN in flaky reception conditions mac tries first the wrong authentication method and messes somehow the right one – BUT you can fix this by going switcing airport off then go keychainaccess and delete the credentials – and then connect to wlan again – that should do it.

Tim 08.26.08 at 12:49 am

Randomly ran across your post during a search for the problem online. It looks like the solution isn’t so much WPA2 as it is choosing the AES encryption method instead of TKIP. Some routers allow you to choose – TKIP seems to cause problems during periods of heavy use. (I was having the problem while using a Linksys WRT54Gv8 with DD-WRT installed. It would show up most often while using Skype. Switching from TKIP to AES solved the problem immediately.)

Good luck!

Wireless Network Support 09.15.08 at 2:24 pm

I am not sure whether the level of security encryption is the reason the wireless started bugging, but if it work better with WAP2 then so be it because it enhances the security.

Wireless network Riley Martin 09.18.08 at 10:23 pm

Switching to WPA2 usually helps

Silver 09.19.08 at 8:12 am

I usually hear only good things about Mac so I’m happy now that I have a PC since i don’t get this message. I do want Mac thou :)

Acai Berry 10.02.08 at 3:22 am

wep keys are easy to break
“I usually hear only good things about Mac so I’m happy now that I have a PC since i don’t get this message. I do want Mac thou :)”

PC dont care if someone breaks in your wireless network

Andreas 11.24.08 at 4:37 am

I have the same, persistent problem with this bogus message rendering my wireless connectivity useless. Mac OS X 10.5.5, latest model MacBook (November 2008), WPA encryption.

James 01.01.09 at 8:51 am

This message is not bogus but has nothung to do with the network beeing compromised but rather a problem with the wireless router you are using and OS X. It occurrs with dlink and linksys routers but more so with Linksys. Neithe Apple or the roter companies have addressed this issue althoug its been around along time. There have messages on various forums dating back overa year to Tiger 10.4.4 and now Leopard. I recenly upgraded from 10.5.5 to 10.5.6 and started having this error message appear every three or four minuted. Very annoying. Already using WAP2 on my Lynksys router. Disablling VP4 or VPS didn’t work nor did changing from AES to TKIP as suggested previously. Swithching off the Airport and going to keychainacess and making sure the box for the network I was using and using the repair function then rebooting and turning Airport back on again did clear up the problem immediately. If you can’t solve the problem using one of the methods mentioned, just park the message out of site while you work and your internet will work just fine.

panqihf 01.03.09 at 7:05 pm

I was having the problem while using a Linksys WRT54Gv8 with DD-WRT installed. It would show up most often while using Skype. Switching from TKIP to AES solved the problem immediately

Paul 01.27.09 at 5:30 pm

I had this problem in spades whenever more than one computer was on the wireless network (Motorola SBG900/Comcast). The problem went away by switching to AES, thanks all!

HC 01.29.09 at 7:35 am

This issue first appeared when I was using a slingbox (streaming video)
switching to AES resolved it for me. Linksys HR200 + MacBook 10.5.6

sheri3466 06.29.09 at 4:12 am

Hi All, I’m having the same problem on an Orange wireless router. Unfortunately, I’m a complete novice at changing settings – can anyone tell me how I change to AES? Any & all helpful suggestions would be much appreciated.

Andres 08.27.09 at 12:30 am

Is it remotely possible that someone IS actually trying to hack in? (I’m in Manhattan and can see more than 50 networks from my apartment!) The way your hacker neighbor will try to get in, is by issuing a command that confuses the wireless router and forces all connections to drop. They then try to come back up and during this process, the hacker listens to the exhange of info from the Access point to the computers. They then run decryption on these hashes and eventually get your WAP2 key. It is just a matter of time.
Mac is smsrt and know this, so it won’t let you reconnect during the period when the hacker is listening to the reconnect.

To all those who have this problem, use a wireless scanning tool such as iStumbler and look for any ad-hoc networks. by just walking around your building and looking at signal levels, you ill find who your nasty neighbor is and hopefully get back to him!!!
Remember that if you get this error every 4 minutes, it could very well be a robot set to to try every 4 minutes until they hack in, not necessarily a crapy netgear router!!!

Andreas 09.03.09 at 10:09 pm

In my case, the problem went away after I tweaked the settings of my airport software and upgraded the system software.

I use neither a dlink nor a linksys router. This problem has been widely reported in mac sites and indeed appears to have been a bug in the wireless software.

sheri3466 09.04.09 at 4:10 am

Hi, a wee update, I changed my router, and since I’ve gone to O2 I got a new router which has better encryption ie. AES (WEP2). No problems ever since. I now love my new Macbook Pro!

Comments on this entry are closed.