File Sharing broken after Upgrade to 10.9

I have the same problem for all sharing point!

Try to go in your server in system preference and then go to Sharing. Select the File Sharing menu in the left side vertical bar, then go in option and uncheck the Share files and folders using SMB and leave the Share files and folders using AFP checked. Now on my server work ... but I need to use SMB connection for 2 client windows!!!

I find that for me our AFP is working, its the SMB thats not with a stupid error message "There was a problem connecting to the server. URLs with type "smb:" are not supported..... *** ! It worked just fine prior to the upgrade... and even on 10.7.5 & 10.6... and MAverick adverts boast better connectivity to SMB.... what gives ?? This is not very encouraging and most frustrating .... why would Apple not test this and why do we not see any "Apple Support" people chiming in on these issues?? Wow ...

Similar situation here. Clean install of 10.9.0 and Server 3. SMB works as expected but AFP and Time Machine doesn't work for any user after the original admin user created at install. I tried to give one of the new users admin permissions just to test if that was the thing but it didn't help.

The same thing happened here. After upgrading to 10.9 the network users could log in but had no access to the AFP shared files on the server. There was one file system with SMB switched on. When I switched it off all users had access again to all AFP shared files. Don't ask me why but may be it works for you as well.

I had the same problem with AFP/SMB/WebDav File Sharing on my OSX server. Disabling SMB allowed access. When connected to the File Share Folder using AFP, the user id was the Apple ID and I was unable to disconnect so that I could login using the User ID on the Server.

Based on the console output it appeared that the Apple ID of the account was automatically being used to connect to the file share. Deleting the keys did not work. I was able to resolve the problem by:

1) Open Keychain Access

2) Select Keychain First Aid from the Keychain Access menu; select Verify then Repair

3) Select Preferences from the Keychain Access Menu; select Reset My Default Keychain from the General Tab; deselect all options from the General and First Aid Tabs

I have the same problem, so I'd like to know some details:

How did you see that the Apple ID was used? Console output on the server or on the client? What was written there?

Did you reset the keychain on the client?

When I try to connect I see that output on the client console:

04.03.14 19:35:45,264 NetAuthSysAgent[829]: NAHSelectionAcquireCredential complete: iakerb <some code number> - dirk: GSSCred: <a hex number> <MC: iakerb dirk@WELLKNOWN:COM.APPLE.LKDC>

04.03.14 19:35:45,294 NetAuthSysAgent[829]: NAHSelectionAcquireCredential Der Vorgang konnte nicht abgeschlossen werden. (com.apple.NetworkAuthenticationHelper-Fehler -1765328228 - acquire_kerberos failed dirk@LOCAL: -1765328228 - unable to reach any KDC in realm LOCAL, tried 0 KDCs)

Thanks,

Dirk

This may help. If you do have "Share files and folders using SMB" checked, then you need to make sure you have at least one Account "On" in the list of "Windows File Sharing" accounts at the bottom.

This Sharing "Options..." pane is not well designed. Many would not know that "SMB" = "Windows File Sharing" and these two seperate options are not even next to each other. It's not obvious, and the error message you get when you try to log in without having an account selected does nothing to alert you to this fact.

What suprises me, is that the login doesn't automatically try AFP when it finds there are no Accounts on the SMB share.

Bottom line, you might as well turn off SMB entirely if you don't work in a Windows environment.

Hope this helps.

Thanks Mark.

This solves my problem. I just disabled 'SMB' and it worked like always.

Apple guys, please take a look on this issue.

For me it does not work even with SMB disabled. All of this used to work. I have a mac Mini and an iMac and neither are able to see each other since mavericks. Also upgraded to Yosemite and the call feature is not working from either of the Macs either.

So, it wasn't working for me. I did nslookups on the terminal and realized that I wasn't able to ping the network addresses for the computers. I was able to ping the router though and the devices that were wired on the network leading me to believe there was a problem with wifi. I looked and for some reason my iMac, iPhone etc looked like the same device to the router. We have 2 iPhones, 2 iPads, 2 macs, 2 apple tvs, 1 rook etc. So I reset the router to factory defaults, reconfigured then brought each device online separately. File share is now working and so is iPhone calling from the desktop.

So, if some of you are still having issues, maybe check your wifi router.

This might also help: connect with cifs://

FROM:

http://osxdaily.com/2013/10/30/connect-smb-nas-network-shares-os-x-mavericks/

Connect to SMB & NAS Network Shares in OS X Mavericks

Oct 30, 2013

... a very easy workaround to connect to SMB and NAS shares from OS X:

From the OS X Finder, hit Command+K to summon “Go To Server” as usual.

In the “Server Address” field, use the cifs:// prefix as follows:

cifs://127.0.0.1

Connect to the SMB, NAS, or Windows share as usual.

... it’s because using CIFS connects with SMB1 rather than the (currently) buggy implementation of SMB2. ... Apple adjusted the default protocol for SMB (Samba, the Windows file sharing ability) from SMB1 to SMB2, and the SMB2 implementation apparently carries a bug which is incompatible with ...

Hi, so I have a similar problem, but all my user accounts (I only have one) are grayed out in the "Windows File Sharing" listbox. Any ideas there?

I have found File Sharing hanging and working poorly since Leopard. Nothing from Apple on this. Pathetic.