Q: Dropping Wi FI Signal

Once again, Apple engineers do not officially read these forums. Some may monitor them on their free time, but not officially as part of their jobs.

If you are having problems with AppleCare staff, ask to speak to a higher level rep.

AppleCare is the official pathway for technical issues between end users and Apple engineering.

I've been having wireless issues with a late 2007 Imac since snow leopard install. I just wanted to let people know that it's not just laptops having these issues. I always raved about how easy wireless network setup, etc. was on a mac...I've been eating my words for months. Haven't had a stable connection to the internet since I "upgraded" to snow leopard...my Windows PC still connects fine, no other changes to the network. Have't been able to print either (snow leopard compatible printer). It would be nice to see some solutions to the multiple problems people have been experiencing since upgrading. If I had my time back, I never would have bothered with snow leopard...nothing but headaches.

Hi guys,

I read this topic, and I maybe lost something, but I believe I could add a good point to this discussion.
I experienced some wifi connection drop since leopard, quitting and reopening safari usually solved the problem.
Now I am on Snow Leopard 10.6.2 and have similar problems: my wifi connection suddenly drops after about 30 minutes work. Turning airport off and back on usually solves the problem, but it is a big issue when working on remote machines.
The thing I want to add to this discussion, is that I asked my router about the security log and this is the output:
{quote}
2010.01.04 13:53:04 192.168.1.9 login success
2010.01.04 13:53:04 192.168.1.9 forced logout
2010.01.04 13:42:36 192.168.1.9 login success
2010.01.04 13:42:36 192.168.1.9 forced logout
2010.01.04 13:36:21 **TCP FIN Scan** 192.168.1.9, 50792->> 17.149.160.10, 80 (from ATM1 Outbound)
2010.01.04 13:36:21 **TCP FIN Scan** 192.168.1.9, 50802->> 151.7.11.145, 80 (from ATM1 Outbound)
2010.01.04 13:32:10 sending ACK to 192.168.1.5
2010.01.04 13:32:10 sending OFFER to 192.168.1.5
2010.01.04 13:31:20 **TCP FIN Scan** 192.168.1.9, 50792->> 17.149.160.10, 80 (from ATM1 Outbound)
2010.01.04 13:31:20 **TCP FIN Scan** 192.168.1.9, 50802->> 151.7.11.145, 80 (from ATM1 Outbound)
2010.01.04 13:27:42 **TCP FIN Scan** 192.168.1.7, 49518->> 74.125.39.149, 80 (from ATM1 Outbound)
2010.01.04 13:27:42 **TCP FIN Scan** 192.168.1.7, 49577->> 217.154.245.52, 80 (from ATM1 Outbound)
2010.01.04 13:26:38 **TCP FIN Scan** 192.168.1.7, 49698->> 151.7.11.136, 80 (from ATM1 Outbound)
2010.01.04 13:26:38 **TCP FIN Scan** 192.168.1.7, 49710->> 195.27.30.129, 80 (from ATM1 Outbound)
2010.01.04 13:25:35 **TCP FIN Scan** 192.168.1.7, 49334->> 209.85.135.118, 80 (from ATM1 Outbound)
2010.01.04 13:25:35 **TCP FIN Scan** 192.168.1.7, 49698->> 151.7.11.136, 80 (from ATM1 Outbound)
2010.01.04 13:24:31 **TCP FIN Scan** 192.168.1.7, 49698->> 151.7.11.136, 80 (from ATM1 Outbound)
2010.01.04 13:24:21 **TCP FIN Scan** 192.168.1.7, 49617->> 213.92.16.244, 80 (from ATM1 Outbound)
2010.01.04 13:23:28 **TCP FIN Scan** 192.168.1.7, 49698->> 151.7.11.136, 80 (from ATM1 Outbound)
2010.01.04 13:22:51 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:22:26 **TCP FIN Scan** 192.168.1.7, 49497->> 213.92.16.150, 80 (from ATM1 Outbound)
2010.01.04 13:22:26 **TCP FIN Scan** 192.168.1.7, 49312->> 209.85.135.91, 80 (from ATM1 Outbound)
2010.01.04 13:22:26 **TCP FIN Scan** 192.168.1.7, 49728->> 195.27.30.89, 80 (from ATM1 Outbound)
2010.01.04 13:22:26 **TCP FIN Scan** 192.168.1.7, 49241->> 151.7.11.145, 80 (from ATM1 Outbound)
2010.01.04 13:22:26 **TCP FIN Scan** 192.168.1.7, 49292->> 209.85.135.191, 80 (from ATM1 Outbound)
2010.01.04 13:22:24 **TCP FIN Scan** 192.168.1.7, 49518->> 74.125.39.149, 80 (from ATM1 Outbound)
2010.01.04 13:22:24 **TCP FIN Scan** 192.168.1.7, 49577->> 217.154.245.52, 80 (from ATM1 Outbound)
2010.01.04 13:22:24 **TCP FIN Scan** 192.168.1.7, 49698->> 151.7.11.136, 80 (from ATM1 Outbound)
2010.01.04 13:21:48 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:21:21 **TCP FIN Scan** 192.168.1.7, 49493->> 213.92.16.141, 80 (from ATM1 Outbound)
2010.01.04 13:21:21 **TCP FIN Scan** 192.168.1.7, 49708->> 151.7.11.136, 80 (from ATM1 Outbound)
2010.01.04 13:21:21 **TCP FIN Scan** 192.168.1.7, 49729->> 151.7.11.138, 80 (from ATM1 Outbound)
2010.01.04 13:21:05 **TCP FIN Scan** 209.85.135.191, 80->> 151.53.43.16, 49286 (from ATM1 Inbound)
2010.01.04 13:20:44 **TCP FIN Scan** 192.168.1.9, 50725->> 17.250.248.161, 5354 (from ATM1 Outbound)
2010.01.04 13:20:44 **TCP FIN Scan** 192.168.1.9, 50054->> 17.148.16.46, 993 (from ATM1 Outbound)
2010.01.04 13:20:44 **TCP FIN Scan** 192.168.1.9, 50058->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:20:33 **TCP FIN Scan** 192.168.1.7, 49708->> 151.7.11.136, 80 (from ATM1 Outbound)
2010.01.04 13:20:33 **Vecna Scan** 192.168.1.7, 49463->> 209.85.129.100, 80 (from ATM1 Outbound)
2010.01.04 13:20:33 **TCP FIN Scan** 192.168.1.7, 49334->> 209.85.135.118, 80 (from ATM1 Outbound)
2010.01.04 13:20:22 **TCP FIN Scan** 192.168.1.7, 49686->> 213.92.16.191, 80 (from ATM1 Outbound)
2010.01.04 13:20:16 **TCP FIN Scan** 192.168.1.7, 49275->> 74.125.43.166, 80 (from ATM1 Outbound)
2010.01.04 13:20:16 **TCP FIN Scan** 192.168.1.7, 49239->> 17.149.160.10, 80 (from ATM1 Outbound)
2010.01.04 13:19:41 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:19:19 **TCP FIN Scan** 192.168.1.7, 49638->> 213.92.16.217, 80 (from ATM1 Outbound)
2010.01.04 13:19:19 **TCP FIN Scan** 192.168.1.7, 49619->> 213.92.16.244, 80 (from ATM1 Outbound)
2010.01.04 13:19:07 **TCP FIN Scan** 192.168.1.7, 49435->> 194.244.107.100, 80 (from ATM1 Outbound)
2010.01.04 13:19:07 **TCP FIN Scan** 192.168.1.7, 49454->> 212.239.36.214, 80 (from ATM1 Outbound)
2010.01.04 13:19:07 **TCP FIN Scan** 192.168.1.7, 49329->> 209.85.135.104, 80 (from ATM1 Outbound)
2010.01.04 13:18:37 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:18:25 **TCP FIN Scan** 192.168.1.7, 49373->> 74.125.39.149, 80 (from ATM1 Outbound)
2010.01.04 13:18:24 **TCP FIN Scan** 192.168.1.7, 49277->> 74.125.3.84, 80 (from ATM1 Outbound)
2010.01.04 13:18:24 **TCP FIN Scan** 192.168.1.7, 49358->> 209.85.129.100, 80 (from ATM1 Outbound)
2010.01.04 13:18:06 **TCP FIN Scan** 192.168.1.7, 49435->> 194.244.107.100, 80 (from ATM1 Outbound)
2010.01.04 13:18:06 **TCP FIN Scan** 192.168.1.7, 49437->> 213.92.16.141, 80 (from ATM1 Outbound)
2010.01.04 13:18:06 **TCP FIN Scan** 192.168.1.7, 49439->> 213.92.16.31, 80 (from ATM1 Outbound)
2010.01.04 13:17:38 **TCP FIN Scan** 192.168.1.7, 49265->> 91.194.90.201, 80 (from ATM1 Outbound)
2010.01.04 13:17:34 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:17:25 **TCP FIN Scan** 213.92.11.242, 80->> 151.53.43.16, 49340 (from ATM1 Inbound)
2010.01.04 13:17:24 **TCP FIN Scan** 192.168.1.7, 49293->> 209.85.135.191, 80 (from ATM1 Outbound)
2010.01.04 13:17:10 **TCP FIN Scan** 192.168.1.7, 49274->> 74.125.43.154, 80 (from ATM1 Outbound)
2010.01.04 13:17:10 **TCP FIN Scan** 192.168.1.7, 49247->> 79.140.82.24, 80 (from ATM1 Outbound)
2010.01.04 13:17:10 **TCP FIN Scan** 192.168.1.7, 49238->> 17.149.160.27, 80 (from ATM1 Outbound)
2010.01.04 13:17:10 **TCP FIN Scan** 192.168.1.7, 49244->> 151.7.11.145, 80 (from ATM1 Outbound)
2010.01.04 13:17:09 **SYN Flood to Host** 192.168.1.7, 49323->> 209.85.135.91, 80 (from ATM1 Outbound)
2010.01.04 13:16:30 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:15:59 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:15:43 **TCP FIN Scan** 192.168.1.9, 50725->> 17.250.248.161, 5354 (from ATM1 Outbound)
2010.01.04 13:15:43 **TCP FIN Scan** 192.168.1.9, 50054->> 17.148.16.46, 993 (from ATM1 Outbound)
2010.01.04 13:15:43 **TCP FIN Scan** 192.168.1.9, 50058->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:15:35 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:15:31 **TCP FIN Scan** 192.168.1.9, 50062->> 192.135.10.19, 993 (from ATM1 Outbound)
2010.01.04 13:15:31 **TCP FIN Scan** 192.168.1.9, 50073->> 212.52.84.160, 143 (from ATM1 Outbound)
2010.01.04 13:15:31 **TCP FIN Scan** 192.168.1.9, 50048->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:15:31 **TCP FIN Scan** 192.168.1.9, 50054->> 17.148.16.46, 993 (from ATM1 Outbound)
2010.01.04 13:15:29 **TCP FIN Scan** 192.168.1.9, 50113->> 212.52.84.160, 143 (from ATM1 Outbound)
2010.01.04 13:15:29 **TCP FIN Scan** 192.168.1.9, 50056->> 192.135.10.19, 993 (from ATM1 Outbound)
2010.01.04 13:15:29 **TCP FIN Scan** 192.168.1.9, 50101->> 17.148.16.46, 993 (from ATM1 Outbound)
2010.01.04 13:15:29 **TCP FIN Scan** 192.168.1.9, 50438->> 74.125.39.109, 993 (from ATM1 Outbound)
2010.01.04 13:15:24 sending ACK to 192.168.1.9
2010.01.04 13:15:24 sending ACK to 192.168.1.9
2010.01.04 13:12:50 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:11:46 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:10:43 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:09:39 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:08:36 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:07:32 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:06:29 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:05:57 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:05:41 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:05:33 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:05:29 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:05:27 **TCP FIN Scan** 192.168.1.7, 49173->> 151.7.11.139, 80 (from ATM1 Outbound)
2010.01.04 13:02:06 **TCP FIN Scan** 192.168.1.9, 50641->> 209.85.135.139, 80 (from ATM1 Outbound)
2010.01.04 13:02:06 **TCP FIN Scan** 192.168.1.9, 50646->> 66.227.17.22, 80 (from ATM1 Outbound)
2010.01.04 13:02:06 **TCP FIN Scan** 192.168.1.9, 50647->> 209.85.135.155, 80 (from ATM1 Outbound)
2010.01.04 13:01:22 **TCP FIN Scan** 151.7.11.139, 80->> 151.53.43.16, 49175 (from ATM1 Inbound)
2010.01.04 13:00:31 **TCP FIN Scan** 213.92.16.191, 80->> 151.53.43.16, 49211 (from ATM1 Inbound)
2010.01.04 12:58:41 sending ACK to 192.168.1.7
2010.01.04 12:58:40 sending OFFER to 192.168.1.7
2010.01.04 12:58:36 sending OFFER to 192.168.1.7
2010.01.04 12:58:33 sending OFFER to 192.168.1.7
2010.01.04 12:58:31 sending OFFER to 192.168.1.7
{quote}

Please note that 192.168.1.7 is a Mac Mini connected by ethernet (who does not suffer of dropped connection) while 192.168.1.9 is my MacBook connected by wifi to my wireless 3Com router (3CRWDR100A-72).

It seems that my systems are running a tcp scan to some unknown addresses..
An investigation about this addresses let me know that they are all connected to mail accounts I read using Mail.
Further investigation on /private/var/log/system.log gives:

{quote}
Jan 4 13:30:20 john-does-macbook-3 Safari[711]: Periodic CFURLCache Insert stats (iters: 394) - Tx time:0.388056, # of Inserts: 49, # of bytes w
ritten: 656721, Did shrink: NO, Size of cache-file: 182534144, Num of Failures: 0
Jan 4 13:30:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet not needed - wrongState:0
Jan 4 13:30:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet issued SELECT before CLOSE - wrongState:0
Jan 4 13:30:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet not needed - wrongState:0
Jan 4 13:30:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet issued SELECT before CLOSE - wrongState:0
Jan 4 13:31:19 john-does-macbook-3 SystemUIServer[651]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil.
This is a programming error. Break on _NSWarnForDrawingImageWithNoCurrentContext to debug. This will be logged only once. This may break in the future.
Jan 4 13:35:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet not needed - wrongState:0
Jan 4 13:35:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet issued SELECT before CLOSE - wrongState:0
Jan 4 13:35:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet not needed - wrongState:0
Jan 4 13:35:32 john-does-macbook-3 Mail[695]: Mail: SafetyNet issued SELECT before CLOSE - wrongState:0
Jan 4 13:35:33 john-does-macbook-3 Mail[695]: Mail: SafetyNet not needed - wrongState:0
Jan 4 13:35:33 john-does-macbook-3 Mail[695]: Mail: SafetyNet issued SELECT before CLOSE - wrongState:0
Jan 4 13:35:33 john-does-macbook-3 Mail[695]: Mail: SafetyNet issued SELECT before IDLE - wrongState:0
{quote}

it seems to me that an error from Mail starts all this.

Does anybody have any idea to solve this problem?

Message was edited by: SnowPuma

Hi,

I am experiencing the same thing on my mac mini. For some reasons the wifi connections gets dropped. The only way to get it back is restarting Airport. It is not constantly but at least one a day.

Any suggestions are welcome.

Lars

2010.01.04 13:42:36 192.168.1.9 forced logout

You need to find out why this is occurring; if your router is forcibly logging you out, you need to find out why; if that's just a message that is logged when your MacBook falls off the network, that's another.

The IP addresses in question seem to belong to your ISP and Google, and as such are probably IMAP "IDLE" connections.

Hmm, given SnowPuma's observation, I wonder if Apple Mail is causing the problems? I have it running all the time, and as I mentioned in a previous email, the Mail program does ask me for my password sporadically, even though it is in my Keychain, so there is an issue with the Mail program since I upgraded to SL. (The term "upgrade" does seem singularly inappropriate in this case!)

I don't think so - I use Apple Mail exclusively and haven't had an AirPort drop on any network on since 2007.

Ah well, back to the drawing board. Channel switching does at least give me a usable system. Odd behavior with Mail though. Seems it cannot retrieve the password, but only sporadically.

Are there any errors logged to your system.log that seem to correspond with when it cannot retrieve the password?

After I updated to SL, Mail asked me for passwords a few times, but only on selected Mail accounts. After several "reminders", this behavior stopped. I haven't had it ask me again for months now.

I'll check next time it happens. It's been fine for two or three weeks now. When it does act up, it will ask me repeatedly for my password. I tried the obvious fix of deleting the Mail password in the Keychain and recreating it but that had no effect.

I don't use Mail. I login to my e-mail directly online (if it is working) so Mail is not my problem. My 15" MacBook Pro is new out of the box with SL as a 2009 Christmas present. Have tried practically everything on this and several other threads and on searches on the web. Netgear dual band router works fine with with older 13" MacBook & Dell computers so I don't want to mess with it. Just about the only other thing I haven't tried is opening up the thing and checking to see if the wires are screwed in to the Airport card. I'm having to go through diagnostics and re-enter my password literally every 2-5 min. This is NOT making for a good argument to get my hubby to switch to Mac.

california99 wrote:
I'll check next time it happens. It's been fine for two or three weeks now. When it does act up, it will ask me repeatedly for my password. I tried the obvious fix of deleting the Mail password in the Keychain and recreating it but that had no effect.

I also assume you've run the Keychain Utility to check for errors?

Kartyna wrote:
I don't use Mail. I login to my e-mail directly online (if it is working) so Mail is not my problem. My 15" MacBook Pro is new out of the box with SL as a 2009 Christmas present.

If that's the case you should immediately if at all possible try your Mac on the wireless network at your local Apple Store and/or make an appointment with the Genius Bar at your local store.

You have a warranty, and your machine is new enough that there shouldn't be issues out of the box and they should be promptly addressed if you do.

Note also that unless it was a custom-ordered configuration, if worse comes to worse:

Items purchased at the Apple Online Store between October 31, 2009 and December 24, 2009, may be returned through January 9, 2010. Please note that all other terms and conditions provided in the Apple Online Store Sales and Refunds Policy are still applicable with respect to such items purchased, including the assessment of a 10% restocking fee on any open box item. All purchases made after December 24, 2009 are subject to the standard Apple Online Store Sales and Refunds Policy, which requires returns to be made within 14 calendar days of the date of receipt.

I suspect, but do not know for sure, that the policy is similar for sales made through Apple's retail locations.

I have the macbook pro 15" purchased snow leopard and now my wifi drops continuously. I find it unfortunate that there is 30 pages of discussion on this issue and the issue is still considered not answered. I've done a clean install, and most of the other suggested fixes. I am at the point now of purchasing the new router as suggested by a couple of folks earlier in the forum. APPLE where are you on this? I continue to be loyal to Apple but this is more than frustrating.