The internal drives on the Windows machine still test at their full speed.

I cannot for the life of me fathom what has changed, everything is still enabled on the windows side, and crucially this is only for externally mounted drives. Install Samba The first step is to install the samba package.

However, I have connected again a couple of weeks later and the network speeds have dropped back down to 5-6MB/s. I ran across this page and when I enabled NetBIOS over TCP/IP this seemed to fix the issue - external drives mounted on the Win side would test at their capacity of 320MB/s when testing from the MBP. However, external drives did not work - I was getting write speeds of around 5MB/s We focused on SMB2 for this research, as opposed to SMB1. You should see both Share Files and Folders Using SMB and another item for AFP checked. My opinion is the Macmini icon is probably the most apt as it looks most like a Vero and a Mac Mini is often used as a file server, so it sort of fits, and it will stand out from other Windows PC’s on the network. For the most part, SMB2 and SMB3 messages are processed by the same code. On the Mac sharing files, open the Sharing system preference pane. Previous versions of Samba (on Stretch) use the Windows (BSOD) icon at the bottom right but I think we can do better than that. They connected up nice and easily, and when running a test of disk speed from the MBP (with Blackmagic disk speed test) the internal drives on the Win machine tested at their full speed for around 500MB/s. SmbX on macOS has full support for SMB1 and SMB2 SMB3 support is limited to message-signing schemes and doesn’t support newer features, such as compression. I just encountered this issue on a fresh format-and-install (not an upgrade) of the public release of 11. I was trying out a direct connection between my MBP and consumer Win10 machine connected direct via thunderbolt.

Macos samba server