New
#1
Samba connectivity
I'm still working with a problem I've mentioned here before: my Windows boxes have lost connectivity to my Samba box since adopting Win 10. There are dozens of flavors of this problem discussed online, and dozens of solutions, none of which have worked for me.
Describing what goes on in two of my hosts, GILGAMESH (Win 10 Pro) and ABELARD (Fedora Linux):
GILGAMESH: Full Internet connectivity via router. Can SSH into ABELARD via PuTTY. Can FTP into ABELARD via WS-FTP. Host ABELARD appears in File Explorer->Network. Clicking on its icon produces error 80070035, network path not found. This PC->Add a Network Location gives same result.
ABELARD: Has Samba 4.7.3 aboard, with two shares configured for access by the Win machines. Filesystem, including the shares, is accessible from GILGAMESH via FTP, but not via Samba.
Samba access was normal until the Windows machines were switched from Win 7 to Win 10.
smb.conf file attached. Suggestions?
rj