Posts Tagged ‘smb’

Recently we had a Mac not be able to access a Windows Samba (SMB) Share

Thinking a windows update could have caused some issue, we tested another Mac but it worked fine 

OS X Mavericks 10.9 brings a change of SMB2 instead of SMB1 , which can be disabled with the below command 

echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf

This still didn’t work so we reverted back to SMB2 with the below

rm ~/Library/Preferences/nsmb.conf

I used Telnet to make sure there wasn’t a network issue on port 445 ( Open Terminal , enter Telnet and open IP 445) which worked

I installed a trial of this on the Windows File Server which creates an AFP share , which worked by is 1000$!

https://www.acronis.com/en-au/mobility/mac-windows-compatibility/

We upgraded the Mac to the latest OS 10.14 ( for free )  and it solved the issues

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I wanted to copy a load of files from a server to a Synology NAS. 

You can use Synology GUI to map a remote file using SMB with a username and password. You can then reference that folder for an RSYNC copy to do the inital sync then copy changes 

The RSYNC Command is below

rsync –archive –progress –verbose –inplace –exclude ‘*@SynoResource’ –exclude ‘@eaDir’ –exclude ‘*.vsmeta’ –exclude ‘.DS_Store’ ‘/volume1/Remote/Dir/’ ‘/volume1/Dir/’ >> /volume1/DIR/log1.txt 2>&1

Just to show you –Archive is equals -rlptgoD (no -H,-A,-X)  , so it will overwrite newer files with the older ones so only use the above for the initial sync

To replicate the rest when the new volume is being used do

rsync -rlptgoDu –progress –verbose –inplace –exclude ‘*@SynoResource’ –exclude ‘@eaDir’ –exclude ‘*.vsmeta’ –exclude ‘.DS_Store’ ‘/volume1/Remote/Dir/’ ‘/volume1/Dir/’ >> /volume1/DIR/log1.txt 2>&1

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Windows 10Recently we had a problem where network shares were dropping in and out on some windows 10 machines. We used pings to make sure network connectivity was not to blame which it wasn’t ( no pings dropped ) some people online where complaining about having to roll back drivers for network cards to older versions

I have seen this on Vista before , so we forced it to use a lower version of Samba : 

To access said setting go to the control panel in Windows 10 (or 7), in Category view click on the text “System and Security”, then click on the text “Administrative Tools”.

Now double click and open “Local Security Policy”.

In the Local Security Policy screen on the left navigation tree, expand the “Local Policies –> Security Options” then about 2/3rd’s the way down the list you’ll see a Policy called “Network Security: LAN Manager authentication level”. Double click and change the setting to be “Send LM & NTLM – use NTLMv2 session security if negotiated.”

Then just press OK and close all of the open windows and then try again

 

n the case of Windows 10 Home, Local Security Policy does not exist; therefore make the change in the registry (use regedit).
 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\LSA
Add:
LMCompatibilityLevel
Value Type: REG_DWORD – Number (32 bit, hexadecimal)
Valid Range 0-5
Default: 0, Set to 1 (Use NTLMv2 session security if negotiated)
Description: This parameter specifies the type of authentication to be used.

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)