You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

jdunruh Author

Level 1

4 points

SMB file sharing to SBS 2011 broken?

After upgrading to mountain lion, I am unable to mount SMB shares from my windows SBS 2011. When I use "connect to server" in the go menu, I get the screen to authenticate, I type the correct server user name and password, and then it cannot connect. When I brotse, I see the server, I connect as myself, and the finder shows directory "/". When I try to go farther, I get "The operation can't be completed becausse the original item for "/" can't be found. I am in a domain environment. The "kind" is Sharepoint, which leads me to believe it connected to sharepoint instead of my SMB shares.

MacBook Pro (15-inch Early 2011), OS X Mountain Lion

Posted on Jul 25, 2012 3:48 PM

67 replies

Aug 23, 2012 10:12 AM in response to jdunruh

Problem resolved, Thanks Apple! 🙂

Aug 23, 2012 10:35 AM in response to hardware geek

Same here. With the upgrade to 10.8.1, I am able to see all the shares on my previously broken Windows 2008 server. I don't have any other issues to report related to SMB connections.

Most importantly, I am now recommending that the rest of my business' Macs get upgraded ASAP.

Thanks for the patch Apple!

Eddie71

Level 1

0 points

Sep 26, 2012 7:03 AM in response to MarCoTech

"Thanks for the patch Apple!"

What patch? I'm sure I'm missing something here but I went through this discussion thread and couldn't see what you're referring to.

Sep 26, 2012 9:43 AM in response to Eddie71

Hi Eddie.

MarCoTech is referring to the upgrade Apple (eventually) released August 23rd to 10.8.1, fixing the smb issue amongst other things.

See http://support.apple.com/kb/HT5418

tep74

Level 1

4 points

Nov 19, 2012 9:03 AM in response to PPublishing

I am running Mac OS 10.8.2 and still seeing this problem.

jeyjay

Level 1

0 points

Jan 18, 2013 1:45 PM in response to tep74

This is probably because another service (e.g. afpd/netatalk) is running on the server and this service conflicts with samba service. In this case the avahi/bonjour doesn't broadcast samba service. To fix this, you have to add smb.service to /etc/avahi/services:

<?xml version="1.0" standalone='no'?>

<!DOCTYPE service-group SYSTEM "avahi-service.dtd">

<service-group>

<name replace-wildcards="yes">%h (samba)</name>

</service>

<type>_device-info._tcp</type>

<txt-record>model=RackMac</txt-record>

</service>

</service-group>

bigtoe

Level 1

24 points

Jan 29, 2013 4:34 PM in response to jdunruh

I just resolved this symptom, which in my case was occurring on an unbound 10.7.5 Mac while attempting to mount a share hosted by an SBS 2011 (Windows Server 2008 R2) server. The fix ended up being:

Reset the user's AD password.
Remove the keychain entry for the server.
Reboot the Mac.

Any one of these three steps by itself did not resolve the issue. In the process of troubleshooting I noticed that the issue was specific to the Mac's local user account, the credentials being used, and the resource being accessed. For example:

The user can successfully mount other shares hosted by the same server with the same credentials.
Connection succeeds using different credentials from the same local account on the Mac.
Connection succeeds using the user's credentials from a different (also unbound) Mac on the LAN.
Connection succeeds using the user's credentials from a different local account on the original Mac.
Using the Connect to Server dialog with embedded username/password syntax (smb://user:pass@server) didn't help.

The user had never succesfully mounted the problematic share, and had only recently been added to the AD group which has permissions to read the share. I'm guessing that the user may have attempted to access the share prior to being added to the group and somehow the resulting access denied was cached and persisted after his permissions were changed.

SMB file sharing to SBS 2011 broken?