For many years I have had to retain two Windows virtual machines,
running on a Linux host and VirtualBox.

I need Windows XP for a large home-grown 16 bit programe and for a
programme that drives a Fujitsu cut-sheet feeder-scanner.

Windows 10 is for professional software not available on any other
platform.

The data files are all on Linux partitions and accessed from Windows
using samba.

I have to use the lowest security protocol for Windows to access the
data.

Today, I discovered that from both Windows I could not longer access
the data.

Eventually I powered down and then up again using a drive last cloned
in December 2022.

Everything worked perfectly.

So it seems an update has clobbered my machine.

Has anyone else using samba suffered from this problem?

TIA, Alan

--
Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
running on an AMD Phenom II X4 Black edition processor with 16GB of
DRAM.

On 10/03/2023 19:25, pinnerite wrote:
> For many years I have had to retain two Windows virtual machines,
> running on a Linux host and VirtualBox.
>
> I need Windows XP for a large home-grown 16 bit programe and for a
> programme that drives a Fujitsu cut-sheet feeder-scanner.
>
> Windows 10 is for professional software not available on any other
> platform.
>
> The data files are all on Linux partitions and accessed from Windows
> using samba.
>
> I have to use the lowest security protocol for Windows to access the
> data.
>
> Today, I discovered that from both Windows I could not longer access
> the data.
>
> Eventually I powered down and then up again using a drive last cloned
> in December 2022.
>
> Everything worked perfectly.
>
> So it seems an update has clobbered my machine.
>
> Has anyone else using samba suffered from this problem?
>
> TIA, Alan
>
>
>
>
bloody computers who would have them...

On 3/10/23 14:25, pinnerite wrote:
> For many years I have had to retain two Windows virtual machines,
> running on a Linux host and VirtualBox.
>
> I need Windows XP for a large home-grown 16 bit programe and for a
> programme that drives a Fujitsu cut-sheet feeder-scanner.
>
> Windows 10 is for professional software not available on any other
> platform.
>
> The data files are all on Linux partitions and accessed from Windows
> using samba.
>
> I have to use the lowest security protocol for Windows to access the
> data.
>
> Today, I discovered that from both Windows I could not longer access
> the data.
>
> Eventually I powered down and then up again using a drive last cloned
> in December 2022.
>
> Everything worked perfectly.
>
> So it seems an update has clobbered my machine.
>
> Has anyone else using samba suffered from this problem?
>
> TIA, Alan
>
>
>
>
Can you look at your history of updates in the update manager to see
what update has caused this problem?

On Fri, 10 Mar 2023 14:25:11 -0500, pinnerite <pinnerite@gmail.com> wrote:

> For many years I have had to retain two Windows virtual machines,
> running on a Linux host and VirtualBox.
>
> I need Windows XP for a large home-grown 16 bit programe and for a
> programme that drives a Fujitsu cut-sheet feeder-scanner.
>
> Windows 10 is for professional software not available on any other
> platform.
>
> The data files are all on Linux partitions and accessed from Windows
> using samba.
>
> I have to use the lowest security protocol for Windows to access the
> data.
>
> Today, I discovered that from both Windows I could not longer access
> the data.

Samba has made several fixes to tighten security. See for example
https://www.samba.org/samba/history/samba-4.16.8.html

You can choose to use an older version of samba, but be careful to ensure
that it can not be accessed by untrusted software.

Regards, Dave Hodgins

On 10/03/2023 19:25, pinnerite wrote:
> For many years I have had to retain two Windows virtual machines,
> running on a Linux host and VirtualBox.
>
> I need Windows XP for a large home-grown 16 bit programe and for a
> programme that drives a Fujitsu cut-sheet feeder-scanner.
>
> Windows 10 is for professional software not available on any other
> platform.
>
> The data files are all on Linux partitions and accessed from Windows
> using samba.
>
> I have to use the lowest security protocol for Windows to access the
> data.
>
> Today, I discovered that from both Windows I could not longer access
> the data.
>
> Eventually I powered down and then up again using a drive last cloned
> in December 2022.
>
> Everything worked perfectly.
>
> So it seems an update has clobbered my machine.
>
> Has anyone else using samba suffered from this problem?

Check the windows update has not disabled the "insecure" SMB1 client...
there is a program (that you can turn off) that does that periodically!

Got setings -> apps and features - Optional Features -> More windows
features (down the bottom).

Then scroll down to SMB 1.0/CIFS File Sharing Support

Turn off the "Automatic Removal", bit and turn on the Client / server as
required.

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

On 3/10/2023 2:25 PM, pinnerite wrote:
> For many years I have had to retain two Windows virtual machines,
> running on a Linux host and VirtualBox.
>
> I need Windows XP for a large home-grown 16 bit programe and for a
> programme that drives a Fujitsu cut-sheet feeder-scanner.
>
> Windows 10 is for professional software not available on any other
> platform.
>
> The data files are all on Linux partitions and accessed from Windows
> using samba.
>
> I have to use the lowest security protocol for Windows to access the
> data.
>
> Today, I discovered that from both Windows I could not longer access
> the data.
>
> Eventually I powered down and then up again using a drive last cloned
> in December 2022.
>
> Everything worked perfectly.
>
> So it seems an update has clobbered my machine.
>
> Has anyone else using samba suffered from this problem?
>
> TIA, Alan

There is SMB1, SMB2, SMB3.

WinXP has only SMB1. Win10 supports all three.

The three of them aren't that much different, it's just
that the later versions of SAMBA support operation
across the Internet better, by using better crypto.

In Win10

Start : Run : control # Make control panel icon appear on task bar
# Right click the icon, select "Pin to Taskbar"

Programs and Features : Windows Features # Look for the SMB1 item, switch on two of three lines
# You want the "automatic removal of this feature" to
# be unticked.

In services.msc on Win10, there are two services beginning
with the word "Function" in their name. One of them has
the modern version of nameserving in it (so you can refer
to your machines by their symbolic name).

Now, having checked all of that, the latest twist in the
saga, is the more modern Windows OSes "brow beat" their legacy
OS friends.

If Windows 11 comes up first on a network, it will win
the network browser election (become the Master), which is
normal. But having done so, it will kick the shit out of
WinXP or Windows 7 when they come up. The modern OSes ensure
that the other OSes can't see anything.

I noticed, that if you start the legacy OSes first, one of
them becomes the network browser master, and the more modern
OSes then play nicely with the protocol.

But generally speaking, it is mostly a waste of time thinking
symbolic access will work.

nautilus smb://wallace/shared # You cannot expect this to work.
# The network neighbourhood icon, never works on any box

nautilus smb://102.168.0.2/shared # This works.

On Windows, the name might work. Sometimes.

explorer.exe \\wallace\shared # Works occasionally

explorer.exe \\192.168.0.2\shared # Works a bit better

Some VM hosts, don't use the same subnets as the
rest of your physical machines. To make Win10 Guest
play nicely, you can modify the netmask with a Powershell
command. Then, your computing solutions can see one another.

But generally, it's a mess, and they only seek to make it worse
not better.

For the person at Microsoft maintaining this stuff, the
versions and dialects of SAMBA means the test matrix
(proving it works) is huge. On the Linux side, nobody
cares any more. It will remain in the same broken state
from one release to the next. At the pinnacle of Linux SAMBA
achievement, there was one release where it all worked.
You could use the GUI, and the automation would wire up
the needed bits (install package manager items for you),
and it could "just work". But all of that work slipped
back into the software ooze. The web articles on setting
up a client manually, the suggestions may or may not work.
You might need to be added to a particular group (sambausers?).

Paul

pinnerite wrote:
> For many years I have had to retain two Windows virtual machines,
> running on a Linux host and VirtualBox.
>
> I need Windows XP for a large home-grown 16 bit programe and for a
> programme that drives a Fujitsu cut-sheet feeder-scanner.
>
> Windows 10 is for professional software not available on any other
> platform.
>
> The data files are all on Linux partitions and accessed from Windows
> using samba.
>
> I have to use the lowest security protocol for Windows to access the
> data.
>
> Today, I discovered that from both Windows I could not longer access
> the data.
>
> Eventually I powered down and then up again using a drive last cloned
> in December 2022.
>
> Everything worked perfectly.
>
> So it seems an update has clobbered my machine.
>
> Has anyone else using samba suffered from this problem?
>
> TIA, Alan
>
>
>
>
Bug #2009863
Upgrade from Samba 4.13 to 4.15 results in "dlopen(pam_winbind.so):
/lib/security/pam_winbind.so: cannot open shared object file: No such
file or directory"

https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2009863

On 10/03/2023 19:25, pinnerite wrote:
> For many years I have had to retain two Windows virtual machines,
> running on a Linux host and VirtualBox.
>
> I need Windows XP for a large home-grown 16 bit programe and for a
> programme that drives a Fujitsu cut-sheet feeder-scanner.
>
> Windows 10 is for professional software not available on any other
> platform.
>
> The data files are all on Linux partitions and accessed from Windows
> using samba.
>
> I have to use the lowest security protocol for Windows to access the
> data.
>
> Today, I discovered that from both Windows I could not longer access
> the data.
>
> Eventually I powered down and then up again using a drive last cloned
> in December 2022.
>
> Everything worked perfectly.
>
> So it seems an update has clobbered my machine.
>
> Has anyone else using samba suffered from this problem?
>
> TIA, Alan
>
>
>
>

This sounds like SMB v1.0 and SMB v2.0 has been disabled on the Windows
VMs so that SMB v3.0 is then the only "option" by default.

You need to turn SMB 1.0 and SMB 2.0 back on and you will get the usual
security warnings on the windows VMs.

Or you could upgrade Linux to support SMB 3.0 or it could just need
enabling?

https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server

https://www.osetc.com/en/how-to-configure-samba-server-to-use-smbv2-or-smbv3-protocol-in-linux.html

On Fri, 10 Mar 2023 14:55:29 -0500
Nic <Nic@none.net> wrote:

> On 3/10/23 14:25, pinnerite wrote:
> > For many years I have had to retain two Windows virtual machines,
> > running on a Linux host and VirtualBox.
> >
> > I need Windows XP for a large home-grown 16 bit programe and for a
> > programme that drives a Fujitsu cut-sheet feeder-scanner.
> >
> > Windows 10 is for professional software not available on any other
> > platform.
> >
> > The data files are all on Linux partitions and accessed from Windows
> > using samba.
> >
> > I have to use the lowest security protocol for Windows to access the
> > data.
> >
> > Today, I discovered that from both Windows I could not longer access
> > the data.
> >
> > Eventually I powered down and then up again using a drive last cloned
> > in December 2022.
> >
> > Everything worked perfectly.
> >
> > So it seems an update has clobbered my machine.
> >
> > Has anyone else using samba suffered from this problem?
> >
> > TIA, Alan
> >
> >
> >
> >
> Can you look at your history of updates in the update manager to see
> what update has caused this problem?

It looks like an update 2023-03-08 caused the problem.
The earliest timeshift entry is for the same date.

Presumably I can uninstall the installed version (2:4.15.12) from synaptic.

But how do I install version 2:4.13.17?

Oh! The Windows 10 problem was fixed by an smb.conf tweak.

I had had: server max protocol = NT1 I changed it to min.

--
Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.

On 3/10/2023 9:39 PM, Paul wrote:
> On 3/10/2023 2:25 PM, pinnerite wrote:
>> For many years I have had to retain two Windows virtual machines,
>> running on a Linux host and VirtualBox.
>>
>> I need Windows XP for a large home-grown 16 bit programe and for a
>> programme that drives a Fujitsu cut-sheet feeder-scanner.
>>
>> Windows 10 is for professional software not available on any other
>> platform.
>>
>> The data files are all on Linux partitions and accessed from Windows
>> using samba.
>>
>> I have to use the lowest security protocol for Windows to access the
>> data.
>>
>> Today, I discovered that from both Windows I could not longer access
>> the data.
>>
>> Eventually I powered down and then up again using a drive last cloned
>> in December 2022.
>>
>> Everything worked perfectly.
>>
>> So it seems an update has clobbered my machine.
>>
>> Has anyone else using samba suffered from this problem?
>>
>> TIA, Alan
>
> There is SMB1, SMB2, SMB3.

it took me quite a while to tip my Linux drive upright again.
(A restore from backup didn't quite do what it was supposed to do.)

I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
the 4.15 SAMBA came in. Initially, nothing worked.

I added these to smb.conf, as an experiment.

server min protocol = NT1
client min protocol = NT1
client lanman auth = yes
ntlm auth = yes

and EVERYTHING worked after that. My test share ("server test") on
Ubuntu 20.04.5 worked (it was set up a while back), as well as the
client worked with a Windows 11 that had SMBV1 turned on in Windows Features.

Paul

On 12/03/2023 07:06, Paul wrote:
> On 3/10/2023 9:39 PM, Paul wrote:
>> On 3/10/2023 2:25 PM, pinnerite wrote:
>>> For many years I have had to retain two Windows virtual machines,
>>> running on a Linux host and VirtualBox.
>>>
>>> I need Windows XP for a large home-grown 16 bit programe and for a
>>> programme that drives a Fujitsu cut-sheet feeder-scanner.
>>>
>>> Windows 10 is for professional software not available on any other
>>> platform.
>>>
>>> The data files are all on Linux partitions and accessed from Windows
>>> using samba.
>>>
>>> I have to use the lowest security protocol for Windows to access the
>>> data.
>>>
>>> Today, I discovered that from both Windows I could not longer access
>>> the data.
>>>
>>> Eventually I powered down and then up again using a drive last cloned
>>> in December 2022.
>>>
>>> Everything worked perfectly.
>>>
>>> So it seems an update has clobbered my machine.
>>>
>>> Has anyone else using samba suffered from this problem?
>>>
>>> TIA, Alan
>>
>> There is SMB1, SMB2, SMB3.
>
> it took me quite a while to tip my Linux drive upright again.
> (A restore from backup didn't quite do what it was supposed to do.)
>
> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
> the 4.15 SAMBA came in. Initially, nothing worked.
>
> I added these to smb.conf, as an experiment.
>
> server min protocol = NT1
> client min protocol = NT1
> client lanman auth = yes
> ntlm auth = yes
>
> and EVERYTHING worked after that. My test share ("server test") on
> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
> client worked with a Windows 11 that had SMBV1 turned on in Windows
> Features.
>
>    Paul
I remember having too do similar back in the day when I still used samba.

But I don't use it any more, not even for my windows VM.

You don't need it to access a local hard drive under virtual box. And my
NFS mounted server partitions appear as 'local drives' to windows.

--
Religion is regarded by the common people as true, by the wise as
foolish, and by the rulers as useful.

(Seneca the Younger, 65 AD)

On Sun, 12 Mar 2023 03:06:11 -0400
Paul <nospam@needed.invalid> wrote:

> On 3/10/2023 9:39 PM, Paul wrote:
> > On 3/10/2023 2:25 PM, pinnerite wrote:
> >> For many years I have had to retain two Windows virtual machines,
> >> running on a Linux host and VirtualBox.
> >>
> >> I need Windows XP for a large home-grown 16 bit programe and for a
> >> programme that drives a Fujitsu cut-sheet feeder-scanner.
> >>
> >> Windows 10 is for professional software not available on any other
> >> platform.
> >>
> >> The data files are all on Linux partitions and accessed from Windows
> >> using samba.
> >>
> >> I have to use the lowest security protocol for Windows to access the
> >> data.
> >>
> >> Today, I discovered that from both Windows I could not longer access
> >> the data.
> >>
> >> Eventually I powered down and then up again using a drive last cloned
> >> in December 2022.
> >>
> >> Everything worked perfectly.
> >>
> >> So it seems an update has clobbered my machine.
> >>
> >> Has anyone else using samba suffered from this problem?
> >>
> >> TIA, Alan
> >
> > There is SMB1, SMB2, SMB3.
>
> it took me quite a while to tip my Linux drive upright again.
> (A restore from backup didn't quite do what it was supposed to do.)
>
> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
> the 4.15 SAMBA came in. Initially, nothing worked.
>
> I added these to smb.conf, as an experiment.
>
> server min protocol = NT1
> client min protocol = NT1
> client lanman auth = yes
> ntlm auth = yes
>
> and EVERYTHING worked after that. My test share ("server test") on
> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
> client worked with a Windows 11 that had SMBV1 turned on in Windows Features.
>
> Paul

I just ran up a clean 21.1 installation.
Virtual XP still cannot access the Linux folders.

Alan

--
Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
running on an AMD Phenom II X4 Black edition processor with 16GB of
DRAM.

On Sun, 12 Mar 2023 15:46:45 +0000
pinnerite <pinnerite@gmail.com> wrote:

>On Sun, 12 Mar 2023 03:06:11 -0400
>Paul <nospam@needed.invalid> wrote:
>
>> On 3/10/2023 9:39 PM, Paul wrote:
>> > On 3/10/2023 2:25 PM, pinnerite wrote:
>> >> For many years I have had to retain two Windows virtual machines,
>> >> running on a Linux host and VirtualBox.
>> >>
>> >> I need Windows XP for a large home-grown 16 bit programe and for a
>> >> programme that drives a Fujitsu cut-sheet feeder-scanner.
>> >>
>> >> Windows 10 is for professional software not available on any other
>> >> platform.
>> >>
>> >> The data files are all on Linux partitions and accessed from Windows
>> >> using samba.
>> >>
>> >> I have to use the lowest security protocol for Windows to access the
>> >> data.
>> >>
>> >> Today, I discovered that from both Windows I could not longer access
>> >> the data.
>> >>
>> >> Eventually I powered down and then up again using a drive last cloned
>> >> in December 2022.
>> >>
>> >> Everything worked perfectly.
>> >>
>> >> So it seems an update has clobbered my machine.
>> >>
>> >> Has anyone else using samba suffered from this problem?
>> >>
>> >> TIA, Alan
>> >
>> > There is SMB1, SMB2, SMB3.
>>
>> it took me quite a while to tip my Linux drive upright again.
>> (A restore from backup didn't quite do what it was supposed to do.)
>>
>> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
>> the 4.15 SAMBA came in. Initially, nothing worked.
>>
>> I added these to smb.conf, as an experiment.
>>
>> server min protocol = NT1
>> client min protocol = NT1
>> client lanman auth = yes
>> ntlm auth = yes
>>
>> and EVERYTHING worked after that. My test share ("server test") on
>> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
>> client worked with a Windows 11 that had SMBV1 turned on in Windows Features.
>>
>> Paul
>
>I just ran up a clean 21.1 installation.
>Virtual XP still cannot access the Linux folders.
>
>Alan
>
>
>--
>Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
>running on an AMD Phenom II X4 Black edition processor with 16GB of
>DRAM.

Given that you are using a m$ product to drive a machine, it might be more cost effective to look at some of those dell laptop latitudes selling for around $100. The cost of the machine includes a license for w7 or w10, the cost of the machine is almost equal to the cost of the license. Using a dedicated machine would seem to answer your problem.

On 3/12/23 08:46, pinnerite wrote:
> On Sun, 12 Mar 2023 03:06:11 -0400
> Paul <nospam@needed.invalid> wrote:
>
>> On 3/10/2023 9:39 PM, Paul wrote:
>>> On 3/10/2023 2:25 PM, pinnerite wrote:
>>>> For many years I have had to retain two Windows virtual machines,
>>>> running on a Linux host and VirtualBox.
>>>>
>>>> I need Windows XP for a large home-grown 16 bit programe and for a
>>>> programme that drives a Fujitsu cut-sheet feeder-scanner.
>>>>
>>>> Windows 10 is for professional software not available on any other
>>>> platform.
>>>>
>>>> The data files are all on Linux partitions and accessed from Windows
>>>> using samba.
>>>>
>>>> I have to use the lowest security protocol for Windows to access the
>>>> data.
>>>>
>>>> Today, I discovered that from both Windows I could not longer access
>>>> the data.
>>>>
>>>> Eventually I powered down and then up again using a drive last cloned
>>>> in December 2022.
>>>>
>>>> Everything worked perfectly.
>>>>
>>>> So it seems an update has clobbered my machine.
>>>>
>>>> Has anyone else using samba suffered from this problem?
>>>>
>>>> TIA, Alan
>>>
>>> There is SMB1, SMB2, SMB3.
>>
>> it took me quite a while to tip my Linux drive upright again.
>> (A restore from backup didn't quite do what it was supposed to do.)
>>
>> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
>> the 4.15 SAMBA came in. Initially, nothing worked.
>>
>> I added these to smb.conf, as an experiment.
>>
>> server min protocol = NT1
>> client min protocol = NT1
>> client lanman auth = yes
>> ntlm auth = yes
>>
>> and EVERYTHING worked after that. My test share ("server test") on
>> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
>> client worked with a Windows 11 that had SMBV1 turned on in Windows Features.
>>
>> Paul
>
> I just ran up a clean 21.1 installation.
> Virtual XP still cannot access the Linux folders.
>
> Alan

That is normal behavior for Windows. I think there
maybe some Windows add-on that lets Windows read Linux files
but most usable Linux distributions can read the various
Windows file systems. My solution to interchange between the
two systems is a partition in a Windows readable format where
I copy files that I thought I wanted to use on Windows to the
xchange partition. Windows prefers to be blind to Linux.

bliss - “Nearly any fool can use a GNU/Linux computer. Many do.”
After all here I am... Again
--
bliss dash SF 4 ever at dslextreme dot com

On Mon, 13 Mar 2023 03:15:30 +1100, Nic <Nic@none.net> wrote:

> On Sun, 12 Mar 2023 15:46:45 +0000
> pinnerite <pinnerite@gmail.com> wrote:
>
>> On Sun, 12 Mar 2023 03:06:11 -0400
>> Paul <nospam@needed.invalid> wrote:
>>
>>> On 3/10/2023 9:39 PM, Paul wrote:
>>> > On 3/10/2023 2:25 PM, pinnerite wrote:
>>> >> For many years I have had to retain two Windows virtual machines,
>>> >> running on a Linux host and VirtualBox.
>>> >>
>>> >> I need Windows XP for a large home-grown 16 bit programe and for a
>>> >> programme that drives a Fujitsu cut-sheet feeder-scanner.
>>> >>
>>> >> Windows 10 is for professional software not available on any other
>>> >> platform.
>>> >>
>>> >> The data files are all on Linux partitions and accessed from Windows
>>> >> using samba.
>>> >>
>>> >> I have to use the lowest security protocol for Windows to access the
>>> >> data.
>>> >>
>>> >> Today, I discovered that from both Windows I could not longer access
>>> >> the data.
>>> >>
>>> >> Eventually I powered down and then up again using a drive last
>>> cloned
>>> >> in December 2022.
>>> >>
>>> >> Everything worked perfectly.
>>> >>
>>> >> So it seems an update has clobbered my machine.
>>> >>
>>> >> Has anyone else using samba suffered from this problem?
>>> >>
>>> >> TIA, Alan
>>> >
>>> > There is SMB1, SMB2, SMB3.
>>>
>>> it took me quite a while to tip my Linux drive upright again.
>>> (A restore from backup didn't quite do what it was supposed to do.)
>>>
>>> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
>>> the 4.15 SAMBA came in. Initially, nothing worked.
>>>
>>> I added these to smb.conf, as an experiment.
>>>
>>> server min protocol = NT1
>>> client min protocol = NT1
>>> client lanman auth = yes
>>> ntlm auth = yes
>>>
>>> and EVERYTHING worked after that. My test share ("server test") on
>>> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
>>> client worked with a Windows 11 that had SMBV1 turned on in Windows
>>> Features.
>>>
>>> Paul
>>
>> I just ran up a clean 21.1 installation.
>> Virtual XP still cannot access the Linux folders.
>>
>> Alan
>>
>>
>> --
>> Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
>> running on an AMD Phenom II X4 Black edition processor with 16GB of
>> DRAM.
>
> Given that you are using a m$ product to drive a machine, it might be
> more cost effective to look at some of those dell laptop latitudes
> selling for around $100. The cost of the machine includes a license for
> w7 or w10, the cost of the machine is almost equal to the cost of the
> license.

A W10 license doesn't cost anything like that.

> Using a dedicated machine would seem to answer your problem.

On 3/12/23 13:51, Rod Speed wrote:
> On Mon, 13 Mar 2023 03:15:30 +1100, Nic <Nic@none.net> wrote:
>
>> On Sun, 12 Mar 2023 15:46:45 +0000
>> pinnerite <pinnerite@gmail.com> wrote:
>>
>>> On Sun, 12 Mar 2023 03:06:11 -0400
>>> Paul <nospam@needed.invalid> wrote:
>>>
>>>> On 3/10/2023 9:39 PM, Paul wrote:
>>>> > On 3/10/2023 2:25 PM, pinnerite wrote:
>>>> >> For many years I have had to retain two Windows virtual machines,
>>>> >> running on a Linux host and VirtualBox.
>>>> >>
>>>> >> I need Windows XP for a large home-grown 16 bit programe and for a
>>>> >> programme that drives a Fujitsu cut-sheet feeder-scanner.
>>>> >>
>>>> >> Windows 10 is for professional software not available on any other
>>>> >> platform.
>>>> >>
>>>> >> The data files are all on Linux partitions and accessed from
>>>> Windows
>>>> >> using samba.
>>>> >>
>>>> >> I have to use the lowest security protocol for Windows to access
>>>> the
>>>> >> data.
>>>> >>
>>>> >> Today, I discovered that from both Windows I could not longer
>>>> access
>>>> >> the data.
>>>> >>
>>>> >> Eventually I powered down and then up again using a drive last
>>>> cloned
>>>> >> in December 2022.
>>>> >>
>>>> >> Everything worked perfectly.
>>>> >>
>>>> >> So it seems an update has clobbered my machine.
>>>> >>
>>>> >> Has anyone else using samba suffered from this problem?
>>>> >>
>>>> >> TIA, Alan
>>>> >
>>>> > There is SMB1, SMB2, SMB3.
>>>>
>>>> it took me quite a while to tip my Linux drive upright again.
>>>> (A restore from backup didn't quite do what it was supposed to do.)
>>>>
>>>> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
>>>> the 4.15 SAMBA came in. Initially, nothing worked.
>>>>
>>>> I added these to smb.conf, as an experiment.
>>>>
>>>> server min protocol = NT1
>>>> client min protocol = NT1
>>>> client lanman auth = yes
>>>> ntlm auth = yes
>>>>
>>>> and EVERYTHING worked after that. My test share ("server test") on
>>>> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
>>>> client worked with a Windows 11 that had SMBV1 turned on in Windows
>>>> Features.
>>>>
>>>>     Paul
>>>
>>> I just ran up a clean 21.1 installation.
>>> Virtual XP still cannot access the Linux folders.
>>>
>>> Alan
>>>
>>>
>>> --
>>> Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
>>> running on an AMD Phenom II X4 Black edition processor with 16GB of
>>> DRAM.
>>
>> Given that you are using a m$ product to drive a machine, it might be
>> more cost effective to look at some of those dell laptop latitudes
>> selling for around $100. The cost of the machine includes a license
>> for w7 or w10, the cost of the machine is almost equal to the cost of
>> the license.
>
> A W10 license doesn't cost anything like that.
>
>> Using a dedicated machine would seem to answer your problem.
What does a license cost?

On Mon, 13 Mar 2023 05:44:55 +1100, Nic <Nic@none.net> wrote:

> On 3/12/23 13:51, Rod Speed wrote:
>> On Mon, 13 Mar 2023 03:15:30 +1100, Nic <Nic@none.net> wrote:
>>
>>> On Sun, 12 Mar 2023 15:46:45 +0000
>>> pinnerite <pinnerite@gmail.com> wrote:
>>>
>>>> On Sun, 12 Mar 2023 03:06:11 -0400
>>>> Paul <nospam@needed.invalid> wrote:
>>>>
>>>>> On 3/10/2023 9:39 PM, Paul wrote:
>>>>> > On 3/10/2023 2:25 PM, pinnerite wrote:
>>>>> >> For many years I have had to retain two Windows virtual machines,
>>>>> >> running on a Linux host and VirtualBox.
>>>>> >>
>>>>> >> I need Windows XP for a large home-grown 16 bit programe and for a
>>>>> >> programme that drives a Fujitsu cut-sheet feeder-scanner.
>>>>> >>
>>>>> >> Windows 10 is for professional software not available on any other
>>>>> >> platform.
>>>>> >>
>>>>> >> The data files are all on Linux partitions and accessed from
>>>>> Windows
>>>>> >> using samba.
>>>>> >>
>>>>> >> I have to use the lowest security protocol for Windows to access
>>>>> the
>>>>> >> data.
>>>>> >>
>>>>> >> Today, I discovered that from both Windows I could not longer
>>>>> access
>>>>> >> the data.
>>>>> >>
>>>>> >> Eventually I powered down and then up again using a drive last
>>>>> cloned
>>>>> >> in December 2022.
>>>>> >>
>>>>> >> Everything worked perfectly.
>>>>> >>
>>>>> >> So it seems an update has clobbered my machine.
>>>>> >>
>>>>> >> Has anyone else using samba suffered from this problem?
>>>>> >>
>>>>> >> TIA, Alan
>>>>> >
>>>>> > There is SMB1, SMB2, SMB3.
>>>>>
>>>>> it took me quite a while to tip my Linux drive upright again.
>>>>> (A restore from backup didn't quite do what it was supposed to do.)
>>>>>
>>>>> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
>>>>> the 4.15 SAMBA came in. Initially, nothing worked.
>>>>>
>>>>> I added these to smb.conf, as an experiment.
>>>>>
>>>>> server min protocol = NT1
>>>>> client min protocol = NT1
>>>>> client lanman auth = yes
>>>>> ntlm auth = yes
>>>>>
>>>>> and EVERYTHING worked after that. My test share ("server test") on
>>>>> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
>>>>> client worked with a Windows 11 that had SMBV1 turned on in Windows
>>>>> Features.
>>>>>
>>>>> Paul
>>>>
>>>> I just ran up a clean 21.1 installation.
>>>> Virtual XP still cannot access the Linux folders.
>>>>
>>>> Alan
>>>>
>>>>
>>>> -- Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
>>>> running on an AMD Phenom II X4 Black edition processor with 16GB of
>>>> DRAM.
>>>
>>> Given that you are using a m$ product to drive a machine, it might be
>>> more cost effective to look at some of those dell laptop latitudes
>>> selling for around $100. The cost of the machine includes a license
>>> for w7 or w10, the cost of the machine is almost equal to the cost of
>>> the license.
>>
>> A W10 license doesn't cost anything like that.
>>
>>> Using a dedicated machine would seem to answer your problem.
> What does a license cost?

$5 or so, Rumm listed it recently.

On Sun, 12 Mar 2023 03:06:11 -0400
Paul <nospam@needed.invalid> wrote:

> On 3/10/2023 9:39 PM, Paul wrote:
> > On 3/10/2023 2:25 PM, pinnerite wrote:
> >> For many years I have had to retain two Windows virtual machines,
> >> running on a Linux host and VirtualBox.
> >>
> >> I need Windows XP for a large home-grown 16 bit programe and for a
> >> programme that drives a Fujitsu cut-sheet feeder-scanner.
> >>
> >> Windows 10 is for professional software not available on any other
> >> platform.
> >>
> >> The data files are all on Linux partitions and accessed from Windows
> >> using samba.
> >>
> >> I have to use the lowest security protocol for Windows to access the
> >> data.
> >>
> >> Today, I discovered that from both Windows I could not longer access
> >> the data.
> >>
> >> Eventually I powered down and then up again using a drive last cloned
> >> in December 2022.
> >>
> >> Everything worked perfectly.
> >>
> >> So it seems an update has clobbered my machine.
> >>
> >> Has anyone else using samba suffered from this problem?
> >>
> >> TIA, Alan
> >
> > There is SMB1, SMB2, SMB3.
>
> it took me quite a while to tip my Linux drive upright again.
> (A restore from backup didn't quite do what it was supposed to do.)
>
> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
> the 4.15 SAMBA came in. Initially, nothing worked.
>
> I added these to smb.conf, as an experiment.
>
> server min protocol = NT1
> client min protocol = NT1
> client lanman auth = yes
> ntlm auth = yes
>
> and EVERYTHING worked after that. My test share ("server test") on
> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
> client worked with a Windows 11 that had SMBV1 turned on in Windows Features.
>
> Paul

So on Mint 21.1, that seems to work for Windows 10 but not for XP.

I tried using VBox's shared directories. They show up all right.
Some programs could be made to run but the two important programs that
make me still need XP just wouldn't.

I have gone back to 20.3 until I can unblock this problem.

I may be some time.

Regards, Alan

--
Mint 20.3, kernel 5.4.0-139-generic, Cinnamon 5.2.7
running on an AMD Phenom II X4 Black edition processor with 16GB of
DRAM.

On 3/12/2023 11:46 AM, pinnerite wrote:
> On Sun, 12 Mar 2023 03:06:11 -0400
> Paul <nospam@needed.invalid> wrote:
>
>> On 3/10/2023 9:39 PM, Paul wrote:
>>> On 3/10/2023 2:25 PM, pinnerite wrote:
>>>> For many years I have had to retain two Windows virtual machines,
>>>> running on a Linux host and VirtualBox.
>>>>
>>>> I need Windows XP for a large home-grown 16 bit programe and for a
>>>> programme that drives a Fujitsu cut-sheet feeder-scanner.
>>>>
>>>> Windows 10 is for professional software not available on any other
>>>> platform.
>>>>
>>>> The data files are all on Linux partitions and accessed from Windows
>>>> using samba.
>>>>
>>>> I have to use the lowest security protocol for Windows to access the
>>>> data.
>>>>
>>>> Today, I discovered that from both Windows I could not longer access
>>>> the data.
>>>>
>>>> Eventually I powered down and then up again using a drive last cloned
>>>> in December 2022.
>>>>
>>>> Everything worked perfectly.
>>>>
>>>> So it seems an update has clobbered my machine.
>>>>
>>>> Has anyone else using samba suffered from this problem?
>>>>
>>>> TIA, Alan
>>>
>>> There is SMB1, SMB2, SMB3.
>>
>> it took me quite a while to tip my Linux drive upright again.
>> (A restore from backup didn't quite do what it was supposed to do.)
>>
>> I did a do-partial-upgrade on a 20.04.3 to 20.04.5 and
>> the 4.15 SAMBA came in. Initially, nothing worked.
>>
>> I added these to smb.conf, as an experiment.
>>
>> server min protocol = NT1
>> client min protocol = NT1
>> client lanman auth = yes
>> ntlm auth = yes
>>
>> and EVERYTHING worked after that. My test share ("server test") on
>> Ubuntu 20.04.5 worked (it was set up a while back), as well as the
>> client worked with a Windows 11 that had SMBV1 turned on in Windows Features.
>>
>> Paul
>
> I just ran up a clean 21.1 installation.
> Virtual XP still cannot access the Linux folders.
>
> Alan

OK, the 4.15 SAMBA is a rat bastard. But I did get around it.

[Picture]

https://i.postimg.cc/W1f4W1Mj/drop-that-security.gif

The evidence suggests there is an authentication problem
when logging into LM211 with its 4.15 Samba version. But doing my Googling,
there is more than one way to authenticate, so I am unable to
determine what "method" happens to be failing. It might be PAM,
it might be something else. But ripping the arms off the thing,
makes it behave. You can declare the share LM211 is offering,
to be a public one.

LM211 was already on my hard drive, and all it
required is a giant update to prepare for experiments.
This is the hard drive that did not restore nicely from
a backup, but ripping more arms off that, got it running again :-)
The root cause there, was (apparently) leaving some GPT partition
tables on a drive (not sufficient cleaning) before starting
brand new experiments. A mistake made months ago. Oops.
I had to clean it with a hex editor.

Paul

On 3/12/2023 12:50 PM, Bobbie Sellers wrote:

>     That is normal behavior for Windows.  I think there
> maybe some Windows add-on that lets Windows read Linux files
> but most usable Linux distributions can read the various
> Windows file systems.  My solution to interchange between the
> two systems is a partition in a Windows readable format where
> I copy files that I thought I wanted to use on Windows to the
> xchange partition.   Windows prefers to be blind to Linux.
>
> bliss - “Nearly any fool can use a GNU/Linux computer. Many do.”
>             After all here I am...  Again
>

Such a bleak world you live in.

I don't have a problem getting around.

I have a hex editor on Windows that really works.
I can burrow into /dev/sda1. I can burrow into /dev/sda (whole disk scan).
I can edit whole disks. For example, I just removed leftover GPT partition
tables from a disk, using the hex editor.

In addition, I have 7ZIP (Igor Pavlov), which also can burrow into anything.
It can burrow into an EXT4 and pull files out. It can burrow into a dd'ed partition
and pull files out. It can take a .docx (or FOSS equivalent) and pull
the images you pasted into the document, out of the document for examination.
It can open a WIM. It can open a .vhd . And other virtual containers (with
an EXT4 inside). It can open an EXE file and you can look for icon resources
in there. it can open an MSI file (a Windows installer thing), but it does not
render the naming in a sensible manner (there is a separate tool written by
a USENET poster, for that).

There aren't too many formats I can't rip to bits.

So I don't know where you got the idea the world
was a limited place, with limited possibilities.
The world is your oyster. Enjoy.

I can set up portable Cygwin applications, without
keeping the Cygwin tree or being limited to keeping them
in the Cygwin tree. That's how I can run "disktype.exe"
on Windows -- it's a Cygwin port.

I was also doing things this way, when I was on a Mac G4
and had virtualization and foreign environments. All in
the name of "having many Swiss army knives". I had Linux
on the G4, back when Ubuntu had a PPC version of the LiveDVD.

When I was on a Sparc at work, I had SoftWindows for company.
When I was on a Mac, I had Connectix Virtual PC. The same Virtual PC
that was bought by Microsoft. That's why they bought Connectix
and chucked away their hardware business.

Windows 10 and Windows 11 have the bash shell, complete with graphics
capability (WSLg). On a regular basis, you can see a Ubuntu Firefox running
on my Windows Desktop via bash shell. There is a little Penguin icon
on the Firefox icon when I do that :-)

Paul

On 3/12/2023 2:44 PM, Nic wrote:
> On 3/12/23 13:51, Rod Speed wrote:
>> On Mon, 13 Mar 2023 03:15:30 +1100, Nic <Nic@none.net> wrote:
>>
>> A W10 license doesn't cost anything like that.
>>
>>> Using a dedicated machine would seem to answer your problem.
> What does a license cost?

There are sources of discount licenses. People would not be
interested in them, unless they were $30 or less. Versus $100
or $150 or whatever, at retail.

It's pretty hard to tell just where these licenses have come
from, because Microsoft does not offer a public tool for
"lineage" work. I don't think MGAdiag will tell you where they
got that license from.

And these licenses are not VLK, or they'd be broken by now.
These are not materials from a "rogue mom and pop computer store".
And considering the price, they're not from a MSDN subscription
either. With an MSDN subscription, you get some licenses with that.

Paul

On 3/12/23 14:47, Paul wrote:
> On 3/12/2023 12:50 PM, Bobbie Sellers wrote:
>
>>      That is normal behavior for Windows.  I think there
>> maybe some Windows add-on that lets Windows read Linux files
>> but most usable Linux distributions can read the various
>> Windows file systems.  My solution to interchange between the
>> two systems is a partition in a Windows readable format where
>> I copy files that I thought I wanted to use on Windows to the
>> xchange partition.   Windows prefers to be blind to Linux.
>>
>> bliss - “Nearly any fool can use a GNU/Linux computer. Many do.”
>>              After all here I am...  Again
>>
>
> Such a bleak world you live in.
Well I am 85 and took up the Commmodore 64 in my 50s, never had
any Computer Science classes and am physically challenged due to several
conditions. What I see is nothing like the future we hoped for as
fossil fuel use messed up the Global Cllimate and Exxon sat on that
report for quite a while.

>
> I don't have a problem getting around.

I do! Carrying my laundry to the machine the building
basement exhausts me but I do it multiple times every month.

>
> I have a hex editor on Windows that really works.

And I had one on the Amiga to do patches on executable files.

> I can burrow into /dev/sda1. I can burrow into /dev/sda (whole disk scan).
> I can edit whole disks. For example, I just removed leftover GPT partition
> tables from a disk, using the hex editor.
>

> In addition, I have 7ZIP (Igor Pavlov), which also can burrow into
> anything.
> It can burrow into an EXT4 and pull files out. It can burrow into a
> dd'ed partition
> and pull files out. It can take a .docx (or FOSS equivalent) and pull
> the images you pasted into the document, out of the document for
> examination.
> It can open a WIM. It can open a .vhd . And other virtual containers (with
> an EXT4 inside). It can open an EXE file and you can look for icon
> resources
> in there. it can open an MSI file (a Windows installer thing), but it
> does not
> render the naming in a sensible manner (there is a separate tool written by
> a USENET poster, for that).
>
> There aren't too many formats I can't rip to bits.

Pinnerite wants to read linux files from a Windows installation.
Tell him how to do it. Ah I see that you did that with 7Zip
which can recognize and read ext4 files.

>
> So I don't know where you got the idea the world
> was a limited place, with limited possibilities.
> The world is your oyster. Enjoy.

Enjoyment exhausts me. Holding up a book to read
it is exhausting though i get more pleasure from reading
than any other source.
>
> I can set up portable Cygwin applications, without
> keeping the Cygwin tree or being limited to keeping them
> in the Cygwin tree. That's how I can run "disktype.exe"
> on Windows -- it's a Cygwin port.
>
> I was also doing things this way, when I was on a Mac G4
> and had virtualization and foreign environments. All in
> the name of "having many Swiss army knives". I had Linux
> on the G4, back when Ubuntu had a PPC version of the LiveDVD.
>
> When I was on a Sparc at work, I had SoftWindows for company.
> When I was on a Mac, I had Connectix Virtual PC. The same Virtual PC
> that was bought by Microsoft. That's why they bought Connectix
> and chucked away their hardware business.
>
> Windows 10 and Windows 11 have the bash shell, complete with graphics
> capability (WSLg). On a regular basis, you can see a Ubuntu Firefox running
> on my Windows Desktop via bash shell. There is a little Penguin icon
> on the Firefox icon when I do that :-)
>
>    Paul

Congratulations. I can barely keep up with my email but I manage to
keep my machine updated. I hope to update my more powerful
6540 sometime this year. But I am tasked with removing my late room
mates's leftover clothing and books this year as well. Sometimes
friends give me things and I hope for a Ryzen with 6 or 8 cores.

bliss - on the ever-faithful Dell Latitude E7450, PCLinuxOS 2022
KDE Plasma 5.27.2 Kernel Version: 6.1.16-pclos1 (64-bit)
KDE Frameworks 5.103.0 - Qt Version: 5.15.6
Graphics : X11 - Mesa Intel® HD Graphics 5500
15.5 GiB of RAM CPU 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Actually 2 real cores and 2 virtual cores.

--
bliss dash SF 4 ever at dslextreme dot com