Apple Event: May 7th at 7 am PT

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

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

Apr 12, 2013 9:56 PM in response to nathan_h

So here's what I've got.


I installed ML to an external USB disk to test out before installing it to the internal drive in my Macbook. My Macbook is currently running the latest, fully patched version of Lion and can connect to shares on two different windows 2008 R2 server successfully. I can also connect to the shares on both of the server from a Windows 7 PC and a PC running Lubuntu.


When I reboot my mac into the ML disk, I am completely unable to access the shares on both of the 2008 R2 servers. When I try to connect, I am *immediately* greeted with the "There was a problem connecting to the server 'XXX.XXX.XXX.XXX'." error message.


I've tried all of the syntaxes I can find in the "connect to server" box with no luck. I've made sure that the time/date is correct between all of the systems. I've made sure every system is up to date and rebooted all of them (both 2008 R2 servers and both Lion & Mountain Lion). I've attempted to connect through clicking on the server in the right hand pane of finder then clicking on "connect as" without any success.


Anyone have any other suggestions?

Aug 6, 2013 12:57 AM in response to Toomuchairplay

Toomuchairplay wrote:


Hi Bernie,

I know this is an old thread, but it really is the only one I can find that is vaguely relevent. I just upgraded a machine to ML from Snow leopard and I am now unable to to access shares for backups from my NAS, a netgear readynas duo NV2. This seems to be an smb issue. Any advice would be most helpful.


Cheers

Noah



Hi Noah,


Are you sure this isn't your issue? Are you sure you're connecting over SMB and not AFP?

http://support.apple.com/kb/HT4700???

http://www.macwindows.com/TIP--Connecting-to-older-AFP-NAS-devices-with-Mountain -Lion.html



With the SMB problem I coldn't get any of the suggestions in this thread to work for me. I did find a 3rd party app thata solves the problem though:


http://www.thursby.com/products/dave.html


There is a trial version available which you can apply to download on their website here:

https://store.thursby.com/evaluations/dave10.html

Aug 6, 2013 9:59 AM in response to Paul Littlewood

Yup deffinitely SMB, the protocol it is using is Windows Archive Bit. Just as a test I disabled SMB sharing and it won't even accept the connection test. On turning back on SMB sharing it works perfectly. Right now my problem is fixed by just rolling back to Snow Leopard using time Machine, but I'd much rather get things running on ML. I had waited to go to ML to preent just such problems. I wonder if this will be fixed in Maveriks.

Sep 19, 2013 11:41 AM in response to KasperFH

Well, not sure what happened but I updated to latest ML 10.8.5..... Prior to this although it never worked with SMB I could still see my MAC on my network. I was hopeful after reading about the update, Apple would finally fix the nagging bug relative to SMB. Now, after update- MAC has disappeared from my network. I can share from the MAC to my W7 PC w/out a problem. I have set all the various sharing preferences but it appears SMB is still broken.

Nov 5, 2013 7:47 AM in response to RTR15

I am using FTP as my workaround for the network connection error "The version of the server you are trying to connect to is not supported" in OS10.8.5. This is the only workaround I have found that does not require a third party application (MUComander or Thursby).


Fortunately, my server will accept FTP connections and OS 10.8.5 will make an FTP connection and mount the share on the desktop. To add insult to injury, the FTP connection is blazingly fast, much faster than SMB ever was. I'm not sure when OSX added FTP to the Finder but it sure is helpful now.


ftp://192.168.1.1/ or ftp://sharename@192.168.1.1/


ftp://servername/ does not work for me. I must use IP address.


For full background, I get the "not supported" error on three differentl 10.8.5 clients when attempting to connect to an old server share via SMB, AFP, or CIFS, regardless of syntax used. All nsmb.conf and smb.conf hacks have been tried with no success. SMB and AFP work fine for the rest of our OS10.6 network.

Nov 16, 2013 7:07 AM in response to nathan_h

Still frustrated by Lion/Mountain Lion not letting you access your NAS? Try using an alternate file manager. mucommander works just fine in OSX, and it's free.


Yes, it's a separate file manager from Finder, not ideal ... but it certainly beats my having to boot virtual Win to access my NAS.


Try it http://www.mucommander.com/

Install is quick, then go to smb servers, find your NAS, and it all just works.

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 ID.