Bug 10890 - smbclient can not connect to Mac OS X 10.10
Summary: smbclient can not connect to Mac OS X 10.10
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.2.0rc2
Hardware: All Mac OS X
: P1 critical (vote)
Target Milestone: 4.2
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2014-10-21 14:52 UTC by Steve French
Modified: 2015-02-16 12:05 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Steve French 2014-10-21 14:52:44 UTC
In my testing, smbclient (and cifs.ko as well) can not connect to the Apple SMB2/SMB3 file server in the most recent Mac update (OS X 10.10). Windows 8.1 and Mac clients can connect to their server.  The file server advertises SMB2.02/SMB2.1/SMB3 in negotiate protocol (presumably no cifs anymore) and the failure cases are both NTLMSSP (in cifs.ko it is RawNTLMSSP and in smbclient it is NTLMSSP in SPNEGO).   The failure is an NT Status logon failure on the 2nd phase of session setup (NTLMSSP_AUTH response).  Windows and Mac succeed with NTLMSSP in SPNEGO with the same userid/password.

Although it used to work to Mac OS 10.9, now with connections to the popular update failing we will need to find a workaround if possible.
Comment 1 Steve French 2014-10-22 05:37:33 UTC
Scenario stopped failing after various reboots.  Will reopen if recreatable.
Comment 2 Ralph Böhme 2015-02-16 12:05:14 UTC
For the archives:

Just ran into this the second time. Last time it went away like it did for you, but this time it wouldn't. After banging my head seriously against this and confirming that I couldn't connect to three different OS X installation (one 10.9, two 10.10), I somehow remembered that the host where I started smbclient was in a VM where the time often goes out of sync. After syncing time with NTP I could finally connect.