Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Security Update 2017-001 BREAKS File Sharing
- Thread starter joedec
- Start date
- Sort by reaction score
With the Finder open a file share to any Mac with the security update installed. Status shows "not connected", when you try to "connect as" your username and password fail.
Could you provide specifics, please, to help others attempt to reproduce this?
EDIT: Disregard. I see your reply. Sorry.
You have Windows File Sharing checked right. That's a work around, a little insecure.
I just now realise that I only have SMB connections from my Mac to my NAS, not to my Mac (and I don't have Windows File Sharing checked). I missed this in your second post, sorry for the confusion.
I confirmed this and filed a bug with Apple on it. With luck it'll get fixed soon.
Confirming the issue. I can't acces my mac through local network anymore. Worked fine before the update. SMB sharing is activated, but get no access with user/password. Drop Box - folder is unusable as well, even for guest account, writing to that folder is not working as well. I guess Apple messed it up again.
..."as soon as possible" ... my a** !!
..."as soon as possible" ... my a** !!
I wonder if Apple developers are measured on bugs closed... It's almost like they only fix and test what the bug report entails, **** wondering what the fix affects and testing the rest of the system, like it would cost them time and lower their score. PKI sucks for developers, because it always ends in min/max behaviour, not whats best for the project.
To be a little more accurate: this breaks File Sharing between High Sierra machines that have the update installed.
I can file share to a Mac mini running 10.12.6 (fully updated) just fine. If I try to file share to any High Sierra machine from the Mac mini, credentials are rejected. This is simply an issue with the Security Update. I currently have a fresh install of 10.13.1 going on a test machine to narrow it down to the Security Update 2017-001 for 10.13.1.
[doublepost=1511995139][/doublepost]
I send an email directly to Craig Federighi. I also tweeted to @AppleSupport and @tim_cook.
I can file share to a Mac mini running 10.12.6 (fully updated) just fine. If I try to file share to any High Sierra machine from the Mac mini, credentials are rejected. This is simply an issue with the Security Update. I currently have a fresh install of 10.13.1 going on a test machine to narrow it down to the Security Update 2017-001 for 10.13.1.
[doublepost=1511995139][/doublepost]
I send an email directly to Craig Federighi. I also tweeted to @AppleSupport and @tim_cook.
I've already tested with an unpatched 10.13.1. File sharing works as expected there.
ok guys, here's the fix from apple for file-sharing trouble https://support.apple.com/en-us/HT208317
entering sudo /usr/libexec/configureLocalKDC into terminal should repair file-sharing.
tested and confirming filesharing works again !!
entering sudo /usr/libexec/configureLocalKDC into terminal should repair file-sharing.
tested and confirming filesharing works again !!
Last edited:
I just posted this. Can't access any of my shared drives anymore after this update. I have Airport AC.
[doublepost=1512011115][/doublepost]
So after Apple updates another screw up, I wonder if this Patch will fail and we're back to no file sharing. LOL
[doublepost=1512011115][/doublepost]
So after Apple updates another screw up, I wonder if this Patch will fail and we're back to no file sharing. LOL
Apple has revised the security update to include a script to fix this, so build number on the update is now 17B1003.
2 weeks ago I swapped AFP for SMB. This week I did not have a single problem with
File Sharing between my 3 macs, not before - not between those updates, not after.
What did I do wrong? (LOL)
;JOOP!
[doublepost=1512056864][/doublepost]
.... insecure ... .... WHY?
;JOOP!
Good eye. I see they quietly released the new version. Fair enough, most users will never know what happened in the last 24 hours.
Was wondering why the 2017-001 update message showed up again in the App store. I installed the original 2017-001 update and it was successful. In fact, my build number is 17B1002.
From another forum I read that since the build number changes as chrfr pointed out, the Nvidia driver (Macs that use this driver) gets disabled. Correct me if I am wrong.
Last edited: