macOS Sierra always prompts for credentials for network drives

I must say that it is unfortunate that the issue in this thread is listed as "solved" by switching to the AFP protocol, leading to a debate between SMB and AFP performance.

The issue is macOS Sierra (and possibly older versions of OS X via patches) prompts for credentials when connecting to Keychain-remembered connections, which is new behavior. Sure it's just one extra click, but we've been accustomed to think that when we see the credential window pop up, there was a problem and the credential needs to be re-entered.

Why go backwards in functionality? There should be an option to change the behavior back to only prompt on error, and not only for automation reasons.

i agree with you, this thread should not have a solved flag.

if anyone at apple monitors this community, they will fly right past this thread.

if the flag cannot be undone, i recommend we start a new topic and link to the initial post on this topic.

This issue is not solved.

I connect to AFP shares on my network and it does not automatically connect.

@Peter Almer -- please remove the "Solved" status of this ticket. The issue in general is not solved.

This is absolutely crazy and completely nonsensical. If you click the auto-discovered NAS share (in my case QNAP) in Finder without having entered credentials (again) you get the error 'NASNAME' can't be opened because the original item can't be found.

Who could have possibly thought this was a good idea? I hope to God(c) this is a bug!!

This is yet another example of Apple not giving two craps about business use. Windows shared drives are setup for SMB use not AFP. Now as a company we will not be updating OS versions for as long as possible.

the latest beta is 10.12.1 beta 5 ....

if anyone is running it, could you please post about whether this is fixed or not yet ?

Apple take this Feature from Windows Vista.

Workaround: Mount a network drive and create there a Folder for iTunes. No prompts for credentials anymore for this share. It's like a glass of water in ****.

Thomas-M wrote:

Observing it in Finder, it sits on "connecting..." for a long period before it jumps to "not connected", I'm almost thinking its a problem to do with Keychain for the reason that I'm having issues with Remote Desktop and Server all having issues with saved credentials.

Has anyone else noticed this?

I am experiencing exactly the same behavior with my Macs with my MacMini being used as

a server. All have Sierra. The Mini used as a server is running macOS Server 5.2. No NAS

involved.

What seems to be even odder, Screen Sharing connects without issue and immediately.

No waiting, no dialog.

If the behavior is an added "security feature", the Screen Sharing was left as a huge gaping hole.

Which is more a threat, uploading a questionable file or being able to take total control over

a computer?

Hello;

For what it's worth I have found an interim solution to auto-mount my symbology NAS.

Since this seems to be several issues at seem to bet intertwined in the discussion; i'll just relate to what i had to do.

1. Created a shell script file with a mount command that includes the NAS user's credential info and mounts to the login user's home directory (apparently /Volumes is not a valid user mount point anymore)... for example:

#!/bin/bash

mount -t smbfs smb://nasusername:nasuserPW@nasusersharename ~/synology

this shell script file must be executable (chmod it with +x)

2. Open automator and create a new APP and drag in the run shell script and point to the above file (i put it in a 'scripts' directory on my home directory).

3. you can test the .sh file and the saved application that run's it and if all goes well; just add that app to your login items.

yes this is obviously not a good solution for a business where the the IT dept deploys user's machines that have to connect to a company share... but it's been working reliably for my personal use.

also note that i used smb to connect so this wouldn't apply to a time machine requirement i assume.

Comment... I also frequently use screen sharing to connect to my servers and did note that after the authentication is

made the credential information is persistent (the way the network shares used to work for me).

I was pretty much forced to move my photo library (>250gb) off to an external hard drive and opted for the NAS for the

reliability; Im also facing to do a similar thing with my iTunes library... the reliance on external network storage devices should be supported and expected imho. This was the worst upgrade i've ever experienced with Apple OS X. Came very close to loosing my photo's library (on the NAS previously connected with AFP).

</comment>

Thanks for that, but I just wonder...does anyone who counts read this thread? I am not into coding, and if you are and those things work, great!

But I'm just a normal guy, in charge of tech support at the school I work at, so I'm not a computer illiterate, but all this coding, and workarounds for something that was cause by an upgrade? Plain and simple...something in the upgrade was broke, and nobody seems to be listening. And to fix it!

Sorry...just venting here, but before Sierra, I never had to re-re-confirm and log into my network shares. Everything ran smooth as silk, and I was loving my El Capitan. Then...I made the HUGE mistake of upgrading.

Please, oh PLEASE Apple..listen, and read, the complaints of the people who, like me, just simply want to log in to their MAC and not have to Re-Connect their network shares, every stinkin' time they start up their computer!

The Mac you're connecting to via screen sharing has no display attached or powered on?

I noticed if I screen share my server from my Mac and the display is powered off it doesn't ask for pssword.

On one of my macs yesterday I noticed it worked as per normal again, clicked on the shared Mac in finder, auto logged in with "com.apple.someextralongkeychainstribg" and acted perfectly. I really do sense a keychain issue.