macOS Sierra always prompts for credentials for network drives

shouldn't have to do that to have relatively painless share automounting.

i am disappointed looking at this situation and ppls responses - different ppl have different experiences and it hints varying degrees of fragmentation amongst different users. isn't apple supposed to stand for better ? regardless of mac mini, imac, macbook, etc... the same OS platform should work relatively the same on recent mac computers.

looking at the direction apple headed in with the macbook pro, it's obvious they no longer care much for the mac platform in general .... the new lineup introduced is disappointing imo (lacking CPU, lacking RAM, lacking SSD, etc., what's offered is not worth the asking price even with the macOS experience). how are audio and video pros supposed to do their work on a 16GB ram ceiling that is the same as some macbooks from nearly 4 years ago ? "they made it thinner" you might say and the serious mac users would say "who cares"

seeing that trend, i wouldn't place all my eggs in this nest as a primary OS, still keeping win10 running on the other partition for dependencies.

Uh, I've been having this problem too. Not only that, but my drives seem to be dismounting every so often.. not sure if its related or not. (Synology DSM 6.0.2-8451 Update 2) SMB or AFP are acting no different.

I'm trying to set a constant ping to see if my connections will stay. I can live temporarily with the login issue but the disconnects are creating real issues.

Might try the latest beta update Sierra as well and see if there are any changes.

Saying this is a feature does not make it better. 😉

Designing a car with a blacked out windshield for sun protection as a feature does not eliminate the problem of having to drive with your head out the driver's door.

This never was by design, nor a feature - no matter what anyone says. It was, and is a bug. But...its been fixed in 10.12.2 beta 2 I've just this minute installed. About time! Thank God(C) for that!!!

to Bama350z:

i saw a notification email of your post on this thread, for some reason it was removed. i suspect probably not by you.

it seems that if comments are made comparing apple products to microsoft products in a manner that shows the apple product is inferior or problematic - that it would get removed on this forum.

that's a sad state of this time, where this type of censorship is allowed here. i've not seen it done elsewhere like this.

regardless, the topic you brought up i generally agree with - for the reasons you mentioned as well as many others - apple will never claim any larger percentage of user base, especially in the enterprise.

from lacking file system functionality to numerous holes/bugs in OS X and MacOS in general - i found the only thing that's pleasing using macOS or OS X is the visuals and smoothness of the UI.

kind of tells you something that functionality and performance are in the trash can vs. what Apple feels their products need to be.

its likely not censorship... we don't need rants that have no relation to the topic. if apple wanted to compete for the bottom they could get a larger user base. id take a MacBook that doesn't boot over a windows device anyday, and I too used to be lost in Microsoft ****.

looking on wikipedia's sierra page, it looks like the latest official release is now 10.12.2.

can someone who's downloaded it, please confirm the re-authentication issue is finally fixed in this official release ?

I've been using AutoMounter since upgrading to Sierra and although it works, its doesn't create mounts inside /Volumes, so its useless for anything terminal related that might be using the /Volumes/XXXX.

Since upgrading to 10.12.2 I've now switched back to Drive Mounter and everything seems to be working fine. However I'm now noticing loads of entries in my /Volumes folder for the same share, so I have stuff like

Storage, Storage-1, Storage-2..... etc. The longer the machine is running the more it creates.

Is anyone else seeing this behaviour ??

I updated to 10.12.2 on two Macs as well and network drives now automount. I didn't even have to re-save the passwords in Keychain. Odd that Apple never acknowledged the bug nor did they call it out on the "fixes" bullets.

good thing you mentioned automounter:

for the longest time I have used drivemounter with el capitan and it worked fine. always seem to notice sluggish mounting during a startup. but once mounted, after several sleep/wake cycles my shares are still connected.

I also plunged into automounter (only just recently bought it). I noticed this mounts my shares faster upon startup in el capitan. however you are raising this issue which makes me wonder what's the difference between these 2 apps in terms of what they are doing and how they mount the shares ?

with both apps I found that afp connection is much more stable and reliable than smb, which I tried and they did not work well with either drive mounter or automounter. I did not give much attention to the other connection types like nfs. wondering if I should try that.

wondering if I should bother with using these automounting tools at all if I upgrade to sierra ? if I upgrade to sierra and then mount the shares first time, then add them to the login items list - does that "hide" check box actually hide the finder window that typically shows up when you first startup and the share is initially mounted ? in the past I found that did not work.

The App Store always gives you the latest build, so once Apple officials releases a build update, that is the version available on the App Store. I upgraded one machine yesterday and the App Store installed 10.12.2. You will get the full (combo) update if you don't already have Sierra installed or if you download from the App Store from the Purchased tab. If you see a Sierra update under the Updates tab it will be a delta update. Hope this helps.

Are trying to auto mount upon startup or does this behavior persist with 10.12.2 when your try to manually mount a network drive where the password is already stored in Keychain? I misspoke in my previous post when I said "auto mount"; I meant manually mounting a disk.

I have a RAID drive connected to a Time Capsule on my home network and I routinely access it to store/retrieve files. With 10.12 and 10.12.1, I had the issue described in this thread. After upgrading to 10.12.2, the usual behavior found on all previous releases of OS X (i.e., click on the disk in Finder sidebar and it would mount without entering a password, assuming you stored it in Keychain the first time you tried to mount the disk) returned. This is true with both my 2012 Mac mini server and 2015 MBPr.

If this is not the case for you, perhaps Keychain is corrupted and you could try clearing the related passwords and starting over. If you're auto mounting a drive, I'm not sure what to say since I am not configured that way. Perhaps another poster can offer advice.

it seems that there are some instances of persistent issues with this even after updating to 10.12.2.

i still have not upgraded from el capitan, and i'm not sure i will if there is a chance this issue will resurface with my installation.

would rather not deal with it again and then restoring from a disk image to get back to el capitan for a second time.

thats interesting, because i thought some ppl have said this is actually a bug rather than a feature.

what would executing this command do in terms of NAS security on a home network ? can malicious code gain access to the NAS ?

The 10.12.2 update fixed this completely for me. I use an Applescript to log in to my file server and previously it was asking for the password no matter what. Now the script is magically working perfectly again without asking for the password.