smb shares on servers inaccessible after mountain lion upgrade?

Getting the same problem

was working fine before upgrade..

running sbs 2011

1 macbook pro (late 2011) osx 10.8

1 imac (late 2011) osx 10.8

when browsing the server it is not showing any of the shares.. but the mapped drives are still working fine and access the files fine.. i cannot access the smb through unc or ip. both were working fine before the 10.8 upgrade

i am not bound to the domain but using the same credentials that the server has in AD which worked fine before the update.

Has anyone tried inbound connections via SMB to a mountain lion system? We have a bunch of Netgear NEO550's that use SMB filesharing to stream media via shared folders (both internal drives and External Firewire drives) on an i7 iMac...and since the upgrade none of them can mount shares from the iMac anymore...

It looks like this is a two way thing...broken when trying to connect to ML as well.

Hey everyone...

I just moved from Windows to Mac at my workplace too, and it was frustrating to see that the SMB does not work...

after days of testing and server log reads, the solution we found finally was:

In Finder, click GO > CONNECT TO SERVER

Server Address: smb://{ipaddress}/share

Enter your work network username and password

Viola! It worked for us!

Hi all,

@nivas37 and everyone, the solution about "knowing" the share name is a work-around AT BEST. The fact of the matter is that SMB networking is severely damaged AND NEEDS TO BE FIXED.

We have 40-50 shares (for example, one for each user) and tons of printers. Not being able to search for a particular share (or printer) is insane…you might as well have to know it's IP address. Furthermore, someone on a Windows machine needs SMB to work properly to mount an Apple share. A new user or someone with a new machine or upgrade is starting to tax the IT staff to the point that they want to either disallow anyone from upgrading to 10.8…or…there have been some who have suggested that we stop supporting Macs altogether.

As I mentioned, this issue goes way beyond just being able to mount a remote volume on a Mac. It is causing problems for people who need to mount a volume on a Mac via SMB and causing problems with setting up printers. A Mac needs to have robust SMB functionality to play nicely in the sandbox with Windows.

Apple…get a !@#$ clue... this needs to be fixed ASAP… Maybe even sooner than 10.8.1 (how about 10.8.0.1)!

I personally should have stayed with Snow Leopard.

Hi @netispguy,

I agree. And I confess that I caught the share name by fluke. I tried half a dozen names before I hit the nail on "/share".

However, the SMB did work smoothly on Lion. The probem appears to be in Mountain Lion... and yes, it calls for 10.8.0.1!!!!

Hi all,

similar problem here on MBP early 2011 (upgraded from SnowLeopard -> Lion -> ML).

First I searched google because since ML my wifi ***** and disconnects after some seconds. All solutions did not work.

SMB-Shares will be disconnected because of read/write errors and a simple ping-to-target did not work. BUT in most cases webbrowsing still works. Deactivating/Activating wifi solves the problem for some short time.

So I thought it could be in conjunction with SMB and the connect-to-suggestions in this thread.

BUT

smb://{ipaddress}/share

smb://{ipaddress}

smb://{name}/share

smb://{name}

-> all works for a short time then disconnection! I tried different Windows- and Linux/Samba-Versions.

The Connection via LAN works fine (till now) and absolutely stable. No problem with Snowy or Lion!

😠😢

hello all,

i do not know if this may be applicable to any of you or it may solve your problems but this is what happened with my case.

i have my imac at work connected with an sbs 2008 server.

after upgrading to mountain lion, some of the server shared folders were not available i.e. missing completely from the folders' lists. furthermore volume(s) that were supposed to open automatically upon logging in, failed to do so.

i then upgraded my version of paragon ntfs s/w which has apparently solved these issues for me.

hope above to assist.

regards,

george

These temp fixes are all great for those of us who understand how to deal with advanced topics...but how do I deal with the majority of users who just want to have the new ML features, but want to continue to have access to the same shares they have been using for the past two major OS releases...?

No they didn't work smoothly at all in lion, I have had nothing but bugs and slow connection time outs, unmounted servers, printer share problems. etc. on lion.

I was actually hoping mountain lion had finally fixed these, and apple had actually done some real coding work here... because I wasn't prepared to shell out another $19.99 for twitter.

Alas not, it's apparently worse... Apple's smb implementation is a joke, and it's a travesty that despite the repeated complaints here, the bug reports and they feedback they 've received, they apparently did zero work for mountain lion.

I'm also having issues connect to SMB servers, however, the problem seems to be related to upper-case characters in the share name (!!!).

The share I was trying to connect is named "WebDesign" (capital W and D) and, in Lion, I could connect just fine. Now I just tried it on ML and I kept getting access denied until I change the share name to lower-case.

I was connecting using Go > Connect to Server... > smb://{ipaddress}/{share}

After spending hours mucking about trying to get me mac pro to share its shares via mountain lion and smb, used a great free program called SMBup. Been using this with all the beta versions and now the retail of 10.8 and it works just fine.

You can see how it works here..

http://knowledgebase.hsti.com/re-installing-smb-on-mac-os-x-lion-10-7-x

I tried so many suggestions,some worked a Short time,but there is still no stable solution.

This OS Release is a joke and definitely Not the worlds Most Advanced OS!!

Every simple Linux can handle wifi connections.....unbelievable.

Same problem. My Teraserver Pro broke on upgrade from Snow Leopard to Lion.

sudo sysctl -w net.smb.fs.kern_deprecatePreXPServers=0 every time you rebooted fixed it in Lion.

Now, in Mountain Lion, this simply yields a: 'Class is not implimented'

Ugh. I understand changes, but abrupt breaks so you can't even transfer data are annoying. I have terabytes of iOS developer stuff on that NAS.

I've asked Apple Tech Support to look into this.

http://www.cultofmac.com/183532/apple-preparing-to-seed-os-x-10-8-1-builds-to-de vs/

Cross your fingers that the fix for our SMB issue is included