XPost: alt.os.linux.mint, alt.os.linux.mageia, uk.d-i-y   
   From: Nic@none.net   
      
   On 3/12/23 13:51, Rod Speed wrote:   
   > On Mon, 13 Mar 2023 03:15:30 +1100, Nic  wrote:   
   >   
   >> On Sun, 12 Mar 2023 15:46:45 +0000   
   >> pinnerite  wrote:   
   >>   
   >>> On Sun, 12 Mar 2023 03:06:11 -0400   
   >>> 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 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?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)