Thanks Andrew. I found the code path for smbclient4 is up to date at most of 2007. So it may be outdated. I also found the code path for smbclient is outdated too. smbclient is older than smbclient4 and it can only supports smb1. I type "smbclient -m SMB2 //server/share" and get message "SMB2 protocol unrecognized".
I have the following two questions: 1: how to build smbtorture in the master branch. Does smbtorture support SMB2? Did anybody use smbtorture to test against smbd daily? Where can I find the document for smbtorture---smbd tests. 2: Did anybody use smbtorture to test against windows servers (for example windows 7 or windows server 2008 R2). Could you please tell me how to do that and where I can find the document? 3: I read a little of smbtorture source code (I will read more). I know where to add a new test case into the framework. To add a runnable test case, what part of the source codes should I read. Should I read the entire source code? Thanks and wait for your reply Jun On Tue, Sep 25, 2012 at 2:08 PM, Andrew Bartlett <[email protected]> wrote: > On Tue, 2012-09-25 at 10:43 -0700, Jun Yi wrote: > > Thanks Andrew, > > > > Let's first clarify the version I used. I use the master branch, e.g., > > version 4.1.0, for both client and server sides. > > > > I run smbclient4 at the client side: > > junyij@junyij] ./smbclient4 > > -V > > Version 4.1.0pre1-DEVELOPERBUILD > > junyij@junyij] ./smbclient4 -m SMB2 -W smb-workgroup -U > > junyij //localhost/share1 > > Connection to \\localhost\share1 failed - NT_STATUS_REVISION_MISMATCH > > > > I run sbmd at the server side with configuration > > file /etc/samba/smb.conf > > junyij@junyij] sudo ./smbd > > -V > > Version 4.1.0pre1-DEVELOPERBUILD > > sudo ./smbd -s /etc/samba/smb.conf -d 10 -l smbd-4 > > junyij@junyij] > > cat /etc/samba/smb.conf > > [global] > > workgroup = smb-workgroup > > max protocol = SMB2 > > min protocol = SMB2 > > [share1] > > path = /tmp > > I examined the source code used by smbclient4, and as far as I can tell > this tool simply cannot do smb2. Therefore, as you have seen, this will > fail. > > You could try 'smbclient' (which uses a different codebase), which > appears to have some support, but I'm not sure exactly how much is > connected there. > > Andrew Bartlett > > -- > Andrew Bartlett http://samba.org/~abartlet/ > Authentication Developer, Samba Team http://samba.org > > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
