Windows 10: Samba 4 and NAS / Windows shares on W10 and Linux servers / clients

Hi folks
there's a lot of confusion about how to set SAMBA up if you have any sort of Linux type system in the mix whether host , running as a NAS or in VM and Windows 10 mix.

the best way is to do the following

1) Enable SMB1 on W10 -- while it might not be recommended it's perfectly safe for a home LAN
2) disable the feature to remove SMB1 if not needed
3) in the SAMBA configuration file in the [global] section add the following to the file (usually in etc/samba directory) :
a) max protocol = NT1
b) name resolve order = bcast host "don't bother with wins or any of that other stuff
c) netbios name = REFUR "or whatever your computer name is
d) case sensitive = no "that gets round computer names / workgroup or WORKGROUP etc etc
e) local master = yes
preferred master = yes
os level = 25
dns proxy = no
auto services = global
interfaces = lo enp2s0f0 "(or whatever your LAN interface is -- use ifconfig to check --keep the lo one in as well
bind interfaces only = yes
server role = standalone server


Forget all the domain stuff - not needed for home type servers etc --you aren't running commercial VPN's or cloud applications for paying users !!!.

Restart the server (better) or simply stop and start services nmb(d) and smb(d) on the NAS. Check you haven't made a typo in the Samba file by typing command testparm on the NAS / Linux machine.

Now you should be in business

check on the NAS / Linux machine as root or sudo with command :
service nmb(d) status -l some distros have nmbd others have nmb. If the service command doesn't work or not available then use systemctl status nmb(d)













cheers

jimbo

:)

 

Linux Samba settings to display Windows shares


Hi folks

Samba needs a different setting to display Windows or any of the SAMBA shares - especially if its version of Linux / NAS server needs / uses SMB1

You still need to set the SMB1 option in Add features to windows of course.

also in the samba config file ensure this line is in the global section


[global]
max protocol = NT1 <===+++++++++++++++++

(Not client max protocol !!)

what this actually does (apart from working !!! ) I have no idea but it fixed 4 Linux machines which suddenly stopped listing Samba shares under network. I saw the suggestion on some weird website - have no idea of the link though - must have been imbibing some of those nice malted fluids kari likes. !!!

Works also with ubuntu guests as well as Hosts and Centos guests and hosts. haven't messed around with other Linux distros as I don't really use them.





Cheers
jimbo

 

W10 pro update 1709 shares cannot be accesed FROM NAS Server (Samba)


Hi folks

it's definitely a windows update problem with version 1709.

FROM Nas server -- cannot access windows shares vua samba anymore -- says timeout on xxxxx - and this comes up immediately !!!

other windows machines have no problem.

Accessing the server FROM windows is OK but I need to access windows FROM the server as well (auto backups from server).

Any suggestions folks.

I actually didn't want this last update but some how windows set to auto update.

version is W10 pro 1709 build 16299.64

SAMBA on server running just fine -- TV's, phones etc can all access OK. SAMBA V4 (latest) being used on server.

Note Windows TO server works, Windows FROM server fails. I have 2 NAS servers and same problem -old Windows works but not the latest.

Tested also disabling BOTH sets of firewalls and Windows has all the allow remote access stuff enabled.

Is there some type of local security policy default enabled that wasn't there before. ??

Cheers
jimbo

 

Citrix killed Network access to NAS / Linux servers - now fixed !!


Hi folks
I tried all the standard stuff to get access to NAS / Linux machines from W10 including re-enabling SMB1 and killing the auto removal of SMB1 -- nothing worked.

Then I had a brain storm -- get rid of CITRIX (I can run that as a VM for access to work remote desktop)

rebooted

Guess what -- access immediately to my 3 NAS type servers. Note for NAS to access windows also check the SERVER as well as CLIENT box - CLIENT allows W10 to access SAMBA on NAS, SERVER allows NAS to access windows shares.






Windows Networking is a real pain but for the moment working now.

Don't know what CITRIX did but it's staying on a VM from now on !!!!

Update : the VM I've installed CITRIX on has the original network problem !! but NAS access isn't needed on that VM. The main problem is solved though.

Cheers
jimbo