server side: centos 7/64 updated
smb server version 4.7.1
client side: win7/64 - no problems at all to call shares (either via IP or hostname)
win10: no access at all (either via IP or hostname)
Two days of read find and try but this hell of win10 does not connect. A customer moved all machines to w10... byebye shared data
Any suggestions to tryout more ?
Smb share not working with Win10 clients
Smb share not working with Win10 clients
Last edited by rnervi on 2018/10/23 10:43:44, edited 1 time in total.
Re: Smb share not wirking with Win10
Is this due to SMB1?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Smb share not working with Win10
Sound so but till now no solutions found.
IF smb1 is removed from win10 machines, the share machine/machine is lost.....
As the Win10 clients shares some folder between them too (..no comment..) if SMB 1.0 is disabled all these shares stops to work, and cannot permit in this situation.
Tryied to instruct SMB for SMB3 for client acces...nothing [just found tons of claims about that and NO a definitive solutions: someone starte to share on "who-know-why" basis].
the nice part: if the share is "on user basis", win7 correctly asks for user/password - this means that server side smb is configured as needed.
Win10 absolutely no. weird.
IF smb1 is removed from win10 machines, the share machine/machine is lost.....
Code: Select all
[global]
netbios name = WORKGROUP
load printers = no
cups options = raw
printing = cups
workgroup = WORKGROUP
os level = 20
map to guest = Bad Password
printcap name = cups
security = user
preferred master = yes
passdb backend = tdbsam
client max protocol = SMB3
Tryied to instruct SMB for SMB3 for client acces...nothing [just found tons of claims about that and NO a definitive solutions: someone starte to share on "who-know-why" basis].
the nice part: if the share is "on user basis", win7 correctly asks for user/password - this means that server side smb is configured as needed.
Win10 absolutely no. weird.
Last edited by rnervi on 2018/10/24 14:17:53, edited 2 times in total.
Re: Smb share not working with Win10 clients
oh no clues damn
but nobody uses win10 as client for smb ??
but nobody uses win10 as client for smb ??
Re: Smb share not working with Win10 clients
damn solved finally.culprit was iptables !
need to open port 445
-A INPUT -p tcp -m state -m tcp --dport 445 --state NEW -j ACCEPT
(eventually with -s to limit ips to local lan)
anyway smb.conf used is:
need to open port 445
-A INPUT -p tcp -m state -m tcp --dport 445 --state NEW -j ACCEPT
(eventually with -s to limit ips to local lan)
anyway smb.conf used is:
Code: Select all
[global]
netbios name = WORKGROUP
load printers = no
cups options = raw
printing = cups
workgroup = WORKGROUP
os level = 20
# map to guest = Bad Password
printcap name = cups
security = user
preferred master = yes
passdb backend = tdbsam
server min protocol = SMB3
client min protocol = SMB3
client max protocol = SMB3