don999
11-29-2021, 04:59 PM
I still like to use my older systems, and I want to access some smb shares and vice versa.
Now remember that older systems are a "security risk" and I don't have these connected to the internet.
Older versions of samba and knoppix have changed the minimum protocol levels which is why older versions of knoppix work with older systems and knoppix 9.1 doesn't.
One handy command is
"findsmb"
which should list any SMB servers on your network.
==================================
To connect to my old windows 2000 box with smbclient, I have to edit the smb.conf file and set
"sudo nano /etc/samba/smb.conf"
"client min protocol = NT1"
"client use spnego = no"
because smbclient gets its settings from smb.conf.
So now I can go
smbclient -L 192.168.0.1
and it lists my available shares without problem.
smbclient -L 192.168.0.1 -d 9
will give you lots of debugging information.
=============================
To mount a cifs/samba share, you can do:
sudo mkdir /mnt/a
sudo chown knoppix:knoppix /mnt/a
mount.cifs //192.168.0.1/share_name /mnt/a -o user=username,pass=password,uid=knoppix
but an older windows system like win2000 uses older authentication (remember that's insecure) so we have to step down the security with:
mount.cifs //192.168.0.1/share_name /mnt/a -o user=username,pass=password,uid=knoppix,sec=ntlmv2 ,vers=1.0
Note that mount.cifs doesn't get its settings from smb.conf, so you specify the security as "sec" and "vers" options on the command line.
================================
Making your own samba share:
"sudo nano /etc/samba/smb.conf"
and add your own share at the bottom of the file
[my_share_sdb]
path = /media/sdb1/
read only = yes
# set read only to yes or no depending on if you want to write it
======
Set the min protocol to "NT1" if you want an older system to be able to connect (remember it's insecure)
Note that this has to go in the global section
min protocol = NT1
#(min protocol is a synonym for "server min protocol")
=====================
another thing you can do is to set the netbios name in the smb.conf, so if you don't want the default Microknoppix name you can set it:
netbios name = KNOPPIX2
or even set aliases
netbios aliases = ALIAS1 ALIAS2
This can prove useful if you have multiple knoppix systems on your network and you don't want them all to have the name Microknoppix.
===================
sudo smbpasswd -a knoppix
will add a user to the smb password file and prompt you for the password
you can do
echo -e 'SMB\nSMB' | sudo smbpasswd -a knoppix
if you want to set your smb password for user knoppix to SMB.
=======================
Okay, once you've fixed up your smb.conf file you need to launch your samba service
smbd is the samba demon, nmbd does the netbios stuff (you need them both)
sudo service smbd start
sudo service nmbd start
and if you change the settings in smb.conf you need to restart smbd (or nmbd if you change the netbios settings)
sudo service smbd restart
sudo service nmbd restart
==================
Also you have the "testparm" command to check your samba smb.conf file.
"testparm -v" for verbose.
Lots of good information on samba at:
https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERMAXPROTOCOL
(https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERMAXPROTOCOL)https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#CLIENTMAXPROTOCOL
CORE: Earliest version. No concept of user names.
COREPLUS: Slight improvements on CORE for efficiency.
LANMAN1: First modern version of the protocol. Long filename support.
LANMAN2: Updates to Lanman1 protocol.
NT1: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.
SMB2: Re-implementation of the SMB protocol. Used by Windows Vista and later versions of Windows. SMB2 has sub protocols available.
SMB2_02: The earliest SMB2 version.
SMB2_10: Windows 7 SMB2 version.
By default SMB2 selects the SMB2_10 variant.
SMB3: The same as SMB2. Used by Windows 8. SMB3 has sub protocols available.
SMB3_00: Windows 8 SMB3 version.
SMB3_02: Windows 8.1 SMB3 version.
SMB3_11: Windows 10 SMB3 version.
By default SMB3 selects the SMB3_11 variant.
Now remember that older systems are a "security risk" and I don't have these connected to the internet.
Older versions of samba and knoppix have changed the minimum protocol levels which is why older versions of knoppix work with older systems and knoppix 9.1 doesn't.
One handy command is
"findsmb"
which should list any SMB servers on your network.
==================================
To connect to my old windows 2000 box with smbclient, I have to edit the smb.conf file and set
"sudo nano /etc/samba/smb.conf"
"client min protocol = NT1"
"client use spnego = no"
because smbclient gets its settings from smb.conf.
So now I can go
smbclient -L 192.168.0.1
and it lists my available shares without problem.
smbclient -L 192.168.0.1 -d 9
will give you lots of debugging information.
=============================
To mount a cifs/samba share, you can do:
sudo mkdir /mnt/a
sudo chown knoppix:knoppix /mnt/a
mount.cifs //192.168.0.1/share_name /mnt/a -o user=username,pass=password,uid=knoppix
but an older windows system like win2000 uses older authentication (remember that's insecure) so we have to step down the security with:
mount.cifs //192.168.0.1/share_name /mnt/a -o user=username,pass=password,uid=knoppix,sec=ntlmv2 ,vers=1.0
Note that mount.cifs doesn't get its settings from smb.conf, so you specify the security as "sec" and "vers" options on the command line.
================================
Making your own samba share:
"sudo nano /etc/samba/smb.conf"
and add your own share at the bottom of the file
[my_share_sdb]
path = /media/sdb1/
read only = yes
# set read only to yes or no depending on if you want to write it
======
Set the min protocol to "NT1" if you want an older system to be able to connect (remember it's insecure)
Note that this has to go in the global section
min protocol = NT1
#(min protocol is a synonym for "server min protocol")
=====================
another thing you can do is to set the netbios name in the smb.conf, so if you don't want the default Microknoppix name you can set it:
netbios name = KNOPPIX2
or even set aliases
netbios aliases = ALIAS1 ALIAS2
This can prove useful if you have multiple knoppix systems on your network and you don't want them all to have the name Microknoppix.
===================
sudo smbpasswd -a knoppix
will add a user to the smb password file and prompt you for the password
you can do
echo -e 'SMB\nSMB' | sudo smbpasswd -a knoppix
if you want to set your smb password for user knoppix to SMB.
=======================
Okay, once you've fixed up your smb.conf file you need to launch your samba service
smbd is the samba demon, nmbd does the netbios stuff (you need them both)
sudo service smbd start
sudo service nmbd start
and if you change the settings in smb.conf you need to restart smbd (or nmbd if you change the netbios settings)
sudo service smbd restart
sudo service nmbd restart
==================
Also you have the "testparm" command to check your samba smb.conf file.
"testparm -v" for verbose.
Lots of good information on samba at:
https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERMAXPROTOCOL
(https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERMAXPROTOCOL)https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#CLIENTMAXPROTOCOL
CORE: Earliest version. No concept of user names.
COREPLUS: Slight improvements on CORE for efficiency.
LANMAN1: First modern version of the protocol. Long filename support.
LANMAN2: Updates to Lanman1 protocol.
NT1: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.
SMB2: Re-implementation of the SMB protocol. Used by Windows Vista and later versions of Windows. SMB2 has sub protocols available.
SMB2_02: The earliest SMB2 version.
SMB2_10: Windows 7 SMB2 version.
By default SMB2 selects the SMB2_10 variant.
SMB3: The same as SMB2. Used by Windows 8. SMB3 has sub protocols available.
SMB3_00: Windows 8 SMB3 version.
SMB3_02: Windows 8.1 SMB3 version.
SMB3_11: Windows 10 SMB3 version.
By default SMB3 selects the SMB3_11 variant.