XPost: alt.os.linux.mint, alt.os.linux.mageia, uk.d-i-y   
   From: i.love@spam.me   
      
   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-se   
   ver/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server   
      
   https://www.osetc.com/en/how-to-configure-samba-server-to-use-sm   
   v2-or-smbv3-protocol-in-linux.html   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)