smb shares on servers inaccessible after mountain lion upgrade?

I just got a new mac mini with ml server installed and I am having the same issues with smb. I have found that if you turn off file sharing and turn it back on it seems to fix the problem. I agree with all above that this is not a real fix for the problem. I have an applecare plan and have talked with the server guys and they are aware of the issue, but who knows if they will ever get it fixed.

Just like what I said long time ago. And still works. Apple should look at why this works and work from it.

"

Keigotw

Before updating to ML, I could access the windows 7 share folder on the network. After updating to ML at 1st I could access it. While copying files it would cut off and then it won't connect to share folders anymore.

Today I updated to 10.8.1 . After update it still won't connect to share folders. So I removed the share from Windows 7 and reshare it again. Now it all working fine"

jd1573 wrote:

I just got a new mac mini with ml server installed and I am having the same issues with smb. I have found that if you turn off file sharing and turn it back on it seems to fix the problem. I agree with all above that this is not a real fix for the problem. I have an applecare plan and have talked with the server guys and they are aware of the issue, but who knows if they will ever get it fixed.

HOW TO FIX:

1. Make sure your clock on the Win7 server has the correct time! Have all of your machines get their clock settings from a reliable NTP server. I had the same issues, and fixing the clock fixed the problem.

2. Fix the Win 7 network nonpaged pool resources! Instructions here: http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

Check the EventLog on windows to check for error: 2017 This is the nonpaged pool error.

Good luck everyone! These things fixed the networking issues over SMB that I had.

This works for my Windows 7 machine but not Vista. Oh well I am part way there.

We had this problem with a Win XP machine serving 3 shares. After years of daily use, it suddenly stopped connecting with all of our Macs running OS X 10.6 and 10.7. We didn't have a 10.8 machine running to test at the time. The one old Mac running 10.4 could still make the connection. All the non-connecting Macs would get a request for user name & password, but they would always get rejected, so I knew the computers were talking.

The Win XP machine is located in a different physical location, so I had someone check the date and time and found out the date was incorrect. It was set forward by a month. Someone must had inadvertantly changed the date. Once that was fixed, everyone could log in again.

Hope that helps someone.

Hi everyone,

Did not read the 14 pages, but as the latest posts seem to still debate on the problem, here's what I can tell.

The problem you're experiencing is a fairly common problem. It is caused by the decision of the Samba debeloppement team to restrict the use of it's code under the GPL L3 license agreement. Thus, it's implementation into Mountain Lion isn't possible without some licensing problems.

This is why Apple decided to abandon the integration of Samba based on the tools provided by the Samba team and to develop it's own... which leads to some compatibility problems.

There are some Samba ports to MacOsX that should allow you to re-install the standard Samba version.

The more advanced users can try to install it using MacPorts. Will require some skills.

Others may want to take a look at SMBUP (just search it on macupdate.com).

Yes, that is an inelegant way to fix problems, and yes, you're bound to the development of the projects. And for each major, or even minor, update of OsX, you might be expecting issues as Apple doesn't give s s*** about those developments and changes everything from a version to another, with no other obvious reason to force developers to change a lot in their code :-(

But if that allows you to share your content... it's worth a try I guess :-)

Regards.

Had this problem that has been described by so many on various set ups. Basically, I was just trying to connect to a Windows 7 64bit workstation as I had shared files on it. Worked until the ML updates. Have to say I did read through all 13 pages of comments until getting to Helios' post above. Changing the 2 registry keys "seems" to have fixed this for the time being. I'm able to connect to the shares on my Win 7 box.

I'm having the same issue but it's also with AFP shares. I upgraded to ML just a few days ago and all was well up until yesterday afternoon. A mounted share just dropped and I could not get it back. I thought it was just with that server, restarted it and upgraded to 10.7.5, but this morning I cannot connect to any share on any server. Tried logging in as a different user, cleared out KeyChain entries, cleared out system and user preferences, Reset SMC on my Macbook Pro. Reset PRAM. Nothing has helped.

if you're rejected by authenticaion failed, Please keep in mind:

windows system time must not differ to your mac OS X's.

That's how I fix the problem. 😍

Hi,

As I wrote in a previous post : if SMB sharing on a Mac is essential to you, just download and install SMBUp.

It's free. It installs easily. It replaces the SMB sharing of OsX Mountain Lion. And it works like a charm !

5 minutes to get it up and running. And if it does not work, there's an uninstall feature that will turn evrything back to the standard OsX version.

But what about the AFP shares that are doing the same thing. Do Mac servers have the same time condition?

windows system time must not differ to your mac OS X's.

WOW! worked!

Holy crap what a pain!!!! I am new to mac but i am a windows admin. Here is how i got it to connect to a windows server 2008R2. First i tried everything on this thread except for the 3rd party stuff. i finally started playing with the address again and this is what worked for me.

smb://192.x.x.x:username

note some things i changed and didnt change back was the netbios name

just thought i would share and hope this helps someone.

I have to use my mac with a book and google close by as i have only had it for less than a week. Okay i am off to tackle all the rest of the items that dont make sense to me and or dont work :-)

ilgfo wrote:

smb://192.x.x.x:username

That syntax does not make any sense.

smb://DNSname or

smb://DNSname/Sharename or

smb://user@DNSname/Sharename or

smb://user:password@DNSname/Sharename or

smb://IP_Addr or

smb://IP_Addr/Sharename or

smb://user@IP_Addr/Sharename or

smb://user:password@IP_Addr/Sharename

Alberto, hello fellow italian!

I understand it makes absolutely no sense - i am puzzled and i am not BS'n.

My scenario last night trying SMB was at home over a hardware VPN back to my office.

The syntax i used was the only one that worked, i swear on my daughters life. i havent rolled backwards to my original config to try and break it but here are the changes i made on my mac last night.

1. Tried every smb syntax possible with no luck

2. I went to my wireless adapter and added my internal DNS server as secondary DNS, primary is my ISP

3. I added my domain.local to search domains in the same tab

4. I also changed the netbios name to a shorter version and under workgroup i used my netbios domain name.

tried syntax again with no luck and started playing and the one i mentioned work. I will gladly post a video if ya dont believe me. When i get some spare time i will roll all settings back and disect this and post. There are alot of posts that make zero sense to me here. Now if someone can tell me how to hack activesync to connect to exchange 2003 on my mac i would be in heaven! We are not going to Exchange 2010 until last quarter of this year :-(

Arrivederci!