In my case commenting out my line "smb ports 139" helped. I think I have a solution that works on Windows 7 - 10 and on Server 2012 I've added my smb.conf file in a comment (can't have more than 2 links with <10 reputation) The successful attempt selects protocol SMB2_10 from the start, but this protocol is not even requested by Windows 10. Then, after some security negotiations, it switches to protocol SMB 2.?, then SMB3_00, followed by: Server exit (NT_STATUS_END_OF_FILE). Then it requests a number of different protocols before selecting SMB2_FF.
I have attached the logs for a failed connection attempt from Windows 10, and those for a successful attempt from Windows 7 (for comparison).īriefly, unlike the successful attempt, the failed one starts with: switch message SMBnegprot (pid 2855) conn 0x0 The error message given by Windows is that the server is online but not responding.
The server and the clients are not on the same LAN. I cannot connect from Windows 10 (but I can from Windows 7). I have a Samba server version 4.1.11 running on Ubuntu 14.04.
0 kommentar(er)
