/etc/samba/smbusers

[pinnerite]

I do not have one of the above on my Mint 19 system.

So where did the smbpasswd -a <user> details go to?

[stepore]

Post by pinnerite
I do not have one of the above on my Mint 19 system.

One of the above what? I see lots of things above.

Post by pinnerite
So where did the smbpasswd -a <user> details go to?

Dunno? Where did you put it? It'll probably be in the very last place
you look.

[pinnerite]

Post by stepore

Post by pinnerite
I do not have one of the above on my Mint 19 system.

One of the above what? I see lots of things above.

Post by pinnerite
So where did the smbpasswd -a <user> details go to?

Dunno? Where did you put it? It'll probably be in the very last place
you look.

I was referring to the subject title.
I am trying to narrow down why samba will not run in my Mint 19
installation.

[Dan Purgert]

Post by pinnerite

Post by stepore

Post by pinnerite
I do not have one of the above on my Mint 19 system.

One of the above what? I see lots of things above.

Post by pinnerite
So where did the smbpasswd -a <user> details go to?

Dunno? Where did you put it? It'll probably be in the very last place
you look.

I was referring to the subject title.
I am trying to narrow down why samba will not run in my Mint 19
installation.

Did you install the samba server package? Last I checked, it wasn't
there by default.

[Pinnerite]

Post by Dan Purgert

Post by pinnerite

Post by stepore

Post by pinnerite
I do not have one of the above on my Mint 19 system.

One of the above what? I see lots of things above.

Post by pinnerite
So where did the smbpasswd -a <user> details go to?

Dunno? Where did you put it? It'll probably be in the very last place
you look.

I was referring to the subject title.
I am trying to narrow down why samba will not run in my Mint 19
installation.

Did you install the samba server package? Last I checked, it wasn't
there by default.

From synoptic I installed everything beginning with 'samba-' (without the
apostrophes).

The O/S I am reporting from now is on the same machine but on a different
drive. it is running Mageia 5 on which samba has always run without hiccups.

I was hoping that another Mint 19 user, running samba would respond so that
comparsons of setups could be made.

I scoured the WWW continuously during the last week trying every set of
hints that I could find. Nothing worked.

So could it be a bug? I am hesitant to suggest that before seeking advice
from someone with more experience.

Someone like stepore for example, :)

[Major Tom]

I just ran sudo apt-get install samba and afterwards sudo smbpasswd -a
and it all worked.

That was in Mint.

[pinnerite]

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd -a
and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.

# service status smbd

looked good, so I edited smb.conf to replace the workgroup and added my
share data, ran testparm, still ok, and ..

# service stop smbd
# service start smbd and got:

● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group
├─1287 /usr/sbin/smbd --foreground --no-process-group
├─1288 /usr/sbin/smbd --foreground --no-process-group
└─1303 /usr/sbin/smbd --foreground --no-process-group

Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.

Still looking good, but

after running up Windows XP, it demanded user name and password for each
share and rejected them.

i installed smb4k, mounted the shares manually. it was very slow but did
it and I could access the data.

# smbtree, however just returned to the prompt.

So, still at square one :(

Never the less, thanks for the suggestion.

[pinnerite]

Post by pinnerite

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd -a
and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.
# service status smbd
looked good, so I edited smb.conf to replace the workgroup and added my
share data, ran testparm, still ok, and ..
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group ├─1287
/usr/sbin/smbd --foreground --no-process-group ├─1288
/usr/sbin/smbd --foreground --no-process-group └─1303
/usr/sbin/smbd --foreground --no-process-group
Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.
Still looking good, but
after running up Windows XP, it demanded user name and password for each
share and rejected them.
i installed smb4k, mounted the shares manually. it was very slow but did
it and I could access the data.
# smbtree, however just returned to the prompt.
So, still at square one :(
Never the less, thanks for the suggestion.

Not long after sending the last message, I ran smbtree again. This time
it returned a complete listing of all the shares.

Yet when XP was run up it could not connect to the shares.

[pinnerite]

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd -a
and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.

# service status smbd

looked good, so I edited smb.conf to replace the workgroup and added my
share data, ran testparm, still ok, and ..

# service stop smbd # service start smbd and got:

● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group ├─1287
/usr/sbin/smbd --foreground --no-process-group ├─1288
/usr/sbin/smbd --foreground --no-process-group └─1303
/usr/sbin/smbd --foreground --no-process-group

Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.

Still looking good, but

after running up Windows XP, it demanded user name and password for each
share and rejected them.

i installed smb4k, mounted the shares manually. it was very slow but did
it and I could access the data.

# smbtree, however just returned to the prompt.

So, still at square one :(

Never the less, thanks for the suggestion.

After a while I ran smbtree again. This time it listed all the shares but
XP still could not detect them.

[stepore]

Post by pinnerite
After a while I ran smbtree again. This time it listed all the shares but
XP still could not detect them.

So what do your smb logs show? I'm sure you've checked them for errors
and such. (nt_status bla bla bla or some such)

Could also post the relevant bits of your smb.conf file. Stuff not
commented out.

[pinnerite]

Post by stepore

Post by pinnerite
After a while I ran smbtree again. This time it listed all the shares
but XP still could not detect them.

So what do your smb logs show? I'm sure you've checked them for errors
and such. (nt_status bla bla bla or some such)
Could also post the relevant bits of your smb.conf file. Stuff not
commented out.

Here goes:

log.smbd
--------
[2018/07/14 18:53:10.483542, 0] ../lib/util/become_daemon.c:
124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2018/07/14 19:12:58.365367, 0] ../lib/param/loadparm.c:
784(lpcfg_map_parameter)
Unknown parameter encountered: "server min protcol"
[2018/07/14 19:12:58.365389, 0] ../lib/param/loadparm.c:
1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "server min protcol"
[2018/07/14 19:12:58.365408, 0] ../lib/param/loadparm.c:
784(lpcfg_map_parameter)
Unknown parameter encountered: "cloent win protocal"
[2018/07/14 19:12:58.365418, 0] ../lib/param/loadparm.c:
1811(lpcfg_do_global_parameter)
Ignoring unknown parameter "cloent win protocal"
[2018/07/14 19:12:58.378503, 0] ../lib/util/become_daemon.c:
124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2018/07/14 19:17:44.791731, 0] ../lib/util/become_daemon.c:
124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2018/07/14 19:27:28.385570, 0] ../lib/util/become_daemon.c:
124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections

log.nmbd
--------
Samba name server ALBURY is now a local master browser for workgroup
ASANDCO on subnet 192.168.0.4

*****
[2018/07/14 19:28:20.297324, 0] ../source3/nmbd/nmbd_become_lmb.c:
397(become_local_master_stage2)
*****

Samba name server ALBURY is now a local master browser for workgroup
ASANDCO on subnet 192.168.98.1

smb.conf
--------
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#======================= Global Settings =======================

[global]

workgroup = ASANDCO
netbios name = ALBURY

server string = %h server (Samba, Ubuntu)

log file = /var/log/samba/log.%m
max log size = 1000
server role = standalone server
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n
pam password change = yes
map to guest = bad user

#======================= Share Definitions =======================

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no

[doc_archive]
comment = archived
path = /home/doc_archive
valid users = alan
admin users = alan
read only = No

[

[Paul]

Post by pinnerite

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd -a
and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.
# service status smbd
looked good, so I edited smb.conf to replace the workgroup and added my
share data, ran testparm, still ok, and ..
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group ├─1287
/usr/sbin/smbd --foreground --no-process-group ├─1288
/usr/sbin/smbd --foreground --no-process-group └─1303
/usr/sbin/smbd --foreground --no-process-group
Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.
Still looking good, but
after running up Windows XP, it demanded user name and password for each
share and rejected them.
i installed smb4k, mounted the shares manually. it was very slow but did
it and I could access the data.
# smbtree, however just returned to the prompt.
So, still at square one :(
Never the less, thanks for the suggestion.
After a while I ran smbtree again. This time it listed all the shares but
XP still could not detect them.

SMB has "versions" and "dialects".

Security wonks will tell you to "disable SMBV1",
which will cause a functional failure of each WinXP
machine. As they're SMBV1 only.

WinXP received a patch for the SMBV1 issue, which
is not listed in Windows Update, and requires you
to track down the KB number on your own. You could
try installing that, if you're concerned about
the security aspects. But the "belt and suspenders"
approach, was to disable SMBV1 on all other OSes,
leaving WinXP huddled in the corner all by itself.

Check your .conf files, to see what happened
to SMBV1 as an option. SMBV1 would be the
"version". I couldn't tell you which numeric
identifier is the "dialect".

Windows 10 actually has two entries in
"Programs and Features" : "Windows Features", to add
SMBV1 to the Win10 machine. By default, it's disabled.

Paul

[pinnerite]

Post by Paul

Post by pinnerite

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd -a
and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.
# service status smbd
looked good, so I edited smb.conf to replace the workgroup and added my
share data, ran testparm, still ok, and ..
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group ├─1287
/usr/sbin/smbd --foreground --no-process-group ├─1288
/usr/sbin/smbd --foreground --no-process-group └─1303
/usr/sbin/smbd --foreground --no-process-group
Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.
Still looking good, but
after running up Windows XP, it demanded user name and password for
each share and rejected them.
i installed smb4k, mounted the shares manually. it was very slow but
did it and I could access the data.
# smbtree, however just returned to the prompt.
So, still at square one :(
Never the less, thanks for the suggestion.
After a while I ran smbtree again. This time it listed all the shares
but XP still could not detect them.

SMB has "versions" and "dialects".
Security wonks will tell you to "disable SMBV1", which will cause a
functional failure of each WinXP machine. As they're SMBV1 only.
WinXP received a patch for the SMBV1 issue, which is not listed in
Windows Update, and requires you to track down the KB number on your
own. You could try installing that, if you're concerned about the
security aspects. But the "belt and suspenders" approach, was to disable
SMBV1 on all other OSes, leaving WinXP huddled in the corner all by
itself.
Check your .conf files, to see what happened to SMBV1 as an option.
SMBV1 would be the "version". I couldn't tell you which numeric
identifier is the "dialect".
"Windows Features", to add SMBV1 to the Win10 machine. By default, it's
disabled.
Paul

I just got Windows 10 to work with the smb.conf file showm in my reply
to stepore but XP still would not. It looks like you have the pinned down
the cause of the problem.

What surprises me is that it hasn't shown up in my Mageia 5 system runing
the same virtual machines.

Alan




I

[pinnerite]

Post by pinnerite

Post by Paul

Post by pinnerite

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd
-a and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.
# service status smbd
looked good, so I edited smb.conf to replace the workgroup and added
my share data, ran testparm, still ok, and ..
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group
├─1287 /usr/sbin/smbd --foreground --no-process-group
├─1288 /usr/sbin/smbd --foreground --no-process-group
└─1303 /usr/sbin/smbd --foreground --no-process-group
Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.
Still looking good, but
after running up Windows XP, it demanded user name and password for
each share and rejected them.
i installed smb4k, mounted the shares manually. it was very slow but
did it and I could access the data.
# smbtree, however just returned to the prompt.
So, still at square one :(
Never the less, thanks for the suggestion.
After a while I ran smbtree again. This time it listed all the shares
but XP still could not detect them.

SMB has "versions" and "dialects".
Security wonks will tell you to "disable SMBV1", which will cause a
functional failure of each WinXP machine. As they're SMBV1 only.
WinXP received a patch for the SMBV1 issue, which is not listed in
Windows Update, and requires you to track down the KB number on your
own. You could try installing that, if you're concerned about the
security aspects. But the "belt and suspenders" approach, was to
disable SMBV1 on all other OSes, leaving WinXP huddled in the corner
all by itself.
Check your .conf files, to see what happened to SMBV1 as an option.
SMBV1 would be the "version". I couldn't tell you which numeric
identifier is the "dialect".
"Windows Features", to add SMBV1 to the Win10 machine. By default, it's
disabled.
Paul

I just got Windows 10 to work with the smb.conf file showm in my reply
to stepore but XP still would not. It looks like you have the pinned
down the cause of the problem.
What surprises me is that it hasn't shown up in my Mageia 5 system
runing the same virtual machines.
Alan

I found the solution on this link

https://askubuntu.com/questions/379044/samba-cannot-access-samba-share-
from-xp

By just inserting:

server max protocol = NT1
lanman auth = yes
ntlm auth = yes

beneath [global] permits both XP and Win-10 virtual machines to run under
Mint 19.

Although NT1 (presumably == SMBv1) is regarded as insecure, on a small
LAN while XP is needed it cannot be avoided.

Thanks for all your help

Alan

[Paul]

Post by pinnerite

Post by pinnerite

Post by Paul

Post by pinnerite

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd
-a and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.
# service status smbd
looked good, so I edited smb.conf to replace the workgroup and added
my share data, ran testparm, still ok, and ..
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group
├─1287 /usr/sbin/smbd --foreground --no-process-group
├─1288 /usr/sbin/smbd --foreground --no-process-group
└─1303 /usr/sbin/smbd --foreground --no-process-group
Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.
Still looking good, but
after running up Windows XP, it demanded user name and password for
each share and rejected them.
i installed smb4k, mounted the shares manually. it was very slow but
did it and I could access the data.
# smbtree, however just returned to the prompt.
So, still at square one :(
Never the less, thanks for the suggestion.
After a while I ran smbtree again. This time it listed all the shares
but XP still could not detect them.

SMB has "versions" and "dialects".
Security wonks will tell you to "disable SMBV1", which will cause a
functional failure of each WinXP machine. As they're SMBV1 only.
WinXP received a patch for the SMBV1 issue, which is not listed in
Windows Update, and requires you to track down the KB number on your
own. You could try installing that, if you're concerned about the
security aspects. But the "belt and suspenders" approach, was to
disable SMBV1 on all other OSes, leaving WinXP huddled in the corner
all by itself.
Check your .conf files, to see what happened to SMBV1 as an option.
SMBV1 would be the "version". I couldn't tell you which numeric
identifier is the "dialect".
"Windows Features", to add SMBV1 to the Win10 machine. By default, it's
disabled.
Paul

I just got Windows 10 to work with the smb.conf file showm in my reply
to stepore but XP still would not. It looks like you have the pinned
down the cause of the problem.
What surprises me is that it hasn't shown up in my Mageia 5 system
runing the same virtual machines.
Alan

I found the solution on this link
https://askubuntu.com/questions/379044/samba-cannot-access-samba-share-
from-xp
server max protocol = NT1
lanman auth = yes
ntlm auth = yes
beneath [global] permits both XP and Win-10 virtual machines to run under
Mint 19.
Although NT1 (presumably == SMBv1) is regarded as insecure, on a small
LAN while XP is needed it cannot be avoided.
Thanks for all your help
Alan

I don't think the transmission is plaintext.

"If you are trying to connect to an older computer that
doesn't support 128-bit encryption, enable the 40- or 56-bit
encryption option."

Maybe that means SMBv1 is 40 or 56 bit, which is sufficient
for casual usage on your home LAN. The existence of encryption,
is for cases where customers run file sharing, across
the Internet. Then you want something a bit better. The
56 bit sounds like DES.

Other potential problems with the thing, are holes
in any handshaking, things that can be exploited. I
don't know the details of this, or even remember what
the issue was with SMBv1. As far as I know, if "something"
gets into my home LAN, the entire thing will be tipped
over - at a guess. I've made no attempt to make it
like a Fort Knox. If I wanted frustration, there's always
sneakernet (hand carrying the disk drive to another machine).

Paul

[pinnerite]

Post by Paul

Post by pinnerite

Post by pinnerite

Post by Paul

Post by pinnerite

Post by Major Tom
I just ran sudo apt-get install samba and afterwards sudo smbpasswd
-a and it all worked.
That was in Mint.

I decided to undo all that I had done, reboot and follow your approach.
# service status smbd
looked good, so I edited smb.conf to replace the workgroup and added
my share data, ran testparm, still ok, and ..
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor
preset: ena
Active: active (running) since Thu 2018-07-12 21:20:49 BST; 50s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Main PID: 1246 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─1246 /usr/sbin/smbd --foreground --no-process-group
├─1287 /usr/sbin/smbd --foreground --no-process-group
├─1288 /usr/sbin/smbd --foreground --no-process-group
└─1303 /usr/sbin/smbd --foreground --no-process-group
Jul 12 21:20:47 albury.asandco systemd[1]: Starting Samba SMB Daemon...
Jul 12 21:20:49 albury.asandco systemd[1]: Started Samba SMB Daemon.
Still looking good, but
after running up Windows XP, it demanded user name and password for
each share and rejected them.
i installed smb4k, mounted the shares manually. it was very slow but
did it and I could access the data.
# smbtree, however just returned to the prompt.
So, still at square one :(
Never the less, thanks for the suggestion.
After a while I ran smbtree again. This time it listed all the
shares but XP still could not detect them.

SMB has "versions" and "dialects".
Security wonks will tell you to "disable SMBV1", which will cause a
functional failure of each WinXP machine. As they're SMBV1 only.
WinXP received a patch for the SMBV1 issue, which is not listed in
Windows Update, and requires you to track down the KB number on your
own. You could try installing that, if you're concerned about the
security aspects. But the "belt and suspenders" approach, was to
disable SMBV1 on all other OSes, leaving WinXP huddled in the corner
all by itself.
Check your .conf files, to see what happened to SMBV1 as an option.
SMBV1 would be the "version". I couldn't tell you which numeric
identifier is the "dialect".
"Windows Features", to add SMBV1 to the Win10 machine. By default,
it's disabled.
Paul

I just got Windows 10 to work with the smb.conf file showm in my
reply to stepore but XP still would not. It looks like you have the
pinned down the cause of the problem.
What surprises me is that it hasn't shown up in my Mageia 5 system
runing the same virtual machines.
Alan

I found the solution on this link
https://askubuntu.com/questions/379044/samba-cannot-access-samba-share-
from-xp
server max protocol = NT1 lanman auth = yes ntlm auth = yes
beneath [global] permits both XP and Win-10 virtual machines to run
under Mint 19.
Although NT1 (presumably == SMBv1) is regarded as insecure, on a small
LAN while XP is needed it cannot be avoided.
Thanks for all your help
Alan

I don't think the transmission is plaintext.
"If you are trying to connect to an older computer that
doesn't support 128-bit encryption, enable the 40- or 56-bit
encryption option."
Maybe that means SMBv1 is 40 or 56 bit, which is sufficient for casual
usage on your home LAN. The existence of encryption,
is for cases where customers run file sharing, across the Internet. Then
you want something a bit better. The 56 bit sounds like DES.
Other potential problems with the thing, are holes in any handshaking,
things that can be exploited. I don't know the details of this, or even
remember what the issue was with SMBv1. As far as I know, if "something"
gets into my home LAN, the entire thing will be tipped over - at a
guess. I've made no attempt to make it like a Fort Knox. If I wanted
frustration, there's always sneakernet (hand carrying the disk drive to
another machine).
Paul

Samba is only been deployed between the Linux Mint host and one or other
of the two virtual Windows machines.

But another problem has arisen ... new thread.

[Paul]

Post by pinnerite
Samba is only been deployed between the Linux Mint host and one or other
of the two virtual Windows machines.
But another problem has arisen ... new thread.

When you want to resize the HDD, boot a LiveCD
and use GParted from there.

To expand a partition, might require dismounting it.
You can't easily dismount slash "/" on a running
OS, and that's where booting the LiveCD comes in.
The "/" on the LiveCD is in RAM, leaving the
HDD completely "un-busy".

Then you could have expanded.

Any time you're running into trouble, you can
always make a backup image of what you've got,
in case an idea comes along later, and you
wanted to backtrack. I make all sorts of
"junk" backups here, tagged with "eraseme"
in the file name, so I know they're junk
backups and can be deleted.

I have around 20 hard drives. Most filled
with "junk". It's easy to be a promoter
of backups when you have 20 hard drives :-)

Paul

[Pinnerite]

Post by Paul

Post by pinnerite
Samba is only been deployed between the Linux Mint host and one or other
of the two virtual Windows machines.
But another problem has arisen ... new thread.

When you want to resize the HDD, boot a LiveCD
and use GParted from there.
To expand a partition, might require dismounting it.
You can't easily dismount slash "/" on a running
OS, and that's where booting the LiveCD comes in.
The "/" on the LiveCD is in RAM, leaving the
HDD completely "un-busy".
Then you could have expanded.
Any time you're running into trouble, you can
always make a backup image of what you've got,
in case an idea comes along later, and you
wanted to backtrack. I make all sorts of
"junk" backups here, tagged with "eraseme"
in the file name, so I know they're junk
backups and can be deleted.
I have around 20 hard drives. Most filled
with "junk". It's easy to be a promoter
of backups when you have 20 hard drives :-)
Paul

I always use Parted Magic when working on partitions.
Sadly, it is not yet a perfect science.

Alan

[Edmund]

Post by pinnerite
I do not have one of the above on my Mint 19 system.
So where did the smbpasswd -a <user> details go to?

I think you can get info with :
sudo pdbedit -L
and
sudo pdbedit -L -v

Edmund