New
#11
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
OK, I've made some headway here. All my Windows machines run Kaspersky, and the first remedy I tried was turning off the Kaspersky firewall. That produced nothing, so I eliminated Kaspersky from consideration. But I just found a user online who had a similar problem, and he found that while turning off Kaspersky didn't help, uninstalling it did.
So I borrowed a Win10 machine that doesn't have Kaspersky aboard, and it went straight to the Samba shares, no problem. Obviously I have to pursue this with Kaspersky now, so I'll be away from here for a bit.
OK, that lead didn't pan out: the problem has mysteriously disappeared on two of the Win10/KIS hosts, but not on the third, and disabling ALL features in KIS didn't cure it on the third. Here is the situation now:
Host BOUDICCA, 192.168.1.125, can open Samba host ABELARD, 192.168.1.13, via File Explorer.
Host GILGAMESH, 192.168.1.111, cannot open the Samba host.
I'm attaching two Samba logs:
log.192.168.1.111, containing a failed attempt to connect to Samba from that host at 10:00 AM MST
log.boudicca, containing a successful connection to Samba from that host at 10:13 AM MST
The problemmay be with the user::password for 1.111, you got the same user password in 1.111 and boudicca?
if not you need to add another samba user in linux for the 1.111 machine, eg user1 and add it to valid users in conf
Yes, the usernames and passwords are consistent across the whole network.
I understand that the server (linux) works, i have no experience in debugging windows behaviour, sorry
Windows 10 pro likes to change Master Browser to itself so if you have a Master Browser Well with Windows 10 pro you now have 1 more,
So look into that i am having similar problems with my Windows 10 pro after the latest build, i am no longer able to access my hd connected via usb on the router.
In fact it does not see anything not even it self, it will see my Routers dlna server but not play anything it downloads anything i click
My Routers Samba and ftp it no longer sees. not sure what the problems is yet could be a user problem normally not an issue as long as i enter the credentials when i map a drive, but it do not see anything not even my WORKGROUP it just says NETWORK hehe.
But back to the OP the problem with the Master Browser should only be a problem with Windows 10 Pro / Home should not be an issue but check it and see how many Master Browser you have, anything more then 1 is BAD good luck ill get back to my own problem