XPost: alt.os.linux.mint, alt.os.linux.mageia, uk.d-i-y   
   From: nospam@needed.invalid   
      
   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   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)