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

Level 1

36 points

smb shares on servers inaccessible after mountain lion upgrade?

From my mini, I access some windows servers for data storage, mapping SMB. For some reason, after upgrading to Mountain Lion, I can't get to those drives (shares) any longer.

They are accessible from other computers on the network, and they are even accessible from a virtual Win7 (Fusion) session on the mini. But in the main OS X mountain lion environment on the mini, they are not accessible through any of the usual means (Finder, etc).

I even installed ForkLift and ForkLift can't get to them either.

If I go to GO -> Connect to Server, I get "There was a problem connecting to the server "192.192.192.192". (Not the real IP.)

If I use the existing entry in the list of shares I get "Connection Failed".

Needless to say, noting on the server has changed, and Mountain Lion left the shortcuts/share names/startup connection commands (which used to open the server drives when the mini started up) in tact. But actually connecting and using docs on the server, no dice.

What am I missing?

Mac mini, Mac OS X (10.7.4)

Posted on Jul 27, 2012 7:25 AM

219 replies

OrdsWoW

Level 1

0 points

Jul 31, 2012 2:27 AM in response to nathan_h

Same issue here,

MBP17' 2009 upgrade , MBP17' 2012 new install and Imac 27" upgrade , same story. map / nothing else.

I cant open in finder my whs 2011, as the picture shows parallels with w7 works fine.

the psf network connection to my osx hd works ok. So i got a work around.

But please we need a fix.

g_pirtle

Level 1

45 points

Jul 31, 2012 6:16 AM in response to OrdsWoW

A guy in our office has a MacBook Pro that is not bound to AD and uses a local account and he is getting the same errors. All Macs bound to Active Directory do NOT have any issues connecting to smb://serverIP or through the Finder -> Network.

g_pirtle

Level 1

45 points

Jul 31, 2012 6:56 AM in response to g_pirtle

Additional Info - I found that trying to connect to our 2 host failover clustered storage array (2 ea. Dell NX1950s w/MD3000 storage array) via Go -> Connect to Server and through Finder fails with the same error you guys are experiencing. All my other SMB shares work.

Jul 31, 2012 10:51 AM in response to nathan_h

Same here, ML fresh install, bound to AD using Centrify, can reach shares via AFP but not SMB.

OrdsWoW

Level 1

0 points

Jul 31, 2012 11:10 AM in response to nathan_h

Update on my previous post 4 up.

Same MBP17" 2012 now NO issue's, whs 2011 at my holliday adres. Can some1 tell me how to debug this to help myself @ home and you guys.

Jul 31, 2012 11:25 AM in response to huff92653

smb://IPADDRESS/SHARENAME works

SMB://HOSTNAME.DOMAIN anything does not work

g_pirtle

Level 1

45 points

Jul 31, 2012 11:39 AM in response to huff92653

smb://hostname.domain brings up a list of available shares for me on most Server 2008 R2 file servers except for 2 servers (shares through Failover Cluster Management). On those two servers, all I get is a "/" through Finder and cannot connect through Go -> Connect to Server.

Jul 31, 2012 4:39 PM in response to g_pirtle

I work for a NAS vendor and we've had some customers report this issue to us. My analysis of it, so far seems to indicate that Mountain Lion is behaving differenty than Snow Leopard and Lion in the total amount of data it will accept from the SMB/CIFS server for the list of SMB shares sent to it from the SMB server. (nerd speak: I'm pulling this from the MaxDataCount field in a network trace)

Snow Leopard accepts 16KB
Lion accepts 16KB
Mountain Lion accepts 2KB

When the server tries responding to Mountain Lion with more than 2KB of data, it fails, because Mountain Lion has said "hey, I can only take 2KB of data for the list of shares." Mountain Lion knows that the server couldn't respond with the shares, so it goes back to the server to get the share list a different way. It uses an older method to get the share list and it seems like this is not fully supported by every SMB server out there. In particular, I know that Windows Server 2003 R2 and Samba seem to support this alternate method, but Windows 2008 R2 does not. So, for the servers that can't respond to 10.8 with the share list at all, 10.8 errors out and you see that error in your Finder when you try to connect.

My feeling here is that this 2KB limit is a bug in 10.8. I'm going to open up a bug with Apple via Radar. Maybe it'll get fixed in 10.8.1.

nathan_h Author

Level 1

36 points

Jul 31, 2012 4:44 PM in response to Bernie Case

That's great info. Sort of. I mean, the only solution then for someone like me, with all my network drives on a Win7 machine is.... get a different OS on the server, or roll back to Lion, for now.

Or is there a way to tell Win7 to send less data?

g_pirtle

Level 1

45 points

Jul 31, 2012 5:17 PM in response to Bernie Case

So in theory, that is why my servers with only a few shares will show me the list, but my main storage array with 20+ file shares will not connect unless I specify the share.

Jul 31, 2012 5:46 PM in response to nathan_h

nathan_h: Your options are to:

reduce the total number of shares you have, or the names of the shares that you have, so that the full list will fit in a 2KB reply from the server to the 10.8 client
use a different SMB server like 2003r2 or Samba
suspend use of Mountain Lion and use Snow Leopard or Lion until Apple patches Mountain Lion's SMB client.

g_pirtle: as far as I can tell, you're correct, but I'm going off of packet traces to try to infer just what Mountain Lion's doing here. That's the one thing that sticks out to me and some of my other colleagues.

nathan_h Author

Level 1

36 points

Jul 31, 2012 5:58 PM in response to Bernie Case

Hmm. I only have three shares, and their names in total are less that 50 characters. You're saying if I cut it down, that will help? I'm guessing since each share has tons of folders inside, just changing the top level names won't help me?

Jul 31, 2012 6:02 PM in response to nathan_h

nathan_h: that sounds a bit different than what I've seen in my environment and in my tests. Your issue sounds somehow different. More investigation (like, a network trace) would be needed for me to be sure it's the same issue. There might be cause for you to try to open a case with Apple to get help, or to use the workaround of connecting directly to a share, i.e. smb://server/sharename. If the workaround doesn't work, then you're definitely seeing a different problem.

nathan_h Author

Level 1

36 points

Jul 31, 2012 6:16 PM in response to Bernie Case

okay, i guess i'm seeing something different. hmmm. my vmware win7 instance on the same box gets to the shares fine, still, and Lion had no trouble from the Mac OS. i'm stumped.

OrdsWoW

Level 1

0 points

Jul 31, 2012 10:23 PM in response to Bernie Case

Thanks, my feeling say's your right.

I got 2 servers running.

1 at @ Home with shares 25 shares. reply's with a map /.

2 at @ holliday adress with 14 shares. reply's full list of shares.

Next week , i am home again and will reduce the shares 1 by 1 and test it.

smb shares on servers inaccessible after mountain lion upgrade?