I have winbind and NSS working happily on the Mint server, successfully resolving all names on my network. All relevant hosts are currently assigned fixed IP addresses, and listed in both
hosts
and lmhosts
files on the Windows machine. As we shall see, name resolution is not a problem. With various different Samba configurations, the Mint server and Windows laptop are happily talking to each other. The problem i am having seems to be with authentication.In Mint 19, I installed Samba (4.7.6) and started with essentially the same
smb.conf
as I have been using in Mint 18 (Samba 4.3.11). This is currently still working with Mint 18 and the Windows 10 laptop without any issues. It is basically a default configuration, with the following initial share:Code: Select all
[msummerfield]
path = /home/msummerfield
writeable = yes
browseable = yes
guest ok = no
valid users = msummerfield
create mask = 0644
directory mask = 0755
log level = 3 passdb:10 auth:10 winbind:10
) in order to observe what is going on. Attempting to access the share, unsurprisingly, results in:Code: Select all
[2019/01/01 14:48:50.193714, 2] ../source3/smbd/service.c:338(create_connection_session_info)
guest user (from session setup) not permitted to access this share (msummerfield)
[2019/01/01 14:48:50.193745, 1] ../source3/smbd/service.c:521(make_connection_snum)
create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/01 14:48:50.193799, 3] ../source3/smbd/smb2_server.c:3139(smbd_smb2_request_error_ex)
smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_ACCESS_DENIED] || at ../source3/smbd/smb2_tcon.c:135
sudo smbpasswd -a msummerfield
).Now it is impossible to browse the server and/or to see or mount the share. On Windows, I get a dialog saying 'Access is denied', and requesting me to enter a password. This just keeps repeating, i.e. I never receive a final red-cross 'not accessible' dialog, unless I enter an incorrect password (i.e. it looks as though the Samba server is recognising a correct password, but then denying access to the authenticated user). Log says:
Code: Select all
[2019/01/01 14:53:41.049984, 1] ../source3/smbd/smb2_tcon.c:227(smbd_smb2_tree_connect)
smbd_smb2_tree_connect: reject request to share [IPC$] as 'SERVER\msummerfield' without encryption or signing. Disconnecting.
[2019/01/01 14:53:41.050034, 3] ../source3/smbd/smb2_server.c:3139(smbd_smb2_request_error_ex)
smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_ACCESS_DENIED] || at ../source3/smbd/smb2_tcon.c:135
smb.conf
:Code: Select all
server signing = mandatory
smb encrypt = mandatory
Code: Select all
[2019/01/01 14:55:44.667593, 3] ../source3/smbd/smb2_server.c:3139(smbd_smb2_request_error_ex)
smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_ACCESS_DENIED] || at ../source3/smbd/smb2_server.c:2366
I have tried all sorts of other things, fairly randomly really, but the above are the only ones that make any logical sense, and have any impact on what happens and what appears in the log files.
In summary: the Win10 client and Mint server are communicating. The client can access shares and individual files in some configurations (e.g. the 'guest only' setup). But as soon as I try to access the server using an actual SMB user account, access is denied.
This has me tearing my hair out. As I say, it all worked - and still works - perfectly in Mint 18. Any assistance would be greatly appreciated.