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

Reply
219 replies
Sort By: 

Jul 27, 2012 7:46 AM in response to nathan_h

I haven't upgraded to ML yet, usually wait till the dust settles, but I have a suggestion.


Are the smb shares username/password protected?


If so, GO -> Connect to Server, try it this way for the server address...


smb://username:password@192.192.192.192


When I went from leopard to lion, this seemed to work on everything, the windows smb shares and solaris (unix) ones.

Reply

Jul 29, 2012 11:59 AM in response to lepling

I have issues also.


With a samba share on Linux, ML can see it correctly, but on my Windows Home Server 2011, if i do smb://"server address" i receive and error saying that the share dows not exist on server. Before on Lion i had a list of my shares. On finder the Server apears with a "/" which i can not open.


If i do smb://"server address/share" is works correctly, but i would like to have tha before behaviour. Besides this the only issue that i found after upgrading is the WHS 2011 Lauchpad could not sign in (before in Lion was working).



Any ideas on how to solve this?


Reply

Jul 30, 2012 3:59 AM in response to nathan_h

This is also not working for us after upgrading to Mountain Lion. As above, typing "smb://[server]/[folder]" works fine, however typing "smb://[server/" gives the share does not exist error. Hope this gets fixed as this is something we use to view all available shares on a server.

Reply

Jul 30, 2012 7:34 AM in response to nathan_h

I also seem to be having the same/a similar issue.


If I connect to smb://server/ it will not connect.


If I connect to smb://server/share/ it works.


Once connected to a share, if I click on the server in the 'Shared' section of the Finder sidebar I get a single folder named '/'

Reply

Jul 30, 2012 9:11 AM in response to nathan_h

Just wanted to let you know that I am not experiencing any issues connecting to SMB shares, but I am bound to an Active Directory domain. Both methods are functioning as they should - Finder -> Go -> Connect to Server -> smb://0.0.0.0 and Finder -> Go -> Network -> Select Server


This isnt particularly helpful, but it does work in certain situations.

Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

smb shares on servers inaccessible after mountain lion upgrade?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.