This discussion is locked
-
All replies
-
Helpful answers
first
Previous
Page
3
of 4
last
Next
-
Nov 21, 2009 7:33 AM in response to LCallerby Hobbes2424,I'm having the same exact issue everyone else is having except I'm using an Airport Extreme instead of some other router. After a while my airport on my MBP will just stop responding, sometimes by beachballing the entire menu bar or just disconnecting and never connecting/finding any networks again until I restart. I'm not really sure what I should do to fix this. I'm not running any security on the router so I don't bother with WEP or WPA. Any suggestions? -
Nov 21, 2009 3:19 PM in response to Hobbes2424by james.wilfong,Hobbes2424:
Have you attempted to change the router channel. It may be set to automatic. If you have other wifi in your area it may be intruding the signal, i set mine to 11, its an off channel and no interruption from sorrounding wifi. I have seen threads about manual dns set up. You may want to follow up on that, my issue was very relivent to yours and its no longer an issue with changing the channel up. I keep a solid connection. -
Nov 21, 2009 9:27 PM in response to LCallerby Buzz Lightgear,Hey LCallerNo it's all airport i don't have an never had a Vodafone card on this machine. I'm wondering if that's come over from a time machine backup of my last machine..
Yes Sir you are correct about TM.
+Only use your Time Machine backup to restore your system to the computer that is the source of the backup. If you want to use your backup to transfer your information to a new computer, use Migration Assistant.+
After looking at your post of your console log, I think it's best to start over & reinstall SL then use MA to restore your stuff. -
Nov 21, 2009 10:45 PM in response to james.wilfongby Hobbes2424,The router itself is fine. Every other device that's wireless is unaffected by this and can access the internet without any trouble. The router is not the problem, it's Snow Leopard or my MBP's hardware that is defective/dying. -
Nov 21, 2009 11:12 PM in response to Hobbes2424by Buzz Lightgear,The router is not the problem, it's Snow Leopard or my MBP's hardware that is defective/dying.
SL relies on the hardware configuration for network connections so I think the MBP's hardware is configured with the draft of 802.11n & needs to be updated.
Use this link to check the MBP's WiFi & see if 802.11n is enabled. http://support.apple.com/kb/HT2447
If 802.11n is enabled then delete the old connection then set it up again.
If 802.11n is disabled then search Apples Downloads for the patch & apply it.
If the problem is persistent, replace the hardware. -
Nov 22, 2009 6:41 AM in response to Buzz Lightgearby Hobbes2424,N has been enabled for a couple years now and it's never had this "killing the airport until restart" issue . It doesn't happen every day at all either. It's sporadic and I can't seem to recreate the issue on my own. I have a feeling it's when there's a lot of data transfer for a long period of time. I'll try it out again later I suppose but why would that happen? I also get this in the console around the time it stops working.
kernel ntpd[26] sendto(17.151.16.22) (fd=26): No route to host
kernel AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
The first one of course being the time server and the second showing that there's no data being transferred via ethernet? I'm not even using that connection so I disabled it in the network prefs. I'm not sure why that popped up.. But basically when it occurs, 2 things can happen: everything stops responding on the menu bar (beach balling, etc.) so I'm forced to hard restart OR the airport will drop the connection and won't connect to any network until restart.
As far as I'm concerned the configuration of both the router and the MBP are normal and fine. I think it's more of a hardware issue but I'm not sure. I honestly don't know what to do at this point. -
Nov 22, 2009 10:23 AM in response to Hobbes2424by William Kucharski,Hobbes2424 wrote:
kernel AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
This one specifically states that your router has requested that your machine disassociate from it due to inactivity.
Driver issue? Router firmware issue? Unknown. -
Nov 22, 2009 12:01 PM in response to William Kucharskiby Hobbes2424,en1 is the ethernet port, isn't it? -
Nov 22, 2009 3:04 PM in response to Hobbes2424by Buzz Lightgear,en1 is the ethernet port, isn't it?
WiFi is an extension of the Ethernet Protocols. -
Nov 22, 2009 3:54 PM in response to Hobbes2424by Buzz Lightgear,I'm not even using that connection so I disabled it in the network prefs.
This should solve your issue because the WiFi (en1) was competing with the wired Ethernet (en0). IMO: Only enable WiFi when needed.
Also if there are multiple active network port configurations when you try to connect, Mac OS X tries the one at the top of the list first, and then tries the other port configurations in descending order. -
Dec 2, 2009 3:55 PM in response to Buzz Lightgearby RSully,Its been a while since this thread has been updated I believe, however I have a MacMini that has this same issue.
I'm using WPA and I have several other devices on my network. I noticed this issue sometime after my Snow Leopard update. -
Dec 2, 2009 7:15 PM in response to LCallerby retiredatlast,Have same problem since upgrade from 10.6.1 to 10.6.2. Airport suddenly is not connected. Thought it might be the Airport Extreme so changed it out to a Linksys - did not help so was not router I assume. Have checked iPhone when this happens and it still is connected to router. It might be up for a couple hours or it might do it repeatably every few minutes. Sometimes have to restart to get it back, sometimes wait a bit. Selecting connect from the Airport menu seldom works immediately after it drops but again does some times if I wait awhile. -
Dec 28, 2009 10:02 AM in response to LCallerby effemmeffe,Same problem here.
I only have wifi network and it's without any security (no WPA no WEP, nothing).
After the update to SL the airport keeps disconnecting from the wifi signal with the message:
AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
Macbook unibody early 2009
Snow Leopard 10.6.2
The wifi is 2.4 GHz (B+G) on channel 11 from a Sitecom Mimo XR router.
How can I change this annoying behaviour? -
Dec 29, 2009 7:12 PM in response to LCallerby giobien,my iMac MB325 2.8 keeps on crashing WLan connection even though it is on WPA2 already......
it is getting annoying day after day -
Dec 30, 2009 7:50 AM in response to giobienby AndrewRennie,I'm also having a similar problem. I have gone home to my parent's house for Christmas and my wifi connection just drops out after a while and then Airport says it can't find any networks at all. I have had no problems with any other wifi networks at all. My wife and brother who are also using Macs have no problems and my other family who are running PCs are having no problems. When I try to search for networks it just says that it is timing out.
I have tried turning Airport off and then on and it doesn't help. I have tried restarting the Mac and it doesn't help. I have tried logging into the Guest account and it still has the same problems. I also wiped the saved networks list in Network Preferences and even deleted the Airport preferences file all to no avail.
I am running Snow Leopard 10.6.2 on a September 2006 MacBook and the router is made by 3Com and has WPA security.