10.9.2 Mavericks and can no longer connect to our SMB file share on the network.

yep...same story here as well! Been trying all the workarounds. Some work for a short peried but I have iMacs constantly dropping connection to Windows Server 2012. Sometimes we have to wait nearly five minutes for a share to mount...then only to have it dropped within ten minutes. All macs running 10.9.2, except two are now running 10.9.3. all are expereincing the same. Update didn't help, go figure.

It's obviously an Apple issue. PC's on network are humming. Mac's were but not now. My extension is ringing constantly. We need help Apple! and fast!

I'm having the same issues as PleasantSpectrum. The CIFS connects quick but slow speeds. Also, if a mount is idle for even just a few minutes it gets dropped; even with an open file from the share on the server. We are having to "Save As" to desktop, then overwrite once the share remounts. FRUSTRATING! Entire CAD department went Mac this past January from Windows. Started with Mac OS 10.9.1...had far fewer issues than now on 10.9.2.

I have tried the update 10.9.3, but still same issue. Actually seems to have gotten much worse in the last couple weeks. PleasantSpectrum have you installed any Win Server updates in the last couple weeks? It couple be a mix bag of tricks from both Microsoft & Apple???

I'm a bit biased, as the only Windows shares I personally mount from my Mac are on Windows 8.1 and Windows Server 2012 R2 (SMB 3.02). However, I do know that Mac users in my company are also having trouble connecting to Windows Server 2008 R2 (SMB 2.1) systems. The 10.9.3 update has not improved things for me (I'm continuing to use the CIFS workaround); I will need to check with colleagues to find out on the other front, but I'm not holding my breath.

I do keep the Windows systems I'm connecting to up-to-date, but the Windows Server 2008 R2 systems the other folks connect to are more sensitive to downtime, so do not get updated as frequently. Additionally, I do not recall any recent Windows Updates calling out changes to Microsoft's SMB implementations specifically.

IMO this problem is all Apple.

Upgrading to 10.9.3 did not solve the SMB and / or cifs disconnect issues... 😟

...agreed: IMO this problem is all Apple

Thanks for the info PleasantSpectrum. Similar scenario here as well. So far 10.9.3 did not solve our SMB/CIFS issues.

...agreed: IMO This problem is all Apple.

i am running a Macbook with OS X 10.9.2. After weeks of frustration, I could not get any smb shares to connect to my Windows network at my work, until I tried the solution below which worked.

What did not work for me:

Finder --> Go --> Connect to Server --> Server Address smb://servername

Finder --> Go --> Connect to Server --> Server Address cifs://servername

What did work for me:

(I am purposely attempting to describe these steps in very simple terms, because I am not a network guru by any means)

I am running Windows 7 Professional on the PC. Go onto the Windows PC that has network connectivty and find the IP address of the servername you are trying to connect to. Use the cmd prompt to ping the address like this:

Click on the start button, then type cmd into the search box and hit enter. The command window will open up, then type this and hit enter:

ping servername

You'll see 4 messages that say "Reply from x.x.x.x ..." This is the IP address of the servername you are trying to reach.

Go back to your Mac and use the Finder like this:

Finder --> Go --> Connect to Server --> smb://x.x.x.x and press Connect

Then you should get a popup window that says "Select the volumes you want to mount on x.x.x.x". Choose which ones you want to connect to, and then press OK. These volumes shold mount and appear on you MAC Finder listed in the "Shared" area over on the left side of your Finder.

This worked for me, I hope it helps someone else.

The only downside is that I lose all these shares every time I power down, and I must manually reconnect using the same procedure each time I power back up.

offtowork you've made that suggestion before, however using IP addresses instead of names does not solve the problem, from several Macs that I've tried. I'm quite sure the problem you had was not the same as described in this thread...most likely you were using names that didn't resolve properly on the Mac for whatever reason.

offtowork, we have treid it all; smb://*name*,smb://*IP*, cifs://*name*, cifs://*IP*. One will work this hour then looses the connection, then we will try another and it will work for a little while...NOTHING has been the silver bullet.

Getting extremely frustrated that no resolution or work arounds are being offered by Apple. Has anyone gotten a response from an Apple tech? I would love to know what their answer was.

Totally agree. It was working and all of a sudden with the new update it doesn't work.

I'm running a 2011 Macbook Pro and whats weird is that it works for me on a Wired connection (although the speed fluxuated like crazy up and down), but on wireless nothing SMB related works. I've tried all the CIFS, SMB, IP and non-IP server connection options. Nothing works on Wifi.

Something I want to share.

I to am struggling with the SMB issues of Mavericks.

But a few days ago my old router (Belkin) gave the ghost at home. I am a tech hoarder so I grabbed an Netgear WNR3500v2 from the parts bin that fired up.

First I used the standard Netgear firmware on the thing (forget what version etc.). I need to say that this particular Netgear had ISP modified and locked down firmware on it (Ziggo Netherlands). Long story short, the "N Gigabit" part of it was false advertisment. Could only connect via b/g networking and the SMB networking problems where even worse than with the Belkin.

But than I found time to put DD-WRT on the netgear. Although SMB still is buggy it's much, much more stable.

One bug with it kills the joy though. If a network storage unmounts, I can't remount it. Now Maverick claims the resource can not be found anymore, although I can still see it in finder an I can mount it on other Macs on the same network. Takes a reboot to fix the problem.

I don't know what Apple messed up, but they really need to put some human resources on this problem. Just imagine the blood, sweat and tears sysadmins on a large educational network go through to get things working proper for student owning Apple's!!!!!

I cannot believe im just being lucky with 30 macbook probretina and few old mac minis all with maverick able to use smb, ip, to mount shared folders.

I can't believe it either!

But it's a real disaster on the network I work on professionally. At home it's a real nuisance.

And it's not only SMB storage connections, it's screen (desktop) sharing, multi-media streaming, general network stability. I deal a lot with VM enivorments, VM's booted over network are sometimes not useable with Mavericks.

We started to advice people to revert back to Lion or Mountain Lion if possible.

Just received this article in my Inbox today concerning SMB settings on Win Server 2012...i'm hoing to give it a try in the morning.

http://redmondmag.com/articles/2014/05/16/network-performance-problems.aspx?m=2

It must be a Win Server issue, as i never ever had any issue to mount shared drive with maverick.

As i said, i now have 30 macbooks, all works perfectly fine.

When i first saw this thread i had only 10 mackbook so i was not sure if i was just being lucky.

My only issues i had was that i had to put the IP because of DNS problems, it wasn't resolving.

Now i have fix that and it's all good.

I'm 99.9% sure it's not OS X related, so you guys can wait a long time to get help by Apple.

Seriously look at your Win Servers settings.