For Fedora 25, I am not familiar with fedora version numbers but I am with RHEL/Centos 7.x If you have selinux enabled by default, you might try as root
setenforce 0 to temporarily put selinux into permissive mode until next reboot, see if this allows samba access to work. If so then it's a selinux problem, and in RHEL/Centos there is
etc/samba/smb.conf.example which explains the samba related selinux commands needed to allow samba shares to work with selinux set to enforcing.
For your version of fedora, I would work off the
for reference here is my working
smb.conf from an older version of samba showing what i believe is the minimum required to get it to work. If you go too restrictive with settings then you can prevent a successful connection so sometimes it's best to not specify which generally means allow for all.
[myshare] take out
allow hosts and
valid users. Once samba working then consider adding restrictive measures like these as necessary.
# min protocol = SMB1 needed for winxp
min protocol = SMB1
# max protocol SMB2 needed to work with win10, unspecified for this older version of samba is smb1.
max protocol = SMB2
security = user
passdb backend = tdbsam
# map to guest = never prevents popup option, bad user allows popup in windows
map to guest = Bad User
path = /data
read only = No
# guest ok = no
# create mask = 660
# directory mask = 770
with guest ok = no, and map to guest bad user, will allow popup in windows giving anyone a chance to enter correct linux username and pw. map to guest never prevents popup, meaning the username of the windows user has to be the same as a valid local user in linux, per security=user. You likely do not need
min/max protocol specified, I do in samba version 3.6. I don't know what verion of samba u have in fedora 25, if it's samba 3.x then try specifying the min/max protocol.
don't forget to do
smbpasswd -a <username on your linux system.