Can't access Airport Extreme after Yosemite install.

i have a vaguely similar issue... after upgrading to Yosemite, the 'back to my mac' password(iCloud id) will not stick - as soon as i update settings on new airport extreme, password is gone and 'can not connect to iCloud' is back... i have a new airport express that remains logged in... any ideas?

Richie Z: I doubt this is the same problem, or even a variant. On the surface, it sounds like an entirely different bug.

thanks, i'll make a separate post

Hello guys

I have problems accessing the shared HHD, sometimes they do not appear on the Finder Under Network shares and sometimes they appear but I can not access. It seems Yosemite broke the whole thing regarding shared drives.

As a rule the shared drive connectivity once is stablished is realiable (I didi not have any issue while transferring files), but the problem is establishing the initial connection and once everything is connected it losses connectivity during the day; then when I try to access the shares again I get the error "connection error".

As a temporary work around, had to connect to another AP then go back to the one I'm using and it seems it is solved, they connects again.

With Mavericks everything worked better.

On my day to day I use a lot the shared drives over the network, please apple try to solve this !!! This is the only very important bug I can complain in Yosemite.

My topology is as follows

1) Linksys router (with custom FW) receiving the Internet WAN. (HDD attached using SMB)

2) Airport Extreme 5thg as WIFI Access point (HDD attached) using AFP

3) Time Capsule 4thg as wifi extender (HDD attached and internal 2TB HDD for backups) using AFP

5) WDTVLive with Pend Drive attached using SMB.

Same issue here. Not running a firewall. In Airport Utility, "Internet" green light is showing, it no Wi-Fi devices are found.

I had configured the Time Machines with local static IP addresses. If you know the IP address, the File->Configure Other will bring up the panel that allows configuration. But nothing I've tried brings up the devices on the main window.

I realize that even if the shared drives are not accesible using the FINDER (they do not appear or we get connection error) they can be accessed fine and used from an ALIAS.

So far, it works to me !!

Just to confirm I'm having too issues with the Airport Utility, green light on both Time Capsule and Airport Extreme, and the Airport Utility is unable to show device details or the EDIT button. Sometimes get a gray icon or sometimes orange, on the Aiport Utility for these devices, but on the real devices the light is green and working.

The suggestion by owlmama worked after reboot. Thanks!

I did a hard factory reset on my airport extreme, set it up again, and it works fine now.

I am experiencing intermittent problems with my Airport Extreme and just realised after reading this thread they started to happen after Yosemite install and I pretty much have the same symptoms many folks shared in this long threat.

The connections to the attached disks to the Airport disappear on my Mac Air but if I go to other computers (running ubuntu, windows, on my iphone 5S) I can see the drive attached to AirPort so seems that the problem is somehow related to Yosemite.

I installed today latest Yosemite patch and the issue happened again a few hours after the install.

I have a Mac Air running Yosemite 10.10.1 installed today Nov 19th/14.

My router is an Airport Time Capsule with an internal 2TB disk and an external 2TB disk. The firmware version of the AirPort is 7.7.3.

When the problem happens, sometimes it goes away in a few minutes, or if not, If I restart the router (pulling the plug, which I hate to do) it recovers when the router comes back on and the Mac reconnects.

FWIW, this began happening to me only after I updated my Mac to 10.10.1 from 10.10.0.

A one-time fix that has worked for me has been to restart my Mac or to restart my Time Capsule base station. Time Machine will then successfully run a backup; it will fail after that. Alternatively, I can mount the Time Capsule's hard drive to my desktop and as long as I don't dismount it, it will continue to function normally. But once it is dismounted, it cannot be found again by either the Finder or Time Machine. The entire Time Capsule can't be found by Airport Utility, either – until either the Time Capsule or Mac are restarted.

After reading this thread I tried disabling the firewall and that worked. Until I turned the firewall back on and dismounted the Time Capsule's hard drive; then the symptoms reappear until/unless the firewall is turned off or the Mac or Time Capsule are restarted.

Something that seems to have worked for me, at least so far, is to add both AirPort Utility and Time Machine to the "Allow Incoming Connections" exceptions list in the firewall. Do that here:

System Preferences -> Security & Privacy -> Firewall ->Firewall Options

Nope, that's not working. Only thing that's consistently allowing a connection to the Time Capsule via AirPort Utility or to the Time Capsule's hard drive via Finder or Time Machine is a restart of either the Mac or the Time Capsule. And that works for one mount of the Time Capsule's hard drive.

What sometimes helps is not a complete reboot but a force quit of airportd in Activity Monitor. I run also Server and since 10.10.1 , even the beta .1 had the new bug of not connecting to my AE. This is in Airport Util and in Server. 10.10 was fine.

After the force quit, the process restarts itself immediately. You can also force quit Airport Base station agent. If that does not help, force quit discoveryd and discovery helper. These processes restart themselves and you can see and edit your AE again. Will see how long it lasts. I just keep Server open.

What a bummer, this.

FYI, I'm on a native IPv6 connection. All is enabled.

I found something that works. For me. For more than a full day so far I haven't been affected by this issue.

After reading this MacWorld article...

http://www.macworld.com/article/2849849/bugs-and-fixes-whats-with-yosemite-renam ing-shared-devices.html

...I did the following:

• Disabled wake-from-sleep for network access.
• Disabled Back To My Mac on both the Mac and the Time Capsule.
• Reset my Mac's name – which had changed on its own from JMH’s Mac Mini to JMH’s Mac Mini (2) – followed by a restart. Restarted the Time Capsule, too.
• Since I was restarting I also booted from Recovery Partition and ran a disk Repair and a permissions Repair but I don’t think this is related in any way.

A day later and all my renaming and Time Capsule/AirPort connection issues haven't reappeared. I've been able to connect and dismount as often as I like and the "fix" lasts through logouts and restarts.

My guess – sorry, that's all it is – is that disabling Back To My Mac on both the Mac and the Time Capsule is what did it for me. But I'm leaving Wake For Network Access turned off, too. I have work to do; can't be bothered trying to track down the issue further since I can live without both functions for now.

Apple needs to get an OS update out ASAP to repair this issue permanently and without regard to feature settings.

Three days later and the problem has not recurred since I applied the changes described in my previous message.

I had a little extra time this morning waiting for a return phone call so I experimented a bit and determined that, for my Mac at least, the problem is being caused by System Preferences->Energy Saver->Wake for network access. If I enable it, =BOOM= I can't connect to the Time Machine backup hosted on my Time Capsule nor can AirPort Utility see my Time Capsule. As soon as I disable it (don't even need to restart the Mac) everything works again.

I have re-enabled Back to My Mac on both my Mac and my Time Capsule, although with "Wake for network access" disabled it isn't going to be terribly useful. But I hardly ever use it anyway; for me, "Wake for network access" is a rare convenience but I can live without it. For now.

Well, today it still works after force quitting discoveryd. Opend a few times Server and Airport Util, all seems fine now.

Strange.