Adding our team to comment/help. -----Original Message----- From: Tom Talpey [mailto:ttalpey@xxxxxxxxxxxxx] Sent: Monday, January 20, 2014 7:17 PM To: Jeff Layton; Ben Greear Cc: linux-cifs@xxxxxxxxxxxxxxx; Amit Haval (India Bangalore); Shirish Pargaonkar Subject: RE: Problem with connecting to SMB server in 3.9.11 kernel. > -----Original Message----- > From: linux-cifs-owner@xxxxxxxxxxxxxxx [mailto:linux-cifs- > owner@xxxxxxxxxxxxxxx] On Behalf Of Jeff Layton > Sent: Monday, January 20, 2014 7:57 AM > To: Ben Greear > Cc: linux-cifs@xxxxxxxxxxxxxxx; Amit Haval (India Bangalore); Shirish > Pargaonkar > Subject: Re: Problem with connecting to SMB server in 3.9.11 kernel. > > On Sat, 18 Jan 2014 09:17:32 -0800 > Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > > > Hello! > > > > A customer reported problems connecting our CIFS traffic generation > > test > gear to their SMB server. > > We are using the 3.9.11+ kernel, and though it is patched, we do not > > have any patches to cifs. > > > > The OS is Fedora 14, 64-bit. > > > > A similar system on Fedora 14, with a 3.7.10+ kernel was working, > > but when we tried the 3.7.10+ kernel on the broken machine, it also > > failed to > work. > > So, it could be the SMB server itself is having issues. (In the > > 3.7.10+ failure, the server just failed to respond after "Setup andX > > Request AUTH message", though we did get the TCP ack so it looks > > like the message was received by the server.) > > > > I'm attaching a capture taken on the SMB server. > > > > From looking at this page: > > > > http://msdn.microsoft.com/en-us/library/ff469913.aspx > > > > It appears the problem (STATUS_UNSUCCESSFUL) is: > > > > "The size of the extended attribute list is not correct. Check the > > EaErrorOffset field for the address of the SMB_GEA structure at > > which the > error was detected." > > > > I did not see anything about extended attribute list in the capture, > > but if someone else with more knowledge could take a look and see if > > they > notice any problems I would be grateful. > > > > Thanks! > > Ben > > > > There's no EA list on this call so that description isn't valid here. > > AIUI, NT_STATUS_UNSUCCESSFUL is basically a generic "something went > wrong" error (sort of like EIO on POSIX). It looks like the server > doesn't like something about the request being sent, but it's tough to know what it is. The trace Ben attached shows an authentication failure, and I don't see any TRANS2_QUERY_FILE_INFORMATION in the trace at all as Ben references. The client is still sending its SESSION_SETUP attempt. Looks like the client is attempting NTLMSSP/NTLMv2 for NICVALIDATION\administrator, and this status is resulting from the authentication and not the SMB protocol. Microsoft Message Analyzer shows no problem with the packet structure itself, in any case. So this doesn't appear to be a malformed request. What type of server is this? The NativeOS string is "SpinStream2", which I don't recognize. ______________________________________________________________________ This email has been scanned by the Boundary Defense for Email Security System. For more information please visit http://www.apptix.com/email-security/antispam-virus ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Boundary Defense for Email Security System. For more information please visit http://www.apptix.com/email-security/antispam-virus ______________________________________________________________________ -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
