never access data from macOS clients with AFP and SMB at the same time (use different shares for AFP and SMB).encourage users to use AFP only (better performance).Problems with 'SMB and AFP at the same time' can be read above and my only advise currently is to Ok, didn't want to open another can of worms and will shut up here too. And starting with OS X 10.8 on both ends of a connection it made no difference any more whether you used AFP or SMB as protocol (since Apple's SMB server and client implementation take care of encodings and metadata representation and conversion into HFS+ native representation on disk - they use the well known Alternate data streams scheme Microsoft introduced with 'Services for Macintosh' in Windows NT 3.1 for metadata and introduced some smart ways to deal with problematic or even 'forbidden' characters when dealing with encodings) Apple developed some proprietary SMB2 extensions (again: check the URL above or do a web search for eg 'aapl samba') and added them to their own smbx implementation.
Wrt Samba: Apple doesn't own Samba but they told developers already several years ago that AFP is deprecated (great! Though somewhat strange saying that as a former Netatalk developer ) and will be replaced with SMB.
