This discussion is archived
19155 Views 41 Replies Latest reply: Mar 30, 2010 2:43 AM by DavidMcQ
Currently Being ModeratedSep 20, 2009 2:17 AM (in response to Jose M Olaya)How does the drive work if connected to a Mac? It sounds like your hard drive is failing.A collection of clinking, clanking, clattering caliginous junk., Mac OS 8.6 or Earlier, PDP11
Currently Being ModeratedSep 20, 2009 4:22 AM (in response to DaddyPaycheck)It's a brand new drive and works just fine on my mac mini.
In fact I bought this one to replace my old 250gb hard drive which I assumed was failing because of this conection failed error. Guess what.. it wasn't the hard drive LOL but it's ok because I really needed the extra 500gb space.MacBook Pro Core 2 Duo Santa Rosa 2.4 ghz 4gb ram 160gb hdd + iMac 2.2ghz, Mac OS X (10.5)
Currently Being ModeratedSep 30, 2009 3:28 PM (in response to Jose M Olaya)I am having the same problem and all I have attached to the airport extreme is the external hard drive.
I have seen other posts on this topic, all similar complaints and all after upgrading to snow leopard. Jose, are you running snow leopard or leopard?MBP unibody, Mac OS X (10.6.1)
Currently Being ModeratedSep 30, 2009 5:09 PM (in response to Jose M Olaya)Upon perusing this thread, you said that you use the network drive connected to the airport extreme for time machine backups. It would be safe to think that this began upon a recent update to the airport extreme firmware (most likely when you updated to 7.4.2) I would try to upload an earlier firmware and test it that way, as time machine is not designed to work with a network drive connected to an airport extreme: http://support.apple.com/kb/HT2038.iMac, Mac OS X (10.5.8)
Currently Being ModeratedOct 2, 2009 5:35 PM (in response to TehPwN)I've actually has the same problem with losing the airport disk. I actually was having the 'connection failed' problem while using the airport with Tiger... both with a USB hub and without a USB hub. Obviously, I wasn't using the disk as a timemachine backup until recently, when I upgraded to snow leopard.MacBook, Mac OS X (10.6.1)
Currently Being ModeratedOct 3, 2009 2:41 PM (in response to mreynolds_728)I am also having this problem, with or without a powered USB hub, with 2 different drives, while the drives are being used for iTunes, not Time Machine. Both drives are trouble free when directly attached to my Mac. I had this problem occasionally on awakening from sleep prior to Snow Leopard, but now it happens as often as several times a day. It seems entirely random as far as I can see. Since I have to either go downstairs to another room and power the disk down and up or restart the AEBS to get the disk back, this is making airport disks pretty much unusable.
The following messages are issued:
*Oct 3 17:17:56 Macintosh-4 KernelEventAgent: tid 00000000 type 'afpfs', mounted on '/Volumes/ITunesIPhoto-1', from 'afp_0SKbl41Cg1Li0ADaWq008PHG-1.2d000005', not responding*
*Oct 3 17:18:31 Macintosh-4 KernelEventAgent: tid 00000000 received event(s) VQ_DEAD (32)*
*Oct 3 17:18:31 Macintosh-4 KernelEventAgent: tid 00000000 type 'afpfs', mounted on '/Volumes/ITunesIPhoto-1', from 'afp_0SKbl41Cg1Li0ADaWq008PHG-1.2d000005', dead*
*Oct 3 17:18:31 Macintosh-4 kernel: afpfs_DoReconnect: max reconnect time reached 35 > 30 (Connecting 61) /Volumes/ITunesIPhoto-1*
JackCMacBook Pro, Mac OS X (10.4.8), 2.33 Ghz Intel Core 2 Duo - 2GB
Currently Being ModeratedOct 5, 2009 5:06 PM (in response to Jose M Olaya)I am curious to know what other's experiencing this problem may be with the following:
I turned off the firewall on the mac itself and the external disk connection seems to be stable. I've had no disconnects since disabling the firewall but haven't put it through a long test yet.
I tried this after browsing through the console logs and noticed errors related to rejecting requests.
I am not sure this has anything to do with the problem, just throwing it out there for consideration.MBP unibody, Mac OS X (10.6.1)
Currently Being ModeratedOct 5, 2009 7:05 PM (in response to Jeff Cyr)After looking at this thread on Apple Discussions:
I downgraded the AEBS firmware from 7.4.2 to 7.4.1 and have had no problem with either of my drives for 2 days of usage. It certainly looks as if this is a problem with the 7.4.2 firmware.MacBook Pro, Mac OS X (10.6.1), 2.33 Ghz Intel Core 2 Duo - 2GB
Currently Being ModeratedOct 6, 2009 3:18 AM (in response to JackC)I've had the same problem ever since i bought my AirPort Extreme last week. I've tried downgrading to 7.4.1, but with no luck. The disconnects seem completely random. I've had the drive connected to my directly MacBook, running smoothly for several months, so this is getting a bit irritating. When the drive disconnects and I click on my AEBS in Finder to look for the USB drive Finder will crash and I have to restart my MBP every time.
The only thing that works is rebooting the AEBS every time this happens. Which is several times / day.MacBook Pro 15", Mac OS X (10.6.1)
Currently Being ModeratedOct 6, 2009 6:20 AM (in response to askielboe)Downgrading to 7.1.1 has stabilized the AEBS disk connection for me. Interestingly, now that I've downgraded, Timemachine doesn't seem to be able to connect to the network disk. I know network timemachine disks aren't supported, but it seemed to work for me when I tried it last week with 7.4.2.MacBook, Mac OS X (10.6.1)
Currently Being ModeratedOct 17, 2009 3:40 PM (in response to Jose M Olaya)I am having a similar issue.
I have a 1TB Lacie USB 2.0 hard drive connected to my Airport Extreme (802.11n, firmware 7.4.2) along with a USB printer (I use a hub.) The backup drive is used as a time machine disk for the two macs in my house (both running Snow Leopard.) About three times per week, both machines encounter the following error:
*Time Machine Error*
*The backup disk is not available.*
When I try to connect to my Airport in the Finder by clicking on it in the Finder's sidebar, there is a dark gray bar that reads "Connection Failed..." and gives me a "Connect As..." button. When I click on the button, I get a dialog that reads:
*The server "server name" may not exist or is unavailable at this time. Check the server name or address, check your network connection, and then try again.*
Given this error, I tried to connect to the Airport using it's IP address (using the Go -> Connect to Server dialog in Finder.) I get the same error message as above.
Curiously, I can still connect to the internet, I can still ping the Airport (to verify it's IP address), and *I can still print off of the USB printer connected to it via the same USB hub.* In fact, everything seems to be in perfect working order except for mounting the airport disk!
The temporary solution is to unplug the USB cable from the disk and plug it back in. As I said before, it breaks again very quickly.
--JordaniMac C2D, Macbook C2D, Mac OS X (10.6.1), Airport Extreme (802.11n), iMac uses Ethernet, Macbook uses WiFi
Currently Being ModeratedOct 22, 2009 3:28 PM (in response to Jose M Olaya)I'm also having this problem.... Its driving me mad!
I have a 1TB WD MyBook attached to my Airport Extreme. I'm using the WD MyBook with TimeMachine on my Mac Pro. At random times and what seems for no reason, the drive will just eject/disappear from my desktop and TimeMachine will give me a warning.
If I go to Finder and click on the Airport and then try to Connect to the MyBook I get a connection failed.... The only way I can fix it is to unplug the USB cable from the drive... A few times that didn't work and I've had to restart the Airport.
Other than this every thing seems to be working great. Strong signal, Internet works, my airport express has a good signal and I can print wirelessly to the printer thats attached to the express just fine. I hope there is a update or fix for this....
Why Airport Disk do you hate me? Why?Mac Pro 2.66 - iPhone 3G - Apple TV - Airport Extreme/Express, Mac OS X (10.6.1)