- #Windows 10 connect to samba share how to#
- #Windows 10 connect to samba share windows 10#
- #Windows 10 connect to samba share windows#
I see server is trying to authenticate with user logged in Windows 10, but since not existing it falls back to guest user but connection is reset just after. source3/smbd/server_exit.c:244(exit_server_common) auth/auth_log.c:760(log_authentication_event_human_readable)Īuth: user \ at with status workstation remote host mapped to \. source3/auth/auth.c:332(auth_check_ntlm_password)Ĭheck_ntlm_password: Authentication for user -> FAILED with error NT_STATUS_NO_SUCH_USER, authoritative=1 source3/auth/check_samsec.c:399(check_sam_security)Ĭheck_sam_security: Couldn't find user 'USER' in passdb.
#Windows 10 connect to samba share windows 10#
And from the computer on which I cannot access them I successfully ping MyLeap15Computer.Īnyway, technically I can access my shared folders by forcing NT1 protocol, but since it should be possible I want to be able to access them from SMB2 or SMB3 since there are security issues in SMB1/CIFS (and then deactivate it in Windows 10 too), also, since I can access them from another Windows 10 without forcing this protocol it then should be something in Windows configuration but I cannot manage to see which since everything appears active on both.Īnd finally, even if issue seems to be more on client side, here is the server condifuration, /etc/samba/smb.conf without forcing to NT1 protocol (this configuration accepts guest users, then no credentials have to be given for connection): Įdit: here are more information after what suggested what was suggested did not work but I found something interesting in server logs (added log level = 3 to /etc/samba/smb.conf global section then looked on /var/log/samba/log.smbd after having tried connection): check_ntlm_password: Checking password for unmapped user with the new password interface
#Windows 10 connect to samba share how to#
I also confirmed that SMB2 and 3 are actually active with How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows, and also been able to access them from another Windows 10. Or connect to tmp shared folder with: smbclient //MyLeap15Computer /tmp -N $ testparm -parameter-name="max protocol"Īnd I can access these shared folders from another Linux computer without forcing protocol with following command for example I can list folders: smbclient -L MyLeap15Computer -N I can successfully browse from an old openSUSE 12.1 that uses only SMB1/CIFS but not from a more recent openSUSE Leap 15, except if I force NT1 protocol (that is for SMB1/CIFS) on its side, in /etc/samba/smb.conf global section: įor information, by default min protocol is LANMAN1 and max protocol is SMB3, that range then includes NT1 protocol (see SMB protocol min max values available?): $ testparm -parameter-name="min protocol" To try to identify and resolve network problems click Diagnose. Otherwise, there might be a problem with your network.
I have an issue under Windows 10 to access some Linux Samba shares with following error: Check the spelling of the name.
0 kommentar(er)
