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

since 3 days my smbd is running stable 🙂🙂

The only thing which I changed was to the DNS.

it was set to answer "local stations only", now it's set to "all stations".

Since then the smbd stays at low CPU-load, the access on the network is quick for all clients,.

Keep the fingers crossed !!!

Regards

Henry

Do you mean the "Perform lookups for" setting?

http://krypted.com/wp-content/uploads/2013/10/Screen-Shot-2013-10-04-at-6.39.50- PM.png

anyone tested this if the file server is NOT the same box as the DNS server?

Sorry, I'm using German Version of Server 3.0.1

On the server tab are settings (forwarding and DNS-lookup).

The DNS-lookup was set to "local clients only", now it's "all clients"

(at least this is the literal translation)

that is what i thought.

we have always had that setting on "all clients", and still have the SMB issue.

today the smbd was blocked at 100% again.

After todays update 10.9.1 no access possible at all ( smb / afp ), only guest or admin

Just retested after installing 10.9.1. No changes that I can see. SMB2 still fails, and SMB1 will still crash under heavy load.

As far as the server becoming inaccessible after a software update, that's been an issue ever since they released MacOS 10.7 Server. Every so often after applying a software update the SMB shares would become inaccessible. Only reliable way to fix it is to unshare, restart, run a diskcheck for permissions and then reshare. And even THAT will sometimes fail. Bottom line is that SMBX has always been notoriously quirky for windows computers.

After two weeks heavy truoble - I have to retourn to Snow Lion and Server 2

Mavericks and Server 3 is a b*tch with SMB...

Can't blame you to go back. My box is dual boot, so I can reboot to compare results. 10.8.5 with Server 2 was a bit finicky, but it worked. Maverick with Server 3 I can get to go for brief periods, but it routinely crashes and goes down.

Fix this, Apple!

Updates:

1- Spoke for a while with an Apple SE and was told tht for now Microsoft's flavor of SMB running on Win 8 and 2012 RDS will not be "supported". Apple has a Radar ticket on it, and it may be supported soon.

2- We have two directories, one OD(different server) and one AD, after binding the mavericks File Server to the AD(in addition to OD), the problem resolved itself. Now ALL our users can authenticate to the file server without issues and withour smbd freaking out.

We are still on OS X 9, didn't dare to upgrade to 9.1...

Our week and a half long nightmare is over(knock on wood). Good luck with yours. If I can be of any help, please PM me!

Not running sever app but running file server on a small network. Maverics upgrade from snow leopard, wifi turned off.

It seems netbios name resolution stop working after some time.

A workaround: edit the hosts file in C:\Windows\System32\drivers\etc and point the server name to the ip adress - - on all windows computers.

I tried editing the Hosts file, and forcing the connection to smb1, but I still see disconnections on my Windows 7 machine. Only way to fix them is to force quit the smbd process on the Maverick server, or restart the Maverick machine.

Here's hoping the forthcoming 10.9.2 will fix this!

Strange and sorry to hear, it a rally annoying bug. Still works for me. I havent forced to smb1.

added this line

192.168.1.50 bicmac

C:\Windows\System32\drivers\etc\hosts

havent restarted the mini for 3 days and its ok, not a nice workaround though.

me too hoping for a real fix from Apple.

Hi everyone,

I do not know if I am having the EXACT same issue or its something else entirely. I upgraded my Mac Mini that I purchased for a shared Apple server at home and connected a Thunderblot Pegasus RAID array to it. I connect from my Desktop Windows 8.1 Alienware desktop and my connections are intermittent at best. Sometimes it works sometimes it does not.

I editied the host files to hard code the Ip Address resolution as ping would time out.

Before reading this I hit PING for 4 mintues and watched as it would alternate between

Reply from 192.168.1.100: bytes=32 time=6ms TTL=64

and

Request timed out.

Here is the weird part. It recovered each time from the timeout with no intervention on my part. But each time I went to Windows Explorer and clicked on the Apple Share....right back to Timed Out.

I have switched the cable out to a brand new CAT 6 cable and put the cable in different ports on my Netgear switch. I have not called Apple yet to see if its the hardware on the NIC as it does seem to be software. I have not tested the above fixes as I am unclear how close our situations are.

The access to the shares is through a network login account.

Hallowed,

You have a network problem and it isn't related to MacOS. You don't mention whether your ping was by hostname or by IP address, but the reply suggests that name resolution isn't involved (assuming 192.168.1.100) is the address of your Mini. Editing the hosts file isn't necessary to ping by IP address. If you see timeouts, look elsewhere for the problem. Cables, router, network configuration, radio interference, etc. Ping is a very low-level network function and if it is intermittent, you have some other issue.

On a local network, ping should be rock solid -- 100% without exception.

Once you have that resolved, you may be back. The topic of this thread is the behavior of the SMB support in OSX.