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

Thanks DavidH. We do use Filemaker Server in general and share that way. However, there are a few single-user databases that we open over the network despite recommendations to the contrary. We've been doing it this way for 15 years with no ill effect! These databases are strictly one-user-at-a-time solutions, so it has never been an issue.

Thanks for the explanation regarding Local Network Users. As I mentioned, all users were created at the server using the Server app. I think what happened is that we turned on Open Directory recently (we weren't using it before); all users created prior to turning it on were Local Users, all users created after turning it on are Local Network Users. Sounds like I should convert everyone to a Local Network User by deleting and re-creating their accounts.

Thanks for your time.

dwbrecovery, if your question was directed at me, the answer is no. I don't think we need perfmode, as our use is pretty low-demand, and we rarely put any strain on the resources.

I was responding to the original post and checked that perfmode has not been suggested.

My observations have been that both AFP and SMB are more reliable with perfmode enabled whether on heavy or low demand Servers. Maybe something to consider.

Well, Pretty much have given up hope that this will be fixed any time soon. After my last update we are now seeing file corruption take place when printing PDF documents using Adobe Acrobat XI Pro from a windows computer and saving the file to a Mac OS X Server SMB share.

Continue to see Errors of unsupported attributes in the logs when this takes place. File locking of Office files is finally not a daily issue but data corruption is, at least for me, a show stopping issue. I will be looking at moving to 'something' else. I'm just not sure what that will be yet...What a sad dissapointment from Apple.

To everybody who has trouble with SMB filesharing and want it fixed:

- FILE A BUGREPORT at http://bugreport.apple.com

- send feedback by every possible way to Apple for example http://www.apple.com/feedback/macosx.html

- conntact jounarlists of computer magazins and explain to them this problem, it is a fact that SMB sharing is not in any case in a shape that allow use in a production environment.

If we want it fixed we have to be heard - so we have to make noise - if we are still not heard we have to be louder. ;-)

Bye,

eweri

P.S. In a month I reach my dead line - than I will be quiet

Anyone brave enough to run 10.9.4 yet? I am out of "volunteer" servers, for now...

I did it (as I can't use Mavericks in its current state, so I jump on the new builds as soon as they come out). Unfortunately, no change for me. AFP, when put-to-the-grind, is still a flop. Attached images show the brutal drop in speed between Mountain Lion Server, left, and Mavericks Server, right (using the exact same hardware, network, drives, etc.). No way we can use Mavericks Server with a performance hit like this...

k.

These are just a couple of screenshots of the numerous tests I run each time a new build is released, comparing Mountain Lion Server to Mavericks Server for AFP performance. I'm testing via a dual-boot 2009 Xserve with 24 GB of RAM, nothing running but File Sharing, OD and DNS. I've tested via both clean installations of Mavericks Server, along with upgrading from Mountain Lion Server > Maverick Server. The only thing different between the two OSs, in terms of hardware, is the HD the OS itself is running on (both identical drives, server/enterprise grade, in bays 1 & 2 of the Xserve—but, I have four of these drives [the second pair is incase of a drive failure, etc.) and I've swapped them around to rule out a bad drive). The AFP share is actually running on a separate drive from the OS (thus, it's the same actual drive being tested each time, even though the OS drive is different—I've also tried using the OS drives as the AFP share location, and it's not made any difference).

k.

Hello!

Just got an email from my customer, he pulled the plug and orders to change his network to windows server and clients.

After 10.7,10.8 and now 10.9 you were not able to give us reliabel SMB file sharing, thank you Apple.

Gave it as long as I could, but problems persisted, so I've moved back to our Xserve with 10.6.8 on it for our file server. Will not repurpose the Mac-Mini & Pegasus RAID for the time being, hoping against hope that Apple will get its act together on this.

But I am becoming convinced that Apple no longer cares about the office server market as they are more interested in moving everyone to the cloud with 10.10 this fall. Fine for home users, but not practical for offices.

Anyone else give up on Apple's 10.9 file server software, and if so, what did you move to for a Mac & Windows network?

Well, my client moved to Google Docs but had to move back after a month as Filtering is unusable in Google Sheets.

Within 2 days I've received a very frustrated phone call saying that all he wants to do is open a spreadsheet, have it open for more than a hour, save it and let someone else open it..

Not too much to ask for..

Even with the latest updates, this STILL isn't the case.

File is opened, the connection drops? hangs? disconnects? and nobody is able to use that file, not even the person who locked it.

Hello pottrell,

So I just tested it from my 10.9.3 client, using Microsoft Excel 14.4.3 with a simple spread sheet saved on my Mac OS X 10.9.3 Server share running Server 3.1.2, connected to it with my Network User account. I had the file open now for over an hour and no disconnect from the server share point and I can still save the file.

I also have a Windows 8.1 client (with all the latest software updates) running, and I opened Word 2003 (yes, I know it's an old one), and created a file tried to save it to the server. The thing is that it wouldn't let me do it when I went to My network and then clicked on my ld-macmini and tried to pull up the workgroup share. Don't know why, but it stalled. But I mapped a network drive of that very same workgroup share folder, and was able to save, read back, edit and safe again just fine.

Now I am not saying that these latest versions are without problems. But for me they are a whole lot better than what they were. Even though I believe that software that is release for production should work 100% of the time without growing pains and flaws. That's just my believe.

I still have issues where for example I can no longer access my mapped network drive from the server. For example my Windows 8.1 client is connected via Wifi. If and when I restart the router, and it comes back on line, most likely the network drive will no longer work. I have to go in and delete that mapping, and then create a new mapping. Very strange but true. Again, didn't say there were no problems. But it is better. Maybe by release of Yosemite and Server 4 they will have it all worked out? Keeping my fingers crossed and I will have a full functioning clone of my server and clients before I will attempt any upgrade to Yosemite 🙂

Martin

I had a number of issues trying to get SMB working in a mixed windows/mac environment using a mav server.

I didn't have trouble on my home mac server and realised that it had the shares set to guest access allowed.

After changing the business to guest access allowed it seems to have reduced the calls i have been getting a lot.

Not sure if its an Auth thing causing problems? I know this isn't a great solution for business that need to lock down files but got me out of the sticky.

Would be good to see if anyone else has seen this.

Simon

It seems that this issue is still present in 10.9.4.

Hi, I have a workaround for this at: https://profallangarcia.wordpress.com/2014/07/08/how-to-setup-a-file-server-on-m ac-os-x-mavericks-that-actually-works/

Hello allangarcia_!

Does it work with OpenDirectory accounts? If not - its a bad workaround.

I think this week I have to change the next business customer from OS X server to Windows 2012 server. Its a shame.😟

Bye,

Christoph