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

I believe this is a different issue caused by the lack of a recovery partition on a RAID array

That is strange, because no RAID in this configuration.

Sry for bumping in, but still on 10.9.1.. Still having the share problems.

When booting, disconnect and re-login, go to file shares on server, after that it finally works.

In our company, we get anoyed about htis.

can you please confirm, 10.9.2 fixes this problem? I hope so. So we can finally work normally again...

Thanks...

HESSIE, our issues are gone using the developer seed of 10.9.2. The only remainder is the attr error messages on console, that are pretty much harmless.

Thanks... that was the info I needed.

So far I see no change in 10.9.2. Still crashes.

I don't have access to 10.9.2, so have no opinion on that.

however, the current solution we have is restarting our Mac Pro 1 time per week - this has greatly lessened our issues.

To recap:

We have a Mac Pro file server running 10.9.1

10 XP clients (tethered image capture stations), 20 Mac clients (our workstations)

After upgrading to 10.9, the XP clients started to lose connectivity to the Mac Pro.

Dropped connections on large (1-10 GB) transfers, unaccessible shares.

Turning on Guest access on the Mac Pro would make everything work again, for a couple of days.

A reboot of the Mac Pro brought it all back to normal (reboots of the XP boxes did nothing).

The Mac clients (10.5.8 through 10.9.1) have had zero issues.

Incidentally, we installed a Windows 8 machine on the LAN last week, and have had no issues with it at all.

Same issue on 10.8.5 and Server App 2.2.2

Seems the issue still occurs on the Server 2.2.2 and also on Mountain Lion. Not only an Mavericks issue!

How is the status of the issue?? Is Apple fixing that issue or what I think they are ignoring that stuff!

I also called apple support about that issue and they don't really have any idea what's wrong! (They think some hardware issue with the windows 7.... But I think that's only a joke because they thont know what's going on!)

So no solution???

Anyone testing 10.9.2 dev seed + Server 3.1 dev seed yet?

Yes, testing this combination (10.9.2 and Server 3.1) on two machines. Running build 13C44 of OSX on both.

Beware, there is an earlier build of 10.9.2 floating about.

The system seems stable as a server, however the SMB log entries are still there:

Jan 28 10:29:39 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:39 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:39 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:29:39 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:39 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:39 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:49 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:29:59 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:59 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:59 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:29:59 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:29:59 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:29:59 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:30:08 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:30:08 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:30:08 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:30:08 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:30:08 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:30:08 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X40000, file attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0 time attrs

Jan 28 10:30:09 mfg.cdvinc.com smbd[286]: File system does not support 0X0, size attrs

A bug report update has been sent with dumps, etc.

This both systems are recent Mac Mini with Promise RAID on Thunderbolt with mixed Win7 and XP clients. Much of the traffic is MS Office applications.

Occasional complaints in the log about name servers:

Jan 28 09:49:46 mfg.cdvinc.com netbiosd[154]: name servers down?

Does not seem to be correlated with the SMB entries.

Also, user complaints are much lower than before. Still too early to tell if this is progress.

Since OS X Server Mavericks we have also serious filesharing problems with all client systems. XP, Windows 7 and Mac clients disconnect several times a day.

This causes save errors on open files. Permanent locks of Word an Ecel files. Sometimes the user rights seem corrupted.

This makes the server unusable. We tried different ways to fix ist, but no success.

Apple shoud fix this asap because no one can use such a unstable fileserver for production environment.

This time we are forced to migrate our files to an emercency replacement system running windows 7 to keep our daily work alive.

Thanks alot for sharing your experiences!!!

I was just about to order a new Mac Mini with Mavericks server, but now I will continue to follow this thread and wait untill these problems are solved before I order anything. 😟

(we have a mixed environment with both windows 7, and osx clients at the office and are currently running a very stable Snow Leopard Server, though 3 years old and we need to upgrade very soon )

jonathanoee wrote:

I was just about to order a new Mac Mini with Mavericks server, but now I will continue to follow this thread and wait untill these problems are solved before I order anything. 😟

I really, really hate to say this, but right now that is the best idea if you've got WIn7 clients on your network.

Our 10.6 server died abruptly and we were forced to rush out and buy a new one with 10.8, and things have not gone smoothly for the Windows users in the building. 10.9 has fixed some problems with 10.8 that made it literally unusable (I had disabled SMBX and installed Samba as a workaround, but that made user management a pain in the butt), but I'm really hoping that 10.9.2 will iron out these SMBD lockups that are the remaining source of complaints.

Fingers crossed.

I just wanted to go on record to say that I'm having the same issues. Mac users (Mountain Lion clients) are randomly being disconnected. Office files are locked as well as Quark files that say they are open by another user when they're not. Windows 7 users unable to connect which can be resolved by killing the smbd service on the server.

I'm hopeful that 10.9.2 will fix. I am in fact on hold for Apple Enterprise support at the moment hoping to get some idea of when it will be release or if there are any other things I can try to resolve the issue. I'm seriously considering downgrading to 10.8, but I don't have any experience with that OS and don't have any idea if I'm just opening up a new can of worms by downgrading.

Here goes the OSX Server ...

I had a well running OSX server on 10.8. First of all, beeing forced to buy a new version of the server software should have been something apple could have told me in advance (here, free mavericks ;-) but now you have to pay as the old server component will not work ;-)) Not a big deal, but nice to know in advance.

Filesharing after the upgrade and purchase is a joke. AFP and Samba are very unreliable and best of all:

Apple kicked FTP support.

Users can't login to different folders anymore.

If someone could give me an understandable explanation for all that, i would be very thankful.

It is horrible to tell you customers to get a mac because it's all easy and it just works if afterwards you have to charge them countless hours to get all the messed up things working again.

In the end it will prevent people from upgrading, at least it will for me.