Thank You for the expert analysis of the problem.
One of the problems with searching the net is that most of time there is
advice that is correct but out of date or wrong OS etc. and they are not
clearly labeled.

We have downloaded the most current copy of Sama-* and all boxes are up
to date.
I will remove the statement form the smb.conf.  When we tested it there
was no differences on the network picture.

WE took down the fire wall on all boxes and after a reboot it made no
difference.  In the Firewall The samba box was checked and the required
ports were enabled.

We have one system still running SL 5.10 because it has a "mongrel" set
of libs so we can run spice, a filter design program and other
applications. It uses VMware and we have a lot of olders OS to allow us
to support projects that are 0ver 20 years old.  It uses samba to
communicate from the old windows OS to the SL 5.10.  This has worked
well for a long time.

What on the network controls the samba server vers a samba client.  The
documentation on this is sparse.

Larry Linder

On Thu, 2020-06-11 at 20:52 +0000, Mark Rousell wrote:
> (I've been forced to post this via the Outlook.com web UI. It's vile. Sorry.)
> 
> On 11/06/2020 15:34, Larry Linder wrote:
> > When I did a search on the internet for the problem.  There were a
> > number of reports from other distributions of linux 6.10 with the same
> > problem.
> >
> > I tried their recommended fix but did not work.
> > They added aline into smb.conf.
> >    client max protocol = NT1  
> >
> > They also indicated that windows 10 had an issue with samba.  Several of
> > our laptops running a stripped Windows 10 can see the server but not
> > now.
> 
> I don't know if this will be helpful to you here and now but here goes. I believe that the "client max protocol = NT1" line limits the SMB version to 1. However, SMB1 is now deprecated in Windows 10[1]. So, with a current default Windows 10 configuration combined with "client max protocol = NT1" in your smb.conf files, your Linux and Windows boxes won't be able to talk to each other. Furthermore, Samba itself is in the process of deprecating SMB1 with a view to removing it entirely in due course, if I remember correctly.
> 
> Ideally you should force a higher version of SMB in Samba such as SMB2 or SMB3 (as long as all your Linuxes have an up to date Samba).
> 
> Alternatively you can force install SMB1 in your Windows 10 boxes but this is definitely not recommended[2].
> 
> To re-enable SMB1 in Windows 10, use the 'Turn Windows features on or off' tool to re-enable it. You can separately enable or disable SMB1 client and server modes in W10. You can also do it at the command line via PowerShell if you wish (Google for instructions).
> 
> 
> 
> 
> Footnotes:-
> 1: 'SMBv1 is not installed by default in Windows 10 version 1709, Windows Server version 1709 and later versions' <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.microsoft.com_en-2Dus_windows-2Dserver_storage_file-2Dserver_troubleshoot_smbv1-2Dnot-2Dinstalled-2Dby-2Ddefault-2Din-2Dwindows&d=DwICAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=T3R6xI1p_QnptvR2voEWzP3OvAa7Zu4tdnDlvYmyx-c&s=os-loLPdUvtGF-hTs5eE2gbAhI_8NAdvwpKX7cFXiFs&e= >
> 
> 2: 'Stop using SMB1' <https://urldefense.proofpoint.com/v2/url?u=https-3A__techcommunity.microsoft.com_t5_storage-2Dat-2Dmicrosoft_stop-2Dusing-2Dsmb1_ba-2Dp_425858&d=DwICAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=T3R6xI1p_QnptvR2voEWzP3OvAa7Zu4tdnDlvYmyx-c&s=tevjBK17-Va8Sh0BWEhgZQ28erLyvUEhDFwPchcFw_k&e= >