We have file perm issues with our SAN. Basically our SAN doesnt like SMB 2 from our Macs, so we use SMB 1 (slower, but less corrupty...). We are moving away from this SAN shortly though.
I ensure this command is ran on all of our clients (either on the base image, deployment workflow or sent our via ARD terminal command)
The bug seems specific to non-Apple SMB shares (we see it with Microsoft Server 2012r2), we can’t replicate it with OS X Server SMB shares. Turning on/off Finder previews has no effect. Our machines are not bound to Active Directory.We have confirmed with other institutions that have their clients and server bound to Active Directory and they see the same issue.
sudo sh -c 'echo '[default]' >> /etc/nsmb.conf; echo 'smb_neg=smb2_only' >> /etc/nsmb.conf'
- In the Server Address field, enter smb:// to define the network protocol for SMB, and then enter either the IP address or the hostname of the server. FIG 2 – Connect to Server dialog box To add the server to your Favorite Servers list, click the ‘+’ button.
- Samba is a handy open source and multi-platform utility that makes it easy for system and network administrators to easily setup, configure and use various systems and equipment. Helps you gain access to print and file services. Samba delivers file and print services for different Microsoft Windows.
- In Mac OS X Server 10.2 or later, make sure the user is set up for Basic authentication, not Password Server authentication. When you've finished configuring Windows Services, click the Save button, then click the Windows icon in Server Settings, and select Start Windows Services. This starts the Samba daemons, enabling access from SMB clients.
Samba For Windows 10
this forces SMB2 on the client
you can then view the share connection with this command:
smbutil statshares -a
![Samba Samba](/uploads/1/2/6/4/126471146/431931814.png)
which shows what flavour of SMB is being used.
To remove the nsb.conf file and revert back to defaults, use this command :
Samba Linux
rm /etc/nsmb.conf
Samba For Mac Server Settings
REBOOT FOR CHANGES TO TAKE EFFECT