You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

Server File Sharing unstable on mac and windows network on Mavericks and OSX Server 3.0

Since I've updated our mac mini server from Mountain Lion and OSX Server 2.X to Mavericks and OSX Server 3.0 we are having sharing issues with Windows (7 and 8) and OSX Mavericks users, not being able to access files on the mac mini server.


What I've notice is that OSX Serer 3.0 stop working and I have to restart the Mac Mini Server to make things start working again.


This was not happening with Mountain Lion and OSX Server 2.X.


On the Windows and OSX users what happen is the computers keep trying to connect to the server and are not being able to open or copy files. Again this is intermittent, and I suspect it might be a OSX Server bug.


Any one having the same problem or can give us and advice would be great help.


Thanks.


Andre Tenenbaum

Mac mini, OS X Server, with OSX Server 3.0

Posted on Oct 31, 2013 8:36 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 3, 2013 12:01 PM

I have the exact same set up (Mac mini running OSX Server 3.0) and have been having lots of issues since upgrading. I have not been able to sort out if the issues are on the Server side or the client side, but after a couple of hours, both Windows 7 and OS X clients lose connection to the server. I have been unable to determine the cause. Rebooting the server does help, but obviously that is not a workable solution. Now that I think about the frequency of occurence, I'm wondering if it has something to do with TimeMachine backups running on the server? I may try turning that off on the server and see if that helps (although, again, that isn't a good solution).


I'll just say, I am regretting upgrading everything. I had been hoping Mavericks and its use of SMB2 would fix other issues I was having with Windows 7 machines accessing shared folders on the server, but instead, it has unleashed a slew of problems for both Windows and OS X clients. It is very frustrating since there does not seem to be any rhyme or reason to why connection to the server drops. Hoping there is a fix on the way. All in all, switching from a Netgear ReadyNAS to a MacMini server hasn't really yielded the improvements I had hoped it would.

290 replies

May 13, 2014 8:57 AM in response to Patrick Savelberg (Private)

@Patrick, AFP is "broken" in that is can no longer sustain high-bandwidth network transfers. You can some of my original testing via this thread, but the long story short:


- Via 10.6 Server, our AFP network read/writes, on average, are 95 MB/s reads, 70 MB/s writes.

- Via 10.8 Server, our AFP network read/writes, on averaige, are 95 MB/s reads, 95 MB/s writes.

- Via 10.9 Server, our AFP network read/writes, on average, are 40 Mb/s reads, 95 MB/s writes.


I haven't updated the thread posted above, lately, but for my continued testing (when Apple was responding to my bug reports), I ended up taking one of our Xserves, along with a Mac mini, for dedicated testing. The Xserve is dual boot between 10.8 Server and 10.9 Server, so the same hardware, network, client, etc. is used for all testing at this point (and, via Apple, my testing now includes a wide range of tests, from manual clocking of 10 GB dmg files right up through a whole series of command line and GUI-based network speed testing tools). Across the board, the results are always the same—toss 10.9 Server into the mix, and high-bandwidth network transfers can't be sustained.


For less intense network transfers, this issue is probably never seen (as it takes about 45 seconds before the network transfer hits the wall then drops to a crawl), but with high-bandwidth transfers, it's unbarable. And since high-bandwidth network transfers is required, for us, I'm unable to upgrade to Mavericks Server knowing our transfer times would take twice as long as they do now. I've been dealing with this issue for almost two months now (at times, running tests on a daily basis, though now, I've pretty much given up on Mavericks Server, only testing when a new seed has been released, and have moved-forward with Mountain Lion Server, since I don't need SMB support).


So, that's what I mean when I say AFP is "broken". 8)


Also note: From my testing, this actually seems to be an issue with Mavericks Server, as using Mavericks client or Mountain Lion Server or Mountain Lion client (or earlier client/server versions), there are no issues. It's only when adding Mavericks Server into the mix does the issue present itself.

May 13, 2014 10:44 AM in response to Patrick Savelberg (Private)

Yea, I've run that too. Just did it again now (I use the 10 Gigabit Ethernet network setting, just to raise the cap up to 110/increase the files transfer size to 3000 MB as the 300 MB test is too short to get accurate results on my network). Using Mavericks client (13D61) as the source, I get the following results.....zzzzzzzz...sorry...I feel asleep there waiting for the Mavericks testing to complete (I lie, I actually stopped the x10 testing on Mavericks early because it was taking so long and I needed to get back to work...)


Mountain Lion Server = 94.1 MB/s READ, 99.9 MB/s WRITE (average of x10 tests)

Mavericks Server - 35.7 MB/s READ, 91.4 MB/s WRITE (average of x5 tests)


Pretty much consistent with my previous tests. With Mountain Lion Server, my limiting factor is my network (as I max out the gigabit ethernet, when taking into account AFP overhead). With Mavericks Server, my limiting factor is Maverick Server, dropping the READ speeds down from 94.1 MB/s (Mountain Lion Server) to 35.7 MB/s (Mavericks Server).


I was using Mavericks (13D61) for the client in both tests, so, again, this points to a Mavericks Server issue (versus Mavericks client).


What kind of drive is in your server? Is it a single 5400? 7200? SSD? RAID? It's possible your speed limitations are a result of your HD (but, that's just a guess).


Thanks,

Kristin.

May 13, 2014 11:43 AM in response to Patrick Savelberg (Private)

You don't need to have a 10 Gigabit Ethernet network to run that test in Helios—select a 10 Gigabit Ethernet network just changes the testing parameters. For example, the Gigabit Ethernet network, you're only testing a 300 MB file transfer—that's too small a file for my testing and doesn't give accurate results for our environment. Switching to the 10 Gigabit Ethernet network setting just changes that to a 3000 MB file, which is a little better (though, in my actual testing, I'm doing 10 GB and 30 GB file transfer tests).

k.

May 16, 2014 3:51 PM in response to André Tenenbaum

10.9.3 so far seems to have solved at least some of our problems, It has only been out publicly a day or so but I have seen a lot less noise in the log and have not had the file locking issues with MS Office that we were having daily prior to the update. I hope that they have nailed this but I am very cautiously optiomistic at this point. If this Isn't fixed I will likely spin up a VM of Linux or Windows server to take over filesharing duties and use the mac as Hypervisor/Storage.

Server File Sharing unstable on mac and windows network on Mavericks and OSX Server 3.0

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