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.
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.You have Windows File Sharing checked right. That's a work around, a little insecure.
I send an email directly to Craig Federighi. I also tweeted to @AppleSupport and @tim_cook.I confirmed this and filed a bug with Apple on it. With luck it'll get fixed soon.
I've already tested with an unpatched 10.13.1. File sharing works as expected there.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.
So after Apple updates another screw up, I wonder if this Patch will fail and we're back to no file sharing. LOL
2 weeks ago I swapped AFP for SMB. This week I did not have a single problem withYes. This problem only affected SMB sharing too. AFP was unaffected.
.... insecure ... .... WHY?Having the same issue since I've applied the patch. Interestingly, I had previously experienced this at some point running a beta version of 10.13.1.
What works for me is to activate Windows File Sharing for the account, but that seems like an insecure workaround.
View attachment 739136
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.Good eye. I see they quietly released the new version. Fair enough, most users will never know what happened in the last 24 hours.