Bug 9073 - connection to Mac OS X 10.6.8 Snow Leopard: SPNEGO login failed
Summary: connection to Mac OS X 10.6.8 Snow Leopard: SPNEGO login failed
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: Client Tools (show other bugs)
Version: 3.6.6
Hardware: x64 Linux
: P5 normal
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-31 19:01 UTC by Benjamin Kay
Modified: 2020-01-03 17:44 UTC (History)
1 user (show)

See Also:

Attachments
command line output & wireshark packet trace (5.04 KB, application/x-gzip)
2012-07-31 19:01 UTC, Benjamin Kay 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Kay 2012-07-31 19:01:20 UTC 
Created attachment 7730 [details]
command line output & wireshark packet trace

I am trying to connect to an SMB share on a server running Mac OS X 10.6.8 (Snow Leopard), which has the illustrious SAMBA 3.0.28a, from a client running Debian Linux (x86_64) using smbclient 3.6.6. Authentication fails with the following output (see the attached file for complete output and a packet trace):

NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60088215
  NTLMSSP_NEGOTIATE_UNICODE
  NTLMSSP_REQUEST_TARGET
  NTLMSSP_NEGOTIATE_SIGN
  NTLMSSP_NEGOTIATE_NTLM
  NTLMSSP_NEGOTIATE_ALWAYS_SIGN
  NTLMSSP_NEGOTIATE_NTLM2
  NTLMSSP_NEGOTIATE_128
  NTLMSSP_NEGOTIATE_KEY_EXCH
SPNEGO login failed: Logon failure
session setup failed: NT_STATUS_LOGON_FAILURE

This has some signs of being a regression since it is possible to connect from a machine running Ubuntu 10.04 using smbclient 3.4.7. It is also possible to connect from Windows workstations provided ACLs are disabled server-side.

Would someone smarter than me please have a look at the packet trace and decide whether or not this is a bug in smbclient?
Comment 1 Björn Jacke 2020-01-03 17:44:32 UTC 
OS X connections haven't been a generic issue in the last yeasrs. This was either a misconfiguration or a bug that was fixed since then.