smb 10.14.5

you can try this

https://support.apple.com/en-us/HT208209

honestly I have rolled back to AFP for the users I support at my job and I'm washing my hands of SMB on mac, it's too limiting. If thats not an option then make sure you have one connection type communicating over your network. SMB and AFP do not behave over the same network as you may find.

try easy find in the apple store for a smb search app

Same here. After 10.14.5, LAN connection to the file server freezes after a while and the finder on the clients crashes. It´s nearly impossible to work. Symptoms are very similar to the known issues after the 10.13.1 security update. Tried https://support.apple.com/ro-ro/HT208317 but without success.

running something like this here for a 20 user share so my $0.02:

Make sure you have a trusted backup then put all the data on a clean external usb 3.0 drive and ignore ownership on that volume. Outside of accessing HD video files over the network the speed difference of data transfer over SATA or USB distributed to network users is not going to be an issue

Run AFP only; it's less traffic accidents to run one protocol if Mac is your only platform.

Yes AFP has not been supported by Apple for some time but my understanding is Apples implementation of SMB had to be modified so it's code did not directly copy proprietary and intellectual info from Microsoft. As a result Apples SMB is not going to behave like anyone else's. In other words it's ****

Once the shared data is on the external and verified your backup use Recovery and restore the "server" with the OS it came with using recovery

https://support.apple.com/en-us/HT201314

Ditch any "sever" upgrades. macOS is going to have more development quality control than server OS.

Patch that OS and setup your shares

maintain a Time Machine backup of the data and get a copy of Carbon Copy Cloner (bomich.com)

Once your boot HD is configured you should clone it to an external and then detach it and store it.

Run a nightly CCC copy of your data drive.

In the event of a catastrophe you can stick the boot drive on that mac or a spare and you don't' need to restore all your data, just plug in the clone if it comes down to it. This is minutes of downtime vs hours or possibly days.

As of now what is your recovery plan if that iMac doesn't boot one morning?

Running into the same issue here.

After the update to 10.14.5 on a mac mini 2018 I had to restart the smb filesharing server up to 10 times a day.

Thats very frustating. Since several years I use the smbd from apple to serve my 5 imacs with filesharing. It was allways slow, but as Apple told us that they will stop serving file with afp I stick to smb.

But now I switched to afp only for the shares I am using with the iMacs.

And stick with smb only for shares I use with windows PC.

Right no this look like a viable solution.

I had contact to the apple support, talking with them for an hour. The first person even asked What is SMB? At the end I was told that the first level support has no deeper information and also had never heard about this issue.. I should ask https://consultants.apple.com/de/, meanI should pay for support for an bug Apple introduced with the last update.

The is no second level support anymore, as in former times. Thats very disappointing.

Apple should be able to invest in the software quality especially for such an important task as filesharing.

One has a suspicion that Apple these days think users either are -

• Home users (and therefore not using a file server)
• Internet based startups using SAAS and cloud services and related things like GitHub and hence again not using traditional file servers

They seem to have completely forgotten the huge majority of business and education customers who do still need to use traditional file servers. :(

(One can presume Apple themselves heavily use cloud services although not iCloud other than for individual use ;) )

Just to get this straight in my mind, you are saying your "server" is what

has been upgraded to 10.14.5?

"...Rolling back to 10.14.4 is complicated as you have to wipe the drive and I will lose all data since the update..."

You mean to say you have a "server" in your system and it has no Time Machine or other daily incremental backups

or any other scheme to quickly recover from issues?

As I recall the sad story was that originally Apple used the open source SAMBA software. Originally this was covered by a GPL 2.0 license which Apple felt able to abide by. However the SAMBA team switched to using GPLE 3.0 which Apple felt unable to work with.

See - https://www.networkworld.com/article/2292472/samba-switches-to-gplv3.html

Again as I recall whilst Apple did not make much if any of an official announcement it was widely viewed that Apple and other corporations viewed GPL 3.0 as incompatible with their being a profit making business. This is allegedly because of a belief that this makes it necessary to share back their own proprietary software.

Apple then wrote their own SMB implementation as a replacement which is generally known under the name SMBx.

SAMBA even back then had had many years of development to smooth off any rough edges whereas Apple's having to be written from scratch was certainly at the beginning 'troublesome'. Even now many years latter there are still numerous issues with Apple's SMBx although not as many. There is also a loss of functionality that still exists and is very unlikely to ever be addressed especially with the continued castration of Server.app.

A Mac acting as a 'server' for SMB file shares can in theory do server side Spotlight indexing which is what the original post discusses. I found even AFP shares became increasingly problematic for this over the years as newer macOS server releases occurred.

It is in theory possible to set up a Linux server running SAMBA and have it do Spotlight indexing. See - https://wiki.samba.org/index.php/Spotlight you might want to consider this as an option.

In theory something similar is possible with a genuine Windows Server but not for free. It would require using Acronis Files Connect. See - https://kb.acronis.com/content/48794

I believe that over the years sometimes voluntarily and sometimes under pressure during the period when Microsoft was being investigated for anti-competitive practises that licenses and access to Windows source code were given to the SAMBA team so they could provide better compatibility. This is probably linked to SAMBA 4.0 being able to add Active Directory support.

With Apple's Server.app becoming more of a joke most people these days consider using a Linux VM as a replacement or purchasing a NAS box. A Synology NAS makes a good choice from a Mac point of view.

We are facing the exact same problem on two totally different networks.

All devices are running 10.14.5. One Server is running macOS10.14.5 (18F132) and the other server is running ubuntu 18.04.2 with Netatalk 3.1.12.

The only solution in our case was to completely disable Samba on the macOS server. The ubuntu one is not that important so no further investigation took place.

Same problem for me also. SMB shares will not stay mounted very long.

Very frustrating.

macOS 10.14.4 was working perfect and as soon as i updated our MacMini, which shares out about a dozen folders to about a dozen users, SMB stopped working or became intermittent but once down will not come back without jumping through rings of fire...and then down again.

Used Time Machine backup to get back to 10.14.4 and all is well again.

I have discovered many others with the same issue via web searches.