Windows 10: 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

:)

 

It is visable in windows 7 file explorer, but not visable in windows 10 file explorer.

there is a known problem:

Cannot
connect to CIFS / SMB / Samba Network Shares & Shared Folders in Windows 10 after update 1511/10586

but you should be able to connect via IP address or share name.

 

Windows 10 Network Computers missing on some computers (9 networked together)

Cannot connect to CIFS
SMB Samba Network Shares & Shared Folders in Windows 10 after update 1511 10586

That's the proper link to what I copy pasted.

 

Did you change smb.conf after installing win 10?

Why you have:

hosts allow = 127. 192.168.1. ? <- seems wrong anyway this can surely cause problems try to comment it it may work then

Does a folder named /buraid exists in fedora?

; browseable = yes <- why commented ?

It seems you're playing a bit with smb.conf maybe without knowing what you're touching,

is smb1 enabled or disable in win 10?

 

I've made numerous changes in trying out the various "solutions" I've found online.
"hosts allow = 127." dates back to when the system was working. "192.168.1." was a recent attempt to enable all the hosts on my network.
Yes, /buraid is the share that I've been using all along for backups, and it was accessible before this problem arose. It is still accessible from Windows via PuTTY or FTP.
The browseable line has been commented out since before the problem: no change there.
SMB 1 is turned on in Windows, with its automatic removal turned off.

 

Have you tried to connect with file explorer from windows with:

smb://192.168.xxx.xxx <- in linux

//192.168.xxx.xxx <- what is fedora's lan address ?

 

Yes: no response if I do that in the filename ribbon. If I go to This PC->Add a network location and enter that, I get "The folder you entered does not appear to be valid." If i double-click on host Abelard's icon in the "Computer" block I get error 80070035, network path not found.

 

have you removed 192.168.1. ?

what is fedora's lan address ?

 

Yes, I've removed 192.168.1.
Abelard, the Fedora host, is 192.168.1.13. Gilgamesh the Win 10 host, is 192.168.1.111.

 

Ok can only give you some advices at this point

commend all "host allow"
make sure the shared folder have right permissions youre using a folder in root would try something in your home folder
make sure the windows user is also a smb user in linux

 

OK, I've commented out the host lines. Full permissions are present in the shares, and the user is the same in both machines. Bear in mind this system was working perfectly until the switch from Win7 to Win10.
I've stripped most of the boilerplate comments out of smb.conf and attached the current version.

 

[buraid]
path = /buraid
read only = no
browseable = yes
guest ok = yes
create mask = 0664
valid users = youruser

and to try simple case:

[sharedir]
path =/home/youruser/sharedir
read only = No
valid users = youruser


of course you have to restart smb or the sytem after saving the file.

 

nope :

hosts allow = hippolyta gilgamesh boudicca

 

OK, both your last 2 posts implemented, and smb.conf attached...no change in behavior.

 

Now you need to be more specific on what you do and what error messages, it should work at least with

\\192.....

what is you windows version? (winver) i'm using 1709 and i can connect to linux hosts but i've disabled smb1
is your windows network private?
Does it work linux to linux?
i'm using Ubuntu 16.04 and i can share folders with right click properties, can you do that in fedora? If not maybe you should switch to a more user oriented distro like ubuntu or mint