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

Yes. 100% minty fresh clean install of Mavericks OS followed by clean install of Server. Same issues.

Hi

i'am facing same issues with my imac since the installation of Mavericks. A windows 8.1 Client is even freezing while copying files from the Imac smb Share.

It feels like being in the eigthes , not having a working file sharing.

Since this is not the first time, having smb troubles, i am considering, buying a NAS. Maybe serving better for the two worlds osx and windows.

Cheers

Ralph

Hello!

Just to summerize my experiences:

The smbd in Mavericks (and Mountain Lion) seams to has some serrious issues.

1. Windows Clients can not connect or loose connection at random

2. Somtimes Windows Clients can not write to a file share they wrote to a few seconds ago

3. The same could happen with Maverick clients when they connect to each other via smb (the default protocol for Mavericks) - if you connect via afp the problem is gone

4. Looks like Mountain Lion had this issues and Mavericks makes it worse.

5. When this happens is unpredictable

This looks like a rotten access right handling in the smbd of Mavericks.

I switched on ACLs for smb service as mentioned in http://support.apple.com/kb/TS4149

but this did not help either.

BTW. Why do I have to switch on ACLs when I have a server running?

Bye,

eweri

Many problems here with mavericks and our smb linux file server.  None of the work arounds on the net have made any difference.  We created a blog at macsmbissues.com to document and discuss issues related to mavericks and smb.

I have things between my Mac Server, Windows 7, and my Mac client working kinda although if I leave a file in Windows open too long it will still loose connection and locks the file on the server side. What I did on the Windows side is in the Registry settings shown in the attached screen shot. On the Mac side I used Connect to Server and connected using the AFP stack like so, AFP:192.168.XXX.XXX.

We're "downgrading" to Mountain Lion. I understand there may be a few quirks with ML but Mavericks has been a nightmare. Meanwhile, my old Snow Leopard Xserver that's sitting right next to the new Mavericks Mac Mini server continues to hum right along. I suspect it's also flipping the Mac Mini the bird.

It's interesting that some people had so much better luck with Mountain Lion.  I wonder what the difference in network or client configuration or use case is?

At our office, and I know some other people had the same issue, Mountain Lion's SMB sharing was completely unusable--there were connection and permissions issues that would reliably cause Acrobat and Office to fail within a few minutes of opening a document off a network volue on some Win7 clients.  I had to resort to ripping out the SMBX daemon and installing Samba to restore functionality for my Windows users.

Mavericks fixed those issues for me entirely, but introduced the routine smbd hangs that drove people nuts.  10.9.2 seems to have fixed those for us, at least in the past two weeks of testing, although there has been one unexplained complete hang of the server.

Hard to argue that 10.6 wasn't bulletproof, though, where 10.7 - 10.9 have been three major versions of growing pains.

Did anyone check out the latest Beta 13D33 of 10.9.3? I'm wondering why Apple encourages the developers to focus only on Graphics Drivers, Audio, Safari and iTunes contacts and calendar synchronization. No word about SMB. I can only hope that with 10.9.3 all the SMB and file copy -36 errors are gone.

Hi, whats serving DNS?  the mac server or windows server?  whats the FQDN?  Ive had similar issues and ive come to find that the errors were rooted in DNS

In our case DNS is done by the server itself, usually server.fqdn.com

Do you serve DNS elsewhere?

The latest dev release of 10.9.3 seems to be behaving better as far as file sharing goes... SMB is "quiet" and playing nice...

the attrib errors still show up, but the users are not complaining about speeds and errors connecting.

We have Windows 7 Pro, Windows 8 and 8.1 Pro, Mac OS X from 10.6 to 10.9 for a grand total of 200 machines in our network

So far so good...

my organization uses windows serving DNS for access to the gateway and then the mac server hosts DNS for the mac clients with a forwordloookup back to the windows server to get outside, the probloems I ran into was that the gateway DNS ended in ".local"  and apple Bonjour kept messing up DNS, so trafic going to clients hit a fork and packets were getting lost.  Id say make sure there arnt any host records that end in a .local on teh mac side

This is encouraging.. we're on 10.9.2 and I am VERY close to installing SMBUp. We're having a world of problems from Office documents getting locked to due disconnections / read only issues etc, joining the Macs as 'Networking Accounts' isn't an option.

Think I may have fire for 10.9.3 and see what happens. Fun question, but guesses on ETA?

Unfortunately I am in the same boat with you guys. Apple have made a handbrake turn and unfortunately crashed into the wall. No idea what is the issue and I gave up long time ago when I moved from 10.6 (working edition server) to 10.8. Since then I am using SMBUp with no issues.

Hello,

did somebody have a solution for the problems with smbx and indesign crashes under win7 cs6?

i also have a photoshop script problem. the following script returns the wrong number of files in a folder on the server over smbx on a win7 pc. on a mac in works!

is there a way to set the default posix permissions for afp and smb for create files and folders?

//===============================================================

function main() {

           var rootFolder = Folder.selectDialog("Choose root folder", "");

          var files = rootFolder.getFiles();

          alert("files:"+files.length);

}

main();