WRT610n dropping connection thread

This is the problem we see the most on different forums.
People report that using both bands with some heavy traffic make the unit to drop connections.  Yet the heat is suspected and some have managed to get rid of that problem by allowing the unit to run cooler.
If you are experiencing dropping connections, can you try to find a way to cool the unit (without voiding the warranty) and report if you still experience the problem?  Maybe a fan blowing air directly on the unit.
This is a brand new router and may have not been fully tested with large tranfer on both bands simultanously where heat is more susceptible to occur with the CPU running non-stop.

I posted my experiences in a few other forums, but since this is the official Linksys forum I'll post here, too.
I got my WRT610N a few weeks ago, primarily to use the 5GHz 802.11n radio to stream 1080p HD content to an HTPC. The initial setup was easy, as I'm an IT consultant and have had my fair share of experience with consumer routers such as this.
After about two weeks of near perfect functionality, my router suddenly started dropping the wireless connection every time I tried to stream HD content or do a significant file transfer that lasted over an extended period of time. Because the HTPC was actively streaming the HD content real-time, there was constant 2-3MB/sec activity -- I was able to get halfway through a movie before I started getting incessant dropped connections. I tried upgrading to the latest Build 18 firmware, but did not see any improvement.
In a room with ambient temperatures in the high 70's, I felt the router with my hand and found that it was quite hot -- the bottom especially, was clearly hotter than it should have been. After fumbling around with different configuration settings (disabling WMM, etc.) I eventually found that completely disabling the 2.4GHz radio partially alleviated the problem. However, on a particularly hot Summer day the problem happened to me again, even with the 2.4GHz radio disabled.
I had read countless posts of people with the same problems -- despite multiple hours of telephone calls with the highest level of tech support, the Linksys people were unable to help to solve the problem. Which is pretty understandable, really, seeing that I believe this to mainly be a hardware design problem where the case simply doesn't have enough airflow to effectively cool the dual radios.
Anyways, since I'm technically inclined, I decided to fix the problem myself. I took apart the router (which voided the warranty.. don't do this!) and installed some slim-profile heat sinks on the metal shields that covered the hottest chips on the board. I also replaced the only heat sink installed at the factory with a larger one. I installed all of the heat sinks with Arctic Silver Alumina Adhesive Thermal Paste.
Additionally, I fashioned up a base stand with a quiet 120mm fan positioned directly under the router, forcing air up through the holes in the bottom of the router, around the heat sinks installed over the hot chips, and out of the top vents near the antennas. This provided decent air circulation within the unit.
Afterward, I setup a stress test to run overnight. One client connected via the 5GHz radio, and was queued to transfer around 100GB at ~10MB/sec, without stop. Another client connected via the 2.4GHz radio, and was queued to transfer 50GB. A final client connected via the GigE switch, and was queued to transfer 180GB at around ~65MB/sec.
I woke up in the morning and found that all transfers had completed successfully without a single hitch the entire night. I touched the router with my hand about an hour after the start of the test, and found that it was not hot at all -- in fact it was barely warm to the touch.
Anyways, that was last week and since then I've streamed multiple movies and done multiple file transfers without any hitches. I'm not telling people to void their warranty's, and I'm not responsible if you try this yourself and screw up your router. I'm just providing evidence that strongly supports my hypothesis that the WRT610N connection drop issues are due to overheating, and can't simply be fixed with firmware updates.
To Linksys: I suggest you look into a better method of cooling this router. On a slim device, such as the WRT610N, which can't be stood on its side for better airflow, and which runs dual wireless radios simultaneously, a single, small heat sink on one of the chips just doesn't cut it. Also, if you do a hardware revision and want to send me a new one for helping out, let me know .
Here are some pics of the base stand I made. I didn't take pics of the heat sinks and it's probably better I don't post that here anyways...
https://trihfh.s3.amazonaws.com/wrt610n/IMG_1549.JPG
https://trihfh.s3.amazonaws.com/wrt610n/IMG_1548.JPG
https://trihfh.s3.amazonaws.com/wrt610n/IMG_1547.JPG
https://trihfh.s3.amazonaws.com/wrt610n/IMG_1546.JPG
Will
Message Edited by trihfh on 09-11-2008 11:03 PM

Similar Messages

  • WRT610N drops connection constantly

    I've reinstalled the firmware, removed the cordless phones, searched this forum and nothing is different. The router drops the wireless connections very frequently. Running 1 wireless pc, 2 wireless macs, 2 iphones and 1 wired PC. Both PC's running Vista, 1 mac on Leopard, the other on Tiger. iPhones are 2.2. Any suggestions before I go find another router that works?

    yea, I can understand how you feel...trust me, I had my moments where I was close to throwing it out the window.
    if your situation is similar to mine, where you are currently running wpa2 aes+tkip, switch it to only AES and see how it goes

  • WRT610N Dropping connection after sustained VPN???

    Hi everyone,
    First time posting on the forums.
    The setup:
    I have a WRT610N router about 5 months old.  Hardwired to it is an iMac with the latest OS X, Mac Mini with latest OS X, Xbox 360 and Bell Express Vu satellite box (for remote PVRing).  Wirelessly I also have a number of devices
    - iPad
    - iphone 4
    - iphone 3G
    - Airport Express
    - Dell Laptop
    I use the Dell Laptop running XP SP3 for work and I am basically VPNed anytime I am working on it.  I find that if I turn the DELL off while VPNed/hibernate while VPNed, or if I leave the house with the VPN on, I lose the capability for any of the computers to go on the internet.
    I have done some basic troubleshooting, and can confirm that the problem exists at the router level and not my internet modem (all 4 lights stay solid with the 5th one blinking -- Shaw is provider).  If I reset the router, the problem goes away.
    I am 99.5% sure this has something to do with my Dell Laptop and the VPN but I don't know how to troubleshoot because I haven't been able to determine a causal relationship between the shutdown/VPN behaviour and this immediately happening.  I usually notice it way later.
    So, I am hoping someone...anyone can help me with suggestions.  I would consider myself fairly tech savy, but have not really had to troubleshoot this type of router issue before beyond some basic DNS/Mac Address settings and Port forwarding.
    I hope my question makes sense.  Let me know if you need any logs or details.
    Thanks!
    ~Rishi
    Calgary, AB

    I wish I could explain this better or have a cause defined.
    I do know that this problem happens during the week (ie. when I am working on that dell laptop and am using VPN all-day every day).
    It doesn't happen on the weekends ever, hence the thought that VPN issues are causing it.
    I am wiling to try ANY steps to get the diagnosis going...

  • 10.7.3 MBP Wifi Problem - Endless Timeouts & Dropped connections

    I've been reading around here a bit already and so I know many other people are having Wifi issues with Lion, but given that there are so many discussions and so many pages of talk, it's hard to go through it all, and using the search I haven't found anything that's quite similar to what I'm experiencing, so I'm starting a new topic...
    Basically, I've got a late 2006 MacBook Pro, installed 10.7.1 (form 10.6.8) on in back in Aug 2011 and everything seemed to be fine. I updated to 10.7.2 sometime in Jan and still didn't notice any issues, but wasn't using Wifi at all at the time.
    Then in Feb I moved and started using wifi (with a Cisco N router), and noticed that often, the system would not automatically reconnect to the network after waking up from sleep. Just selecting the network manually worked on the first try every time though, so it wasn't so bad.
    At the end of April, I finally got around to installing the 10.7.3 update. I read it was supposed to fix wifi issues and so was looking forward to it. It installed fine and didn't seem to cause any problems...
    2 days later I moved again (to India), and all **** broke loose... Now, I can rarely connect to wifi (a Beetel G router, configed with WPA). Around 25% of the time, the network won't show up in the list (despite being a clear 5ft from the base station), and when it does show up, 95% of the time I get a "connection timeout" error - often immeadiately, but sometimes it takes about 10sec to respond. On the same network, 2 Win 7 Dells and an iPad 1 all work flawlessly - it's not the router...
    One the occasions that I am able to connect, it usually works fine, but if I put the computer to sleep and wake up again, there's no guarentee that the connection will work again - it's back to the lottery. And sometimes even when it's connected, the wifi stays (according to the menu indicator) but the internet connection disappears (to the point I can't even ping the router - 100% packet loss, let alone any internet server)
    I've tried zapping everything I can think of (PRAM, SMC), repairing permissions, clearing the remembered networks from the System Prefs, deleting old Locations and creating new ones etc. I have a clean install of 10.7.1 that I booted off of, but it still had the same issues!
    Here's the Wifi output from System Profiler (trying to use "Home Network"):
    Software Versions:
      CoreWLAN:          2.1.2 (212.1)
      CoreWLANKit:          1.0.2 (102.2)
      Menu Extra:          7.0.2 (702.1)
      configd plug-in:          7.1.2 (712.1)
      System Profiler:          7.0 (700.3)
      IO80211 Family:          4.1.2 (412.2)
      WiFi Diagnostics:          1.0.1 (101.1)
      AirPort Utility:          6.0 (600.92)
      Interfaces:
    en1:
      Card Type:          AirPort Extreme
      Firmware Version:          Atheros 5416: 2.1.14.9
      MAC Address:          00:XX:XX:XX:XX
      Locale:          FCC
      Country Code:          IN
      Supported PHY Modes:          802.11 a/b/g/n
      Supported Channels:          1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 149, 153, 157, 161, 165
      Status:          Not Associated
      Local Wi-Fi Networks:
    Home Network:
      PHY Mode:          802.11g
      BSSID:          80:a1:d7:4a:d0:02
      Channel:          1
      Network Type:          Infrastructure
      Security:          WPA Personal
      Signal / Noise:          -77 dBm / -96 dBm
    MGMNT:
      PHY Mode:          802.11g
      BSSID:          80:a1:d7:4a:d0:03
      Channel:          1
      Network Type:          Infrastructure
      Security:          WEP
      Signal / Noise:          -77 dBm / -96 dBm
    RC:
      PHY Mode:          802.11g
      BSSID:          00:1e:40:57:67:61
      Channel:          6
      Network Type:          Infrastructure
      Security:          WPA Personal
      Signal / Noise:          -97 dBm / -96 dBm
    Vivek:
      PHY Mode:          802.11g
      BSSID:          00:24:b2:94:ea:06
      Channel:          11
      Network Type:          Infrastructure
      Security:          WEP
      Signal / Noise:          -94 dBm / -96 dBm
    nischai:
      PHY Mode:          802.11n
      BSSID:          58:6d:8f:c3:ea:2a
      Channel:          6
      Network Type:          Infrastructure
      Security:          WPA2 Personal
      Signal / Noise:          -90 dBm / -96 dBm
    noor:
      PHY Mode:          802.11g
      BSSID:          00:24:b2:7e:26:72
      Channel:          11
      Network Type:          Infrastructure
      Security:          WPA Personal
      Signal / Noise:          -90 dBm / -96 dBm
    One thread here I read had someone suggesting to run the Airport debugger in Terminal and posting the output - here's the results:
    Sat May  5 09:52:00.823 <kernel> IO80211ScanManager::startScan: Broadcast scan request received from pid 622 ().
    Sat May  5 09:52:00.824 <kernel> IO80211ScanManager::startScan: Initiating scan.
    Sat May  5 09:52:00.824 <kernel> __ieee80211_newstate: INIT -> SCAN (arg 0xffffffff)
    Sat May  5 09:52:00.824 <kernel> ieee80211_check_scan: active scan, duration 24000, desired mode auto, append, nopick
    Sat May  5 09:52:00.824 <kernel> ieee80211_start_scan: active scan, duration 24000, desired mode auto, append, nopick
    Sat May  5 09:52:00.824 <kernel> scan_next: chan   1g ->   1g [active, dwell min 8 max 8]
    Sat May  5 09:52:00.865 <kernel> [80:a1:d7:4a:d0:02] new beacon on chan 1 (bss chan 1) "Home Network"
    Sat May  5 09:52:00.865 <kernel> [80:a1:d7:4a:d0:02] caps 0x411 bintval 100 erp 0x4 
    Sat May  5 09:52:00.873 <kernel> [80:a1:d7:4a:d0:03] new beacon on chan 1 (bss chan 1) "MGMNT"
    Sat May  5 09:52:00.873 <kernel> [80:a1:d7:4a:d0:03] caps 0x411 bintval 100 erp 0x4 
    Sat May  5 09:52:00.909 <kernel> scan_next: chan   1g ->   6g [active, dwell min 8 max 8]
    Sat May  5 09:52:00.917 <kernel> [58:6d:8f:c3:ea:2a] new probe_resp on chan 6 (bss chan 6) "nischai"
    Sat May  5 09:52:00.919 <kernel> [58:6d:8f:c3:ea:2a] caps 0x411 bintval 100 erp 0x4 
    Sat May  5 09:52:00.920 <kernel> [58:6d:8f:c3:ea:2a] new probe_resp on chan 6 (bss chan 6) "nischai"
    Sat May  5 09:52:00.920 <kernel> [58:6d:8f:c3:ea:2a] caps 0x411 bintval 100 erp 0x4 
    Sat May  5 09:52:00.928 <kernel> [58:6d:8f:c3:ea:2a] new probe_resp on chan 6 (bss chan 6) "nischai"
    Sat May  5 09:52:00.928 <kernel> [58:6d:8f:c3:ea:2a] caps 0x411 bintval 100 erp 0x4 
    Sat May  5 09:52:00.992 <kernel> scan_next: chan   6g ->  11g [active, dwell min 8 max 8]
    Sat May  5 09:52:01.47  <kernel> [00:24:b2:7e:26:72] new beacon on chan 11 (bss chan 11) "noor"
    Sat May  5 09:52:01.47  <kernel> [00:24:b2:7e:26:72] caps 0x411 bintval 100 erp 0x0 
    Sat May  5 09:52:01.75  <kernel> scan_next: chan  11g ->   7g [active, dwell min 8 max 8]
    Sat May  5 09:52:01.158 <kernel> scan_next: chan   7g ->  13g [active, dwell min 8 max 8]
    Sat May  5 09:52:01.241 <kernel> scan_next: chan  13g ->  52a [passive, dwell min 8 max 8]
    Sat May  5 09:52:01.327 <kernel> scan_next: chan  52a ->  56a [passive, dwell min 8 max 8]
    Sat May  5 09:52:01.409 <kernel> scan_next: chan  56a ->  60a [passive, dwell min 8 max 8]
    Sat May  5 09:52:01.492 <kernel> scan_next: chan  60a ->  64a [passive, dwell min 8 max 8]
    Sat May  5 09:52:01.575 <kernel> scan_next: chan  64a ->  36a [active, dwell min 8 max 8]
    Sat May  5 09:52:01.657 <kernel> scan_next: chan  36a ->  40a [active, dwell min 8 max 8]
    Sat May  5 09:52:01.741 <kernel> scan_next: chan  40a ->  44a [active, dwell min 8 max 8]
    Sat May  5 09:52:01.823 <kernel> scan_next: chan  44a ->  48a [active, dwell min 8 max 8]
    Sat May  5 09:52:01.906 <kernel> scan_next: chan  48a ->   2g [active, dwell min 8 max 8]
    Sat May  5 09:52:01.920 <kernel> [04:4f:aa:b4:dc:f9] new beacon on chan 2 (bss chan 2) ""
    Sat May  5 09:52:01.920 <kernel> [04:4f:aa:b4:dc:f9] caps 0x431 bintval 100 erp 0x0 
    Sat May  5 09:52:01.992 <kernel> scan_next: chan   2g ->   3g [active, dwell min 8 max 8]
    Sat May  5 09:52:02.74  <kernel> scan_next: chan   3g ->   4g [active, dwell min 8 max 8]
    Sat May  5 09:52:02.157 <kernel> scan_next: chan   4g ->   5g [active, dwell min 8 max 8]
    Sat May  5 09:52:02.239 <kernel> scan_next: chan   5g ->   8g [active, dwell min 8 max 8]
    Sat May  5 09:52:02.321 <kernel> scan_next: chan   8g ->   9g [active, dwell min 8 max 8]
    Sat May  5 09:52:02.388 <kernel> [00:26:15:61:4c:87] new beacon on chan 9 (bss chan 9) "BSNL_AP"
    Sat May  5 09:52:02.388 <kernel> [00:26:15:61:4c:87] caps 0x431 bintval 100 erp 0x0  country info  49 4e 49 01 0d 14
    Sat May  5 09:52:02.403 <kernel> scan_next: chan   9g ->  10g [active, dwell min 8 max 8]
    Sat May  5 09:52:02.486 <kernel> scan_next: chan  10g ->  12g [active, dwell min 8 max 8]
    Sat May  5 09:52:02.569 <kernel> scan_next: chan  12g -> 149a [active, dwell min 8 max 8]
    Sat May  5 09:52:02.655 <kernel> scan_next: chan 149a -> 153a [active, dwell min 8 max 8]
    Sat May  5 09:52:02.738 <kernel> scan_next: chan 153a -> 157a [active, dwell min 8 max 8]
    Sat May  5 09:52:02.821 <kernel> scan_next: chan 157a -> 161a [active, dwell min 8 max 8]
    Sat May  5 09:52:02.903 <kernel> scan_next: chan 161a -> 165a [active, dwell min 8 max 8]
    Sat May  5 09:52:02.991 <kernel> scan_next: done, [ticks 32630, dwell min 8 scanend 56413]
    Sat May  5 09:52:02.993 <kernel> __ieee80211_newstate: SCAN -> INIT (arg 0xffffffff)
    Sat May  5 09:52:02.993 <kernel> ieee80211_init_node[1132] old_auth 5
    Sat May  5 09:52:02.994 <kernel> IO80211ScanManager::getScanResult: All scan results returned for pid 622.
    Sat May  5 09:52:05.765 <airportd[804]> _handleNewMessage: Received XPC message, event = ASSOC_EVENT, pid = 622
    Sat May  5 09:52:05.766 <airportd[804]> associate: INFO: airportd associate: network=<CWNetwork: 0x7f9fd8c11fc0> [ssid=Home Network, bssid=80:a1:d7:4a:d0:02, security=WPA Personal, rssi=-76, channel=<CWChannel: 0x7f9fd8c185b0> [channelNumber=1(2GHz), channelWidth={20MHz}], ibss=0], is8021X=0, remember=1
    Sat May  5 09:52:05.781 <airportd[804]> associate: INFO: Checking if admin authorization is required
    Sat May  5 09:52:05.802 <kernel> __ieee80211_newstate: INIT -> SCAN (arg 0x0)
    Sat May  5 09:52:05.802 <kernel> ieee80211_check_scan: active scan, duration 24000, desired mode auto, append
    Sat May  5 09:52:05.802 <kernel> ieee80211_check_scan: check scan cache
    Sat May  5 09:52:05.802 <kernel>  macaddr          bssid         chan  rssi rate flag  wep  essid
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.802 <kernel> 
    Sat May  5 09:52:05.807 <kernel> 
    Sat May  5 09:52:05.807 <kernel> ieee80211_init_node[1132] old_auth 5
    Sat May  5 09:52:05.807 <kernel> __ieee80211_newstate: SCAN -> JOIN (arg 0x0)
    Sat May  5 09:52:05.812 <kernel> __ieee80211_newstate: JOIN -> AUTH (arg 0xc0)
    Sat May  5 09:52:05.813 <kernel> ieee80211_cancel_scan: cancel active scan
    Sat May  5 09:52:05.813 <kernel> scan_next: done, [ticks 32912, dwell min 8 scanend 56413]
    Sat May  5 09:52:05.813 <kernel> parseWPAIE: groupCipherType = 3 pairwiseCipherType = 3 authSel = 2
    Sat May  5 09:52:05.813 <kernel> initWithInterfaceAndIE: _myMacAddress 00:17:f2:e6:81:a1
    Sat May  5 09:52:05.813 <kernel> setPMK: PMK SET!
    Sat May  5 09:52:05.815 <kernel> ieee80211_tx_timeout: state AUTH
    Sat May  5 09:52:05.815 <kernel> [80:a1:d7:4a:d0:02] ieee80211_scan_assoc_fail: reason 1
    Sat May  5 09:52:05.815 <kernel> [80:a1:d7:4a:d0:02] sta_assoc_fail: reason 1
    Sat May  5 09:52:05.815
    Sat May  5 09:52:05.815 <kernel> __ieee80211_newstate: AUTH -> SCAN (arg 0x1)
    Sat May  5 09:52:05.815 <kernel> [80:a1:d7:4a:d0:02] ieee80211_scan_assoc_fail: reason 1
    Sat May  5 09:52:05.816 <kernel> ieee80211_init_node[1132] old_auth 5
    Sat May  5 09:52:05.816 <kernel> ieee80211_check_scan: active scan, duration 24000, desired mode auto, append
    Sat May  5 09:52:05.816 <kernel> ieee80211_check_scan: check scan cache
    Sat May  5 09:52:05.816 <kernel>  macaddr          bssid         chan  rssi rate flag  wep  essid
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> 
    Sat May  5 09:52:05.816 <kernel> ieee80211_start_scan: active scan, duration 24000, desired mode auto, append
    Sat May  5 09:52:05.816 <kernel> scan_next: chan   1g ->   1g [active, dwell min 8 max 8]
    Sat May  5 09:52:05.834 <kernel> ieee80211_cancel_scan: cancel active scan
    Sat May  5 09:52:05.834 <kernel> __ieee80211_newstate: SCAN -> INIT (arg 0xffffffff)
    Sat May  5 09:52:05.834 <kernel> ieee80211_init_node[1132] old_auth 5
    Sat May  5 09:52:05.835 <kernel> en1: Terminating supplicant.
    Sat May  5 09:52:05.835 <kernel> RSNSupplicant: Releasing authenticator for 00:00:00:00:00:00
    Sat May  5 09:52:05.835 <airportd[804]> associate: Apple80211Associate2() failed with error -3905
    Sat May  5 09:52:21.354 <kernel> IO80211ScanManager::cachePurge: clearEntries[0] Firing!
    Sat May  5 09:52:21.354 <kernel> IO80211ScanManager::cachePurge: Rescheduling in 14 seconds.
    Sat May  5 09:52:35.354 <kernel> IO80211ScanManager::cachePurge: clearEntries[0] Firing!
    Sat May  5 09:52:35.354 <kernel> IO80211ScanManager::cachePurge: NOT Rescheduling.
    I'm pretty savy with computers and have dealt with all kinds of stuff before, but this one is beyond me, and is really annoying! I konw my machine is old, but it was totally useable up until these Wifi issues, and now wifi is basically useless.
    From what I've read, it seems like its a driver issue with the Atheros card in my machine, but most people seem to be complaining about dropped connections (mine rarely drops) rather than timeout connection issues. I've also never had the "hardware not found" issue that many people have, so I think this is something different.
    Anyone out there have any advice? I'm getting close to losing it with wifi since the update!

    Sorry - to add:
    I don't think it's a question of WPA vs. WPA2, or even channel number - I have 2 identical routers here and neither work (both default to WPA Ch 11) but I changed one to WPA2, new SSID, various channels and still had the same problems.
    Another thing to note that should be irrelevant, but who knows: the Firewire controller on my machine died back in Fall 2010 - to the point where the system won't start-up unless I remove the IOFirewire***.kext from /System/Library/Extensions , and as soon as I do that, it works flawlessly (minus Firewire). It meant I had a **** of a time installing Lion becuase I can't boot off the Recovery Partition (which has the drivers baked into it), but by cloneing my HD, installing Lion onto the clone via a borrowed machine, removing the .kext's and cloning back, I got it on and everything seems to be fine otherwise... I posted about that problem before, but never got any answers. And it wasn't just me, my father has a late 2007 MBP and the same firewire issue happened to his within 5 days of mine (not a power spike - I think it was shortly after some system update if I remember correctly).

  • Issue with AFP server dropping connections on 10.8.5 server 2.2.2

    We are having issues with users getting dropped from their AFP server shares.
    These issues did not start happening until we upgraded to 10.8.5 and server 2.2.2
    the first symptoms were an occasional user would lose his / her active connection while copying files. They were unable to disconnect from the network shares without physically disconnecting the LAN or disabling the network on their system. Once the connection was removed they could reconnect to the network and establish their AFP shares again.
    However this his escalated to every user losing connections to their AFP shares at the same time.
    The server has no AFP error in the AFP error log however we are getting diskutil crash reports at around the same time. (See Below)
    The server has
    smalltree 1x6 8254 with latest drivers supporting a LACP bonded 6 pair connecting to an edgecore (LACP configured)switch.
    small tree 10Gb card directly connected to an edit station.
    onboard ethernet connected to switch in support of DHCP & DNS. (previous version of server would not see the bonded pair)
    Two Accusys A12S2's
    (we did not have this dropping connection issue before the upgrade to server 2.2.2 and OSX 10.8.5)
    Users connected to any network connection to the server appear to be affected when the AFP shares are disconnected. Direcet connect, onboard ethernet port and Bonded pair connections)
    diskutil verifies all shared drives appear to be ok. (All Green)
    SYSTEM LOG
    Feb 23 11:15:44 doghouse.local diskutil[1067]: -[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8
    Feb 23 11:15:44 doghouse.local diskutil[1067]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
              *** First throw call stack:
                        0   CoreFoundation                      0x00007fff91b2bb06 __exceptionPreprocess + 198
                        1   libobjc.A.dylib                     0x00007fff901403f0 objc_exception_throw + 43
                        2   CoreFoundation                      0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
                        3   CoreFoundation                      0x00007fff91b1a02e ___forwarding___ + 414
                        4   CoreFoundation                      0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
                        5   diskutil                            0x000000010c1eb550 diskutil + 83280
                        6   diskutil                            0x000000010c1ea0af diskutil + 77999
                        7   diskutil                            0x000000010c1e7abe diskutil + 68286
                        8   diskutil                            0x000000010c1dd0ef diskutil + 24815
                        9   diskutil                            0x000000010c1e5161 diskutil + 57697
                        10  Foundation                          0x00007fff8d29dd05 __NSFireDelayedPerform + 358
                        11  CoreFoundation                      0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
                        12  CoreFoundation                      0x00007fff91ae831d __CFRunLoopDoTimer + 557
                        13  CoreFoundation                      0x00007fff91acdad9 __CFRunLoopRun + 1529
                        14  CoreFoundation                      0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
                        15  Foundation                          0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
                        16  Foundation                          0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
                        17  diskutil                            0x000000010c1e5126 diskutil + 57638
                        18  diskutil                            0x000000010c1e51cd diskutil + 57805
                        19  libdyld.dylib                       0x00007fff86bf87e1 start + 0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1061] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544_doghouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-22-164711_dogh ouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local diskutil[1071]: -[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1067] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544-1_doghouse.crash
    Feb 23 11:15:44 doghouse.local diskutil[1071]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
              *** First throw call stack:
                        0   CoreFoundation                      0x00007fff91b2bb06 __exceptionPreprocess + 198
                        1   libobjc.A.dylib                     0x00007fff901403f0 objc_exception_throw + 43
                        2   CoreFoundation                      0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
                        3   CoreFoundation                      0x00007fff91b1a02e ___forwarding___ + 414
                        4   CoreFoundation                      0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
                        5   diskutil                            0x0000000100e49550 diskutil + 83280
                        6   diskutil                            0x0000000100e480af diskutil + 77999
                        7   diskutil                            0x0000000100e45abe diskutil + 68286
                        8   diskutil                            0x0000000100e3b0ef diskutil + 24815
                        9   diskutil                            0x0000000100e43161 diskutil + 57697
                        10  Foundation                          0x00007fff8d29dd05 __NSFireDelayedPerform + 358
                        11  CoreFoundation                      0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
                        12  CoreFoundation                      0x00007fff91ae831d __CFRunLoopDoTimer + 557
                        13  CoreFoundation                      0x00007fff91acdad9 __CFRunLoopRun + 1529
                        14  CoreFoundation                      0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
                        15  Foundation                          0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
                        16  Foundation                          0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
                        17  diskutil                            0x0000000100e43126 diskutil + 57638
                        18  diskutil                            0x0000000100e431cd diskutil + 57805
                        19  libdyld.dylib                       0x00007fff86bf87e1 start + 0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-22-164712_dogh ouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Saved crash report for diskutil[1071] version 680 to /Library/Logs/DiagnosticReports/diskutil_2014-02-23-111544-2_doghouse.crash
    Feb 23 11:15:44 doghouse.local ReportCrash[1064]: Removing excessive log: file://localhost/Library/Logs/DiagnosticReports/diskutil_2014-02-23-093307_dogh ouse.crash
    diskutil crash report
    Process:         diskutil [1061]
    Path:            /usr/sbin/diskutil
    Identifier:      diskutil
    Version:         680
    Code Type:       X86-64 (Native)
    Parent Process:  sh [1060]
    User ID:         0
    Date/Time:       2014-02-23 11:15:43.719 -0800
    OS Version:      Mac OS X 10.8.5 (12F45)
    Report Version:  10
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFConstantString getBytes:length:]: unrecognized selector sent to instance 0x7fff7628bbe8'
    terminate called throwing an exception
    abort() called
    Application Specific Backtrace 1:
    0   CoreFoundation                      0x00007fff91b2bb06 __exceptionPreprocess + 198
    1   libobjc.A.dylib                     0x00007fff901403f0 objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff91bc240a -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
    3   CoreFoundation                      0x00007fff91b1a02e ___forwarding___ + 414
    4   CoreFoundation                      0x00007fff91b19e18 _CF_forwarding_prep_0 + 232
    5   diskutil                            0x000000010124a550 diskutil + 83280
    6   diskutil                            0x00000001012490af diskutil + 77999
    7   diskutil                            0x0000000101246abe diskutil + 68286
    8   diskutil                            0x000000010123c0ef diskutil + 24815
    9   diskutil                            0x0000000101244161 diskutil + 57697
    10  Foundation                          0x00007fff8d29dd05 __NSFireDelayedPerform + 358
    11  CoreFoundation                      0x00007fff91ae8804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
    12  CoreFoundation                      0x00007fff91ae831d __CFRunLoopDoTimer + 557
    13  CoreFoundation                      0x00007fff91acdad9 __CFRunLoopRun + 1529
    14  CoreFoundation                      0x00007fff91acd0e2 CFRunLoopRunSpecific + 290
    15  Foundation                          0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
    16  Foundation                          0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
    17  diskutil                            0x0000000101244126 diskutil + 57638
    18  diskutil                            0x00000001012441cd diskutil + 57805
    19  libdyld.dylib                       0x00007fff86bf87e1 start + 0
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib                  0x00007fff86519212 __pthread_kill + 10
    1   libsystem_c.dylib                       0x00007fff8a31ab24 pthread_kill + 90
    2   libsystem_c.dylib                       0x00007fff8a35ef61 abort + 143
    3   libc++abi.dylib                         0x00007fff85dc39eb abort_message + 257
    4   libc++abi.dylib                         0x00007fff85dc139a default_terminate() + 28
    5   libobjc.A.dylib                         0x00007fff90140873 _objc_terminate() + 91
    6   libc++abi.dylib                         0x00007fff85dc13c9 safe_handler_caller(void (*)()) + 8
    7   libc++abi.dylib                         0x00007fff85dc1424 std::terminate() + 16
    8   libc++abi.dylib                         0x00007fff85dc261b __cxa_rethrow + 85
    9   libobjc.A.dylib                         0x00007fff90140575 objc_exception_rethrow + 40
    10  com.apple.CoreFoundation                0x00007fff91acd146 CFRunLoopRunSpecific + 390
    11  com.apple.Foundation                    0x00007fff8d2c57ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
    12  com.apple.Foundation                    0x00007fff8d25e1aa -[NSRunLoop(NSRunLoop) run] + 74
    13  diskutil                                0x0000000101244126 0x101236000 + 57638
    14  diskutil                                0x00000001012441cd 0x101236000 + 57805
    15  libdyld.dylib                           0x00007fff86bf87e1 start + 1
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x00007fff86519d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff8a0dddea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib                       0x00007fff8a0dd9ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff865196d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8a31bf1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff8a31bce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8a306191 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff865196d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8a31bf1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff8a31bce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8a306191 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff865196d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8a31bf1c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff8a31bce3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff8a306191 start_wqthread + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x0000000000000000  rbx: 0x0000000000000006  rcx: 0x00007fff5e9c9ad8  rdx: 0x0000000000000000
      rdi: 0x0000000000000707  rsi: 0x0000000000000006  rbp: 0x00007fff5e9c9b00  rsp: 0x00007fff5e9c9ad8
       r8: 0x00007fff764be278   r9: 0x00007fff5e9c9ae0  r10: 0x0000000020000000  r11: 0x0000000000000206
      r12: 0x00007fff5e9c9c60  r13: 0x0000000000000001  r14: 0x00007fff764bf180  r15: 0x00007fff5e9c9b40
      rip: 0x00007fff86519212  rfl: 0x0000000000000206  cr2: 0x00007fff764b7ff0
    Logical CPU: 0
    Binary Images:
           0x101236000 -        0x10126efff  diskutil (680) <47174BB8-7EAC-39F7-96F7-99FE93C9CAF3> /usr/sbin/diskutil
        0x7fff60e36000 -     0x7fff60e6a93f  dyld (210.2.3) <6900F2BA-DB48-3B78-B668-58FC0CF6BCB8> /usr/lib/dyld
        0x7fff85d6f000 -     0x7fff85d6ffff  libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
        0x7fff85dc0000 -     0x7fff85de5ff7  libc++abi.dylib (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /usr/lib/libc++abi.dylib
        0x7fff85de6000 -     0x7fff85e4eff7  libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
        0x7fff85e4f000 -     0x7fff85ef5ff7  com.apple.CoreServices.OSServices (557.6 - 557.6) <FFDDD2D8-690D-388F-A48F-4750A792D2CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
        0x7fff85f54000 -     0x7fff85f62ff7  libkxld.dylib (2050.48.12) <B8F7ED1F-CF84-3777-9183-0A1C513DF81F> /usr/lib/system/libkxld.dylib
        0x7fff861de000 -     0x7fff86353ff7  com.apple.CFNetwork (596.5 - 596.5) <22372475-6EF4-3A04-83FC-C061FE4717B3> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
        0x7fff86354000 -     0x7fff863d5fff  com.apple.Metadata (10.7.0 - 707.12) <69E3EEF7-8B7B-3652-8320-B8E885370E56> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
        0x7fff86468000 -     0x7fff86470ff7  libsystem_dnssd.dylib (379.38.1) <BDCB8566-0189-34C0-9634-35ABD3EFE25B> /usr/lib/system/libsystem_dnssd.dylib
        0x7fff86499000 -     0x7fff86506ff7  com.apple.datadetectorscore (4.1 - 269.3) <5775F0DB-87D6-310D-8B03-E2AD729EFB28> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
        0x7fff86507000 -     0x7fff86522ff7  libsystem_kernel.dylib (2050.48.12) <4B7993C3-F62D-3AC1-AF92-414A0D6EED5E> /usr/lib/system/libsystem_kernel.dylib
        0x7fff865b1000 -     0x7fff865b2ff7  libremovefile.dylib (23.2) <6763BC8E-18B8-3AD9-8FFA-B43713A7264F> /usr/lib/system/libremovefile.dylib
        0x7fff86764000 -     0x7fff86769fff  libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
        0x7fff86784000 -     0x7fff86785fff  libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
        0x7fff86bf6000 -     0x7fff86bf9ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8715b000 -     0x7fff8715bfff  com.apple.vecLib (3.8 - vecLib 3.8) <6CBBFDC4-415C-3910-9558-B67176447789> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
        0x7fff871a8000 -     0x7fff87235ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
        0x7fff87236000 -     0x7fff87243fff  libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
        0x7fff872d9000 -     0x7fff87373fff  libvMisc.dylib (380.10) <A7F12764-A94C-36EB-88E0-F826F5AF55B4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
        0x7fff87455000 -     0x7fff87455fff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
        0x7fff87874000 -     0x7fff87947ff7  com.apple.DiscRecording (7.0 - 7000.2.4) <6DCA9535-E276-3D77-BEB3-296B537AA6BB> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
        0x7fff879ab000 -     0x7fff879aefff  libutil.dylib (30) <EF3340B2-9A53-3D5E-B9B4-BDB5EEECC178> /usr/lib/libutil.dylib
        0x7fff87da3000 -     0x7fff87da5ff7  com.apple.EFILogin (2.0 - 2) <51A470D7-1F72-3369-AF0F-AD2340B42C12> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin
        0x7fff880b1000 -     0x7fff880e9fff  libncurses.5.4.dylib (37.3) <68D5B5F5-8252-3F1E-AFF1-C6AFE145DBC1> /usr/lib/libncurses.5.4.dylib
        0x7fff881ed000 -     0x7fff881faff7  com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
        0x7fff88571000 -     0x7fff8859fff7  libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
        0x7fff887e7000 -     0x7fff887e8ff7  libSystem.B.dylib (169.3) <5ED23C27-47AF-3C93-984A-172751CF745A> /usr/lib/libSystem.B.dylib
        0x7fff887e9000 -     0x7fff8883aff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <581BF463-C15A-363B-999A-E830222FA925> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
        0x7fff8883b000 -     0x7fff88b52ff7  com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
        0x7fff88b53000 -     0x7fff88b54ff7  libsystem_sandbox.dylib (220.3) <B739DA63-B675-387A-AD84-412A651143C0> /usr/lib/system/libsystem_sandbox.dylib
        0x7fff88be0000 -     0x7fff88bf3ff7  libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
        0x7fff88dd0000 -     0x7fff88dd1fff  libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
        0x7fff892df000 -     0x7fff892e5fff  libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
        0x7fff892e6000 -     0x7fff89335ff7  libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib
        0x7fff89336000 -     0x7fff89536fff  libicucore.A.dylib (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /usr/lib/libicucore.A.dylib
        0x7fff89537000 -     0x7fff89537fff  libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib
        0x7fff89538000 -     0x7fff89581ff7  com.apple.DiskManagement (5.3.1 - 680) <5438A1FF-B92C-3D28-A8E4-FB41F03144C2> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManag ement
        0x7fff89589000 -     0x7fff895abff7  libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib
        0x7fff895b6000 -     0x7fff895cdfff  com.apple.CFOpenDirectory (10.8 - 151.10) <F7AD9844-559A-366E-8192-BB4FCF9EE7A3> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
        0x7fff895ce000 -     0x7fff895d9fff  libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
        0x7fff8960f000 -     0x7fff89614fff  libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
        0x7fff899f3000 -     0x7fff89a3fff7  libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib
        0x7fff89b9a000 -     0x7fff89b9cff7  libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
        0x7fff89bd8000 -     0x7fff89c09ff7  com.apple.DictionaryServices (1.2 - 184.4) <FB0540FF-5034-3591-A28D-6887FBC220F7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
        0x7fff8a01f000 -     0x7fff8a0afff7  libCoreStorage.dylib (296.18.2) <2FFB6BCA-3033-3AC1-BCE4-ED102DCBECD5> /usr/lib/libCoreStorage.dylib
        0x7fff8a0d9000 -     0x7fff8a0eeff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8a0ef000 -     0x7fff8a11afff  libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
        0x7fff8a2e9000 -     0x7fff8a2f3fff  libcsfde.dylib (296.18.2) <08092C5B-2171-3C1D-A98F-CF499A315DDC> /usr/lib/libcsfde.dylib
        0x7fff8a305000 -     0x7fff8a3d1ff7  libsystem_c.dylib (825.40.1) <543B05AE-CFA5-3EFE-8E58-77225411BA6B> /usr/lib/system/libsystem_c.dylib
        0x7fff8a5c9000 -     0x7fff8a628fff  com.apple.AE (645.6 - 645.6) <44F403C1-660A-3543-AB9C-3902E02F936F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
        0x7fff8a679000 -     0x7fff8a776fff  libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
        0x7fff8a8e3000 -     0x7fff8a9e0ff7  libxml2.2.dylib (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /usr/lib/libxml2.2.dylib
        0x7fff8afa9000 -     0x7fff8afdffff  libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
        0x7fff8afe6000 -     0x7fff8afeefff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff8b2b7000 -     0x7fff8b368fff  com.apple.LaunchServices (539.9 - 539.9) <07FC6766-778E-3479-8F28-D2C9917E1DD1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff8b3bc000 -     0x7fff8b3c0ff7  com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
        0x7fff8c051000 -     0x7fff8c0b9fff  libvDSP.dylib (380.10) <3CA154A3-1BE5-3CF4-BE48-F0A719A963BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
        0x7fff8c15b000 -     0x7fff8c17cff7  libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
        0x7fff8c1bc000 -     0x7fff8c1c2ff7  libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
        0x7fff8c58d000 -     0x7fff8c984fff  libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
        0x7fff8c985000 -     0x7fff8c993ff7  libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
        0x7fff8c994000 -     0x7fff8c99bfff  libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
        0x7fff8c99c000 -     0x7fff8c9aafff  libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib
        0x7fff8ccbc000 -     0x7fff8cf8dff7  com.apple.security (7.0 - 55179.13) <F428E306-C407-3B55-BA82-E58755E8A76F> /System/Library/Frameworks/Security.framework/Versions/A/Security
        0x7fff8d22a000 -     0x7fff8d589fff  com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
        0x7fff8d939000 -     0x7fff8d950fff  com.apple.GenerationalStorage (1.1 - 132.3) <FD4A84B3-13A8-3C60-A59E-25A361447A17> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
        0x7fff8d951000 -     0x7fff8d952fff  liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
        0x7fff8d953000 -     0x7fff8d95afff  com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
        0x7fff8d968000 -     0x7fff8d9d1fff  libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
        0x7fff8dbde000 -     0x7fff8dc4cff7  com.apple.framework.IOKit (2.0.1 - 755.42.1) <A90038ED-48F2-3CC9-A042-53A3D7985844> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
        0x7fff8e11b000 -     0x7fff8e11dfff  libquarantine.dylib (52.1) <143B726E-DF47-37A8-90AA-F059CFD1A2E4> /usr/lib/system/libquarantine.dylib
        0x7fff9012f000 -     0x7fff9024792f  libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
        0x7fff91567000 -     0x7fff91568ff7  libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib
        0x7fff91952000 -     0x7fff919b5fff  com.apple.audio.CoreAudio (4.1.2 - 4.1.2) <FEAB83AB-1DE5-3813-BA48-7A7F2374CCF0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
        0x7fff91a98000 -     0x7fff91c82ff7  com.apple.CoreFoundation (6.8 - 744.19) <0F7403CA-2CB8-3D0A-992B-679701DF27CA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff91c83000 -     0x7fff91e09fff  libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
        0x7fff91e13000 -     0x7fff91e25ff7  libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
        0x7fff91e76000 -     0x7fff91e7cfff  com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
        0x7fff91f14000 -     0x7fff91f54ff7  com.apple.MediaKit (14 - 687) <8AAA8CC3-3ACD-34A5-9E57-9B24AD8AFD4D> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
        0x7fff92028000 -     0x7fff92037ff7  libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
        0x7fff921bd000 -     0x7fff921c1fff  libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
        0x7fff921c2000 -     0x7fff92314fff  com.apple.audio.toolbox.AudioToolbox (1.9.2 - 1.9.2) <DC5F3D1B-036A-37DE-BC24-7636DC95EA1C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    External Modification Summary:
      Calls made by other processes targeting this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by all processes on this machine:
        task_for_pid: 240
        thread_create: 0
        thread_set_state: 0
    VM Region Summary:
    ReadOnly portion of Libraries: Total=89.5M resident=64.1M(72%) swapped_out_or_unallocated=25.4M(28%)
    Writable regions: Total=82.6M written=784K(1%) resident=1340K(2%) swapped_out=0K(0%) unallocated=81.3M(98%)
    REGION TYPE                      VIRTUAL
    ===========                      =======
    MALLOC                             72.3M
    MALLOC guard page                    32K
    STACK GUARD                        56.0M
    Stack                              10.0M
    VM_ALLOCATE                           8K
    __DATA                             3472K
    __LINKEDIT                         52.1M
    __TEXT                             37.4M
    __UNICODE                           544K
    mapped file                        18.1M
    shared memory                        12K
    ===========                      =======
    TOTAL                             250.0M

    That kind of crash is usually caused by system corruption. I suggest you reinstall.

  • WRT610N Dopped Connection

    I have a WRT610N that has been exchanged once already by my local electronics store but I continue to have issues. I have spoken to tech support at least 3 times and @ one point was convinced to pay $9.95 for some remote access software that would allow the technician to work on the router directly. Needless to say, it was a waste of money as my router continued to drop connection and reboot whenever it wanted to.
    Now, Linksys is telling me that they can only exchange the router for another WRT610N. I don't want another WRT610N, I want my $179.99 (plus tax) back!.
    I will continue to push to get this resolved with linksys
    (Mod note: Edited for guideline compliance. Thank you.)
    Message Edited by Vince_02 on 12-04-2008 08:24 AM

    Package the router back up in the original boxes along with the receipt and take it back to where you purchased it and get your money back.

  • Some healthcheck.htm requests do not respond (dropped connection)

    Hi,
    Several (most) of the services on our Exchange server don't return a valid response when querying their "health check" URL.
    These are OK:
     - /ecp/healthcheck.htm (200 OK)
     - /owa/healthcheck.htm (200 OK)
     - /powershell/healthcheck.htm (200 OK)
    But these fail with an instantly dropped connection:
     - /autodiscover/healthcheck.htm
     - /ews/healthcheck.htm
     - /mapi/healthcheck.htm
     - /Microsoft-Server-ActiveSync/healthcheck.htm
     - /oab/healthcheck.htm
     - /rpc/healthcheck.htm
    There are no errors or warnings noted in the event logs, and all services work normally for all users, but I don't see the failed requests in IIS' logs.
    What can be causing this?
    Thanks!

    Hi,
    According to your description, the health check URL cannot work for certain requests. And I’d like to confirm if there is any connection issue for your clients.
    Based on my research, here is a similar thread:
    http://social.technet.microsoft.com/Forums/ie/en-US/e9ee04de-9b62-44e7a-85db-3fff160dddd2/healthcheckhtm-not-accessible-for-several-protocols?forum=exchangesvradmin
    We can try to restart Exchange Health Manager service to resolve the issue as the above thread.
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Apple TV & Time Capsule Internet Dropping Connection

    Dear Mac/Apple TV/Time Capsule users,
    i had experienced the Dropping Connection problem:
    http://discussions.apple.com/thread.jspa?threadID=1959199&start=0&tstart=0 .
    and now i want to contribute to that thread
    My hardware Imac 21,5, TC 1T(1gen), ATV (1 gen, 160GB)
    Recently since i wanted to put a movie on my ATV i noticed than after uploading for 5 min
    the upload stopped and the connection dropped from my TC .
    So i've done everything:
    - reboot TC many times, change channel, downgrade to 7.3.2, upgrade again
    - downgraded ATV & upgraded again
    The only way to have back the wi-fi connection from TC is to search and put again the password from the ATV .
    i just solve the whole problem setting the wireless of the TC to N 5ghz good but invisible to my iPhone4…
    The question is what happened ??? Maybe an interference from another N Router/Cordless Phone ?
    Hope you'll find a reason 4 this..i can't explain !!!!!!!
    Ciao

    I wish I had a solutipn for you... I am having a similar problem which started in the last two days with my playstation not finding the network from the TC, although the AT! and everything else in the house can find it just fine. The connection in the AT1 is spotty. I wonder if setting the TC to "internet robustness" will help or hurt? I just tried that and will let you know if it helps. Also, often, the syncing stops and does not complete between our iMac (i7 processor) and our AT1.

  • WRT160N dropping connection

    Hi every one
    I just get Lynksis WRT160n (V3) yesterday, and it keeps dropping connection randomly ,but most of the time every 5-15 minute, I notice a couple of threads mentioning the same issue !! But I didn't find a fix to this horrible problem
    I don't have any problem connection directly to my ISP modem, or even when connecting directly to the router (wire) ,it's only wireless issue, and I installed the latest firmware yesterday, from Lynksis site, I don't have any wireless hardware that could interfere with the signal at my room, the router is close to my laptop.
    so my question is ,is there any fix to this problem ,or should I get the router back ??

    Since you have already upgraded the firmware on your Router, the first thing which you need to do is, Press and hold the reset button for 30 seconds...Release the reset button...Unplug the power cable from your router, wait for 30 seconds and re-connect the power cable...Now re-configure your router...
    On your Router setup page, click on the Wireless tab and change the following settings.. 
    For Wireless Settings, please do the following : -
    Click on the Wireless tab
    - Here select manual configuration...Wireless Network mode should be mixed...
    - Provide a unique name in the Wireless Network Name (SSID) box in order to differentiate your network from your neighbors network...
    - Set the Radio Band to Standard-20MHz and change the Standard channel to 11-2.462GHz...Wireless SSID broadcast should be Enabled and then click on Save Settings...
    Please make a note of Wireless Network Name (SSID) as this is the Network Identifier...
    For Wireless Security : -
    Click on the Sub tab under Wireless > Wireless Security...
    Change the Wireless security mode to WPA, For Encryption, select TKIP...For Passphrase input your desired WPA Key. For example , MySecretKey , This will serve as your network key whenever you connect to your wireless network. Do NOT give this key to anyone and remember the key.
    NOTE : Passphrase should be more that 8 characters...
    Click on Advanced Wireless Settings
    Change the Beacon Interval to 50,Change the Fragmentation Threshold to 2204,Change the RTS Threshold to 2205 and Click on Save Settings...
    Now see if you can locate your Wireless Network and attempt to connect...

  • Refund after 78 days of dropping connections

    Today I had a talk with BT billing, as they again did not give me a prommised callback.
    I had 78 days of continious dropping connections (as soon as you start using it it was dropping direct)
    it tool them 78 days to find out that there was a probleem with the cabeling underground
    every time they day you are getting refunded after the problem is solved (and i bravely payed my bills)
    now the time is that the lines do not drop again, thair answer is.
    out terms and conditions say that intermitting connections are not refunded.
    and i can do with that.
    2.5 months not able to use the internet, and having to use my mobile if i wanted to do something(pay as you go), and now they don't refund anything of the broadband costs (i pay 25 on broadband costs a month)
    Continious stress when calling them, every time it was the same procedure and they wanted to ask me all the questions again, and again and again..
    this little joke of them cost me a lot of money as i depend on internet for income (remote support)
    they charged me
    130 new line costs for a line which was there already (and engineers confirmed there was no work done at the exchange (BT said they are not allowed to discuss that with me)
    40 monthly line and broadband costs (so 100 in this period)
    they disconnected me because after 45 days of still not a functional line i refused to pay them before they did fix this. so they disconnect you and charge you 12 pound reconnection fee, and 7.50 late payment
    and they charged me 6.95 for sending me a new modem because they did think we have done everything so it must be the modem
    that makes way more then 250 pound payed for a line what worked 2.5 months to late
    what will they refund, some of the line costs 17.26 and 26 pound
    (another thing i am now waiting for is that my upstream is 443.9 what is much less the possible in training period, but that is already requested at the care team, so lets hope that they can take care of this)
    But what can I do to convince BT that 50 or more reconnections (what takes an avarage of 3 minutes each, and sometimes only have 1 minute of online time in between) that this should not be seen as an line with some interuptions  to what they refer in the terms and conditions.
    thanks for reading

    You are already waiting for contact from the BT Care Team on this thread.
    http://community.bt.com/t5/BB-Speed-Connection-Issues/limited-UPstream-speed-at-443-9-Kbps/m-p/61066...
    If you would like to raise any outstanding issues with them, they should be able to help.
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • New time capsule+new airport express=daily dropped connections

    I have a new 2 TB Time Capsule and a new Airport Express that I puchased to update my old set-up of an Airport Express and Airport Extreme.
    I have the TC set-up as the primary base station in the back of the house and the airport express set-up to extend the network in the front of the house. I was getting constant disconnects up front for the first several days so I finally exchanged the new AX for another one thinking maybe the first one was faulty. I reset the TC back to factory defaults for good measure and re-set up my network the same way with the new AX.
    Two days with no disconnects, thought it was fixed, and then it started again...no joy. Not as often as with the first AX, but still it happens 2-3 times a day and always up in the front of the house while we're on our MacBook Pro or MacBook Air. When this happens both the AX and the TC have green lights and full bars of connectivity show in the menu bar, but yet no internet access. The only way to reconnect is to restart the AX. I have noticed too, that when this happens, the Airport Utility does not show the TC at all...even though it's light is fully green and it should be there, it just shows the AX until I restart and then both show up again.
    I've tried changing the channel from automatic to a specific channel but this really doesn't change things much. Now I'm starting to wonder if something is awry with the TC. I've also noticed that it sometimes fails to back up because it can't find a connection to my iMac which is right next to it in the back of the house.
    So far this upgrade has been more of a downgrade. Any help would be greatly appreciated!

    Just an update and still seeking some advice for this situation...anybody?
    I tried re-setting both TC and AX to factory settings and re-configuring. Still get at least 3-4 dropped connections up front on a daily basis; however, TC has been connecting successfully and backing up my iMac, so at least that seems to be ok.
    Still the same situation with the TC not showing up in Airport Utility every time the network connection drops happen...just the AX is seen until I finally have to restart the AX and then both can be viewed in Airport Utility and the internet connection is restored. Sometimes I can restore connection by simply toggling my airport access on and off in the menu bar of my MacBook Pro, but more often then not, I have to restart the AX itself to get back online.
    Is it possible that this could be an issue with the TC? Somehow it might be dropping the connection to the AX? I can still exchange it for another if this may be the case. I'm already on my second AX thinking that the Express was the problem initially.
    So far, nothing seems to help the situation. About the only thing that I haven't done is configure the AX to just join the network rather than extend it...but that would be defeating the purpose of why I bought it in the first place (to stream iTunes and extend network).
    I never had issues with my old set-up, but then I had it configured as a WDS because I didn't have the option to "extend" the network as it was an older AX and Airport Express.

  • Poor performance and now dropping connection

    I am very underwhelmed by performance since switching to infinity FTTC last year. Download speed is very variable and I just cannot get an upload speed much better than 1.1 Mb/s.
    Now we have a regularly dropping connection. Last Saturday morning we had a thunderstorn with heavy downpour and phone line dropped completely - no dialtone and unsurprisingly no broadband. Did a line check from my mobile - all fine and no reported problems in the area. I phoned BT and got an Indian who just repeated what the website told me and said couldn't get an engineer for 4 days! Phone came back late the same afternoon and a little while later broadband came up but connection was up and down like a yo-yo. After 4 days of sunshine when the engineer turned up broadband had been up solid from 3 am and phone was fine. Engineer did more detailed tests which showed no problem and reckoned our problem must have been fixed, and that reason broadband had been dropping was because of computerised checks due to reported fault which would cause line to drop.
    For a few days all was fine, although performance still underwheliming, until we had another downpour yesterday morning. Phone line stayed up, although a little crackly, but once again broadband started dropping regularly. Since then it has gradually improved (no more rain).
    My suspicion is (and always has been) that with the heavy rain water is getting into a connection somewhere. How do I go about communicating it to BT support (I can't even find a web page or number for reporting broadband problems) this fact and actually getting someone to look into it properly? I rejected the "fault reported fixed" on the tracking your fault web page but so far nothing.
    I am distinctly unimpressed with BT support and unless this gets fixed soon I am seriously thinking of switching to fibre to the home with Virgin (despite hating Branson) especially as the move from Yahoo mail to BT mail has not been smooth and the BT webmail is full of bugs (which again I cannot find any way of reporting).

    Thanks. I tried that. Broadband up and down regularly until the day the engineer came. Day before had intermittent heavy crackling on the line and calls dropping. Day he came all is fine and of course his diagnostics checks come back all clear. Apparently, or so he told me, they are not allowed to work on our line unless the checks show a fault...which they didn't.
    I've just had 24 hours of our broadband working but just now it's started dropping regularly again.
    I am getting very frustrated/annoyed. What do I do now? How do they expect to solve the problem if it isn't constant and they can't get an engineer to look at it within 3 or 4 days? Do I just keep on calling our an engineer until by chance it happens to hit a problem while they're on site? Not good for customer satisfaction and surely it must cost them to keep sending out an engineer!

  • AT&T U-verse dropping connections suddenly

    Hi all.
    Since upgrading to Yosemite, there has been a degrading of my internet reliability with AT&T U-verse, and its been getting worse and worse.  I now drop connections every HOUR.  Speed and WiFi strength are great when its working, but it will spontaneously stop working, and if i do a series of diagnostics, quitting safari, turning wifi off and on, etc., I can get back online after a few minutes.  BUT WHAT THE HECK IS HAPPENING?  At this point I've mucked around with just about every network setting so I no longer even know what they should be.  AT&T is fairly useless regarding tech support for Macs, so hopefully someone here knows the current UVerse setup and can give me some advice.  Here's where I stand:
    - I have a 2009 Mac Pro, running latest Yosemite.
    - Router is AT&T Motorola NVG589, connecting to U-verse service (not gigabit, just regular)
    - When internet service drops, it appears that the WiFi continues to be connected well, at least for a while.  The NVG589 status page still shows my machine connected, and the WiFi signal strength in the menu bar remains full strength, but Diagnostics show failure to connect to ISP and internet.  Other Devices, like my phone or other laptops, continue to connect fine, so the broadband is fine, so maybe the WiFi is only appearing to work or something else is going on.  At some point, the WiFi also stops responding until I do a bunch of restarting stuff.
    - I have already trashed the various preference files and created fresh new locations, but to no avail.  It all works fine for a while then goes spotty again.
    - I have my network prefs set to "Link-local only" which had worked fine before.
    - I set the DNS servers to 8.8.8.8 and 8.8.4.4
    I don't really know much about the various pros and cons of different settings, but apparently you can get the NVG589 to assign a static IP address (or semi-static or something like that) but is that BETTER?   would that end the dropouts?
    Any other ideas?

    Hello Javier Bonafont,
    Welcome to the Apple Support Communities!
    I understand that it can be very frustrating when you are having multiple Wi-Fi drops in signal at home. There are a couple of different troubleshooting steps that I would recommend in this situation. Please refer to the attached article for information and steps to help you troubleshoot this situation.
    Wi-Fi: How to troubleshoot Wi-Fi connectivity - Apple Support
    Symptom: The network connection drops unexpectedly
    Your Mac may not not stay connected to your Wi-Fi network reliably.
    Your Mac may stop accessing the Internet during use.
    Solution
    Use these steps if your computer disconnects from its Wi-Fi network unexpectedly.
    Check your range to the Wi-Fi router and reduce the effect of interference.If your computer is too far from your Wi-Fi router or your environment has too much Wi-Fi interference, then your computer may not detect the Wi-Fi network properly. The easiest way to check for range limits with your Wi-Fi network is to move your computer or your Wi-Fi router closer together and make sure that there are no obstructions (such as walls, cabinets, and so forth) between the router and your computer.See Potential sources of wireless interference for more information about interference and solutions.
    Try connecting to a different Wi-Fi network. If your computer works fine when connected to a different Wi-Fi network, then the issue may be related to your network router or ISP. In that case, contact the manufacturer of your router or your ISP.
    Best regards,
    Joe

  • New Airport Extreme (6th Gen) Dropping Connection from Time to Time.

    Problem:
    6th Generation Airport Extreme drops connection intermittently at random times.
    Set Up:
    6th Generation Airport Extreme (main router - no hard drive/not a time capsule) located center of house on the main floor. 2 Range extenders each approximately 30+ feet away from main router. First range extender (Airport Express - newest generation) located on the third floor parallel to main. Second range extender (Airport Express - new generation) is located at the end of the kitchen (main floor).
    Main Router is connected straight from a Motorolla Surfboard modem on a foyer table at the center of the house.
    Range extenders connected to Main Router wirelessly and at wall outlett height.
    Previous Setup:
    Same setup as above but, with the 5th Generation Airport Extreme instead of the 6th Generation.
    Firmware:
    All current versions.
    Devices:
    1 SONY VAIO VGN-FW490J
    HP Notebook G60
    Several WEMO outlets
    1 iPad Mini
    1 iPad 2
    1 iPhone 5
    1 Motorolla RAZR MAXX
    Macbook Pro
    iMac (wired from main router on foyer table)
            Note: All of these routers/range extenders/modem/computers are plugged into surge protected outlets.
    Notes:
    With the new Airport Extreme my family and I have been experiencing intermettent connection drops. The amber light on the main router turns on and within a few minutes turns green and connection resumes again. This has been happening for a few days now ever since I purchased the new router. This has not happened before with the 5th generation router, which I donated to our church.
    I have not exchanged the product yet. I will be initiating a Complete Power Recycle after some suggested solutions in a bit. I have contacted my Internet Service Provider (Comcast) for a line check and found no problems.
    Has anyone found any solutions to resolve the intermittent connection drops? Is reverting to the previous firmware going to solve this?
    I would like some insights before trying to do all this. Thank you all for your time.
    P.s.
    I've done a detailed post since posts like these is frequently asked questions on set-up, devices, connections, etc:

    Update:
    Before I went to exchange my 6th Gen Extreme, I ran through all possible solutions from complete power recycle to no devices connected. I even went out of my way to my cousin's house to test it out. The same problem still kept coming.
    I was able to exchange my 6th Gen Airprt Extreme with another 6th Gen Extreme the other day. I set it up how the instructions told me and within an hour it did the exact same problem as the previous 6th Gen Extreme. I gave up and decided to get the ASUS RT-AC66R (ASUS RT-AC66U is the same, just the 'R' is Best Buy's model.)
    The ASUS router is just as great as the 6th Gen Router. You can actually get it down to $180 by price matching to Amazon. The ASUS router has 3 antennas that you can adjust according to where the signal is used more. I pointed them more towards the backyard, upstairs, and the living room. The range is by far better than the Extreme because of this. I was able to drive down a good block (3-4 houses down) and still connected to my router. Also it has 2 USB ports which was fantastic for me so I can plug in my external hard drive and a non-wireless printer. It has many more features that I really liked that I didn't even know was possible. The router utility interface is a bit confusing at first but, it's pretty easy once you get the hang of it.
    Some features that I liked with the ASUS was the ability to have multiple guest network with time limits. 3 for 2.4gHz and 3 for 5gHz. I think that Airport guest accounts are only allowed 2.4gHz but not a 5gHz. Though I only needed 1 for each but, I can see this working well for businesses.
    Another feature is traffic manager. I am able to set specific bandwith for different types of use such as, high priority 80%-100% bandwith for gaming, medium priority badwith 70%-90% for HD media streaming/data transfer, and 50%-80% low bandwith for casual web surfing. It also has it's own "beamforming" so that data isn't free roamed.
    Lastly it has AiCloud sync which is basically like having a hard drive into your router but, much like having a Dropbox at the same time.
    More or less I think I'll stick with the ASUS router rather than going with the new Airport Extreme. I think that it's more on firmware issue than it is hardware. If you are not willing to switch to another brand and want to keep staying with Apple, I recommend going back to the 5th generation until a new firmware or rebuilt 6th gen extreme is out.
    I have not found any problem with the ASUS router and no intermittent connectivity issues.
    Now I am not trying to make you buy the ASUS router. I'm merely expressing how great the product is.
    I do have 60 days from Best Buy return policy to try out the ASUS (and report of any malfuntions) and if within that time a new firmware is out for the Extreme. I highly doubt I'll go back to the extreme though.
    Hope this helped!!

  • LaserJet Pro P1102w dropping connection

    I hope someone can help. We have been having a long term issue with our HP LaserJet Pro P1102w wifi printer keeping a stable connection to our network. It connects to our network via wifi. It is in a high signal wifi area of the office.
    In the printer network settings I have tried setting the printers IP as static and also tried it as dynamic being assigned by our DHCP server.
    The problem is the printer keeps randomly dropping connection in that we can no longer print to the printer / access the printers webpage or ping the printer. The problems is fixed by either powering down and restarting the printer or if you leave the printer after a period of time the printer will once again be contactable (by doing nothing).
    I have updated the printers firmware, computers printer drivers. Checked network settings but just cannot resolve the issue.
    It's driving me crazy!

    Thanks for the clarification Angus,
    Try disabling the Auto Off feature, this current configuration actually turns the printer Off after 5 minutes idle (Any key pressing will turn the printer On, but any remote command as printing or accessing the printer page will fail..
    You may enter the EWS by entering the printer IP through Safari.
    Enter the Settings tab.
    Select Print Settings and turn the Auto Off after as Never.
    Click Apply and reboot the device, then check for any change.
    Now reboot the device and check for any chnage,
    Shlomi
    Say thanks by clicking the Kudos thumb up in the post.
    If my post resolve your problem please mark it as an Accepted Solution

Maybe you are looking for