Bug 7931 - Samba does not respond to SMB2 NEGOTIATE packets
Summary: Samba does not respond to SMB2 NEGOTIATE packets
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: SMB2 (show other bugs)
Version: unspecified
Hardware: x64 Linux
: P3 major
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
Depends on:
Reported: 2011-01-21 16:50 UTC by Mike Smith
Modified: 2011-01-26 18:36 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Mike Smith 2011-01-21 16:50:00 UTC
When I send a SMB2 NEGOTIATE request packet the samba server does not send a response.

Tested with Version 3.6.0pre1-GIT-1007dd3-test
Comment 1 Jeremy Allison 2011-01-21 17:27:39 UTC
What are you using to generate the packet ? Can you attach a packet trace and debug level 10 please ?

Comment 2 Jeremy Allison 2011-01-21 18:13:16 UTC
Ok, I just tested with a Windows7 client, and the current git v3-6-test code certainly does respond directly to a SMB2 Negprot request as the first packet on a new TCP connection.

The only way this might not happen is if you have "security = share" set in your smb.conf. Is this the case ?

Comment 3 Jeremy Allison 2011-01-26 11:56:52 UTC
Ping - can you let me know if you're using "security = share" please ?

Comment 4 Mike Smith 2011-01-26 16:41:51 UTC
Sorry for the delay responsing, I've been busy moving. I am using the "security = share". Not sure why this should happen with that setting, can you explain? 


PS - Do you still want me to post a packet trace and debug log? If so it might be a few more days but I will (eventually) get to it. :) 
Comment 5 Jeremy Allison 2011-01-26 16:48:55 UTC
Ok, that makes sense. I've pushed a fix for this to master and v3-6-test. Perviously if "security = share" we disabled SMB2 support internally, and would quit if we receive an SMB2 packet (just like we would if we received any non-SMB packet).

Now we will map "security = share" to the two parameters "security = user" and "map to guest = bad user" internally.

Please test out the fixed code and close out this bug if it works for you.

Comment 6 Mike Smith 2011-01-26 18:36:58 UTC
It's working now, thanks!