search for: smb1cli_req_writev_submit

...s to > provide network browsing. > > You could always code up what you require and propose it as a patch for > Samba. I think this isn't (exactly) a Samba problem. The problem is we can't enmerated shares exposed from MacOS. But our Windows and MacOS clients can. We get: smb1cli_req_writev_submit: called for dialect[SMB3_00] server[mac_svr2] Error returning browse list: NT_STATUS_REVISION_MISMATCH I think this is some sort of Mac problem(?) Thanks for everyone's time. Unless you have some hints with regards to the above.

...always code up what you require and propose it as a patch for >>> Samba. >> >> I think this isn't (exactly) a Samba problem. The problem is we can't >> enmerated shares exposed from MacOS. But our Windows and MacOS clients can. >> >> We get: >> smb1cli_req_writev_submit: called for dialect[SMB3_00] server[mac_svr2] >> Error returning browse list: NT_STATUS_REVISION_MISMATCH > > This error is generated by the smbcient libraries trying > to send an SMB1 writev request to a server that only supports > SMB2 or above. From our code: > > libcli...

...tup GUI, it is not able to find any shared printer. If I run smbclient I get this error: smbclient -L dap001 -N Unable to initialize messaging context Anonymous login successful ?????????????? Sharename???????????? Type?????????? Comment ?????????????? ---------???????????? ----?????????? ------- smb1cli_req_writev_submit: called for dialect[SMB2_10] server[dap001] Error returning browse list: NT_STATUS_REVISION_MISMATCH Reconnecting with SMB1 for workgroup listing. Anonymous login successful ?????????????? Server???????????????????????????? Comment ?????????????? ---------?????????????????????? ------- ??????????...

...nter does not do anything, just idling. In Windows logs I can see successful logon audit followed by an immediate logout. I tried to give some commands, but no visible result was produced: $ smbclient "\\\\192.168.0.100\\hp1516" "password" -c "queue" -U user -m SMB2 smb1cli_req_writev_submit: called for dialect[SMB2_10] server[192.168.0.100] $ smbclient "\\\\192.168.0.100\\hp1516" "password" -c "posix_open /home/kotee/file.txt" -U user -m SMB2 smb1cli_req_writev_submit: called for dialect[SMB2_10] server[192.168.0.100] smb1cli_req_writev_submit: called fo...

Hello, I'm trying to use the "notify" API of libsmbclient, testing against a Samba AD DC. The function is returning with errno=22 (mapped from NT_STATUS_REVISION_MISMATCH), and I'm getting the following error message: smb1cli_req_writev_submit: called for dialect[SMB3_11] server[dc1.example.com] It looks like libsmbclient is, for some reason, using SMB1 but needs to be using SMB3_11. Note that the following command (which, like my code, forces the use of Kerberos) works just fine: $ smbclient -kN //dc1.example.com/sysvol -c 'notif...

...used), I can not browse shares of a Windows 10 machine (sorry, Thunderbird splits some lines): smbclient -L 192.168.122.200 Unable to initialize messaging context Enter WORKGROUP\yvan's password: Anonymous login successful Sharename Type Comment --------- ---- ------- smb1cli_req_writev_submit: called for dialect[SMB3_11] server[192.168.122.200] Error returning browse list: NT_STATUS_REVISION_MISMATCH Reconnecting with SMB1 for workgroup listing. do_connect: Connection to 192.168.122.200 failed (Error NT_STATUS_RESOURCE_NAME_NOT_FOUND) Failed to connect with SMB1 -- no workgroup availabl...

...gt; > > You could always code up what you require and propose it as a patch for > > Samba. > > I think this isn't (exactly) a Samba problem. The problem is we can't > enmerated shares exposed from MacOS. But our Windows and MacOS clients can. > > We get: > smb1cli_req_writev_submit: called for dialect[SMB3_00] server[mac_svr2] > Error returning browse list: NT_STATUS_REVISION_MISMATCH This error is generated by the smbcient libraries trying to send an SMB1 writev request to a server that only supports SMB2 or above. From our code: libcli/smb/smbXcli_base.c:smb1cli_req_wr...

...always code up what you require and propose it as a patch for >>> Samba. >> >> I think this isn't (exactly) a Samba problem. The problem is we can't >> enmerated shares exposed from MacOS. But our Windows and MacOS clients can. >> >> We get: >> smb1cli_req_writev_submit: called for dialect[SMB3_00] server[mac_svr2] >> Error returning browse list: NT_STATUS_REVISION_MISMATCH >> >> I think this is some sort of Mac problem(?) Thanks for everyone's time. >> Unless you have some hints with regards to the above. > > Can you log a bug...

...): >> >> smbclient -L 192.168.122.200 >> Unable to initialize messaging context >> Enter WORKGROUP\yvan's password: >> Anonymous login successful >> >> Sharename Type Comment >> --------- ---- ------- >> smb1cli_req_writev_submit: called for dialect[SMB3_11] >> server[192.168.122.200] >> Error returning browse list: NT_STATUS_REVISION_MISMATCH >> Reconnecting with SMB1 for workgroup listing. >> do_connect: Connection to 192.168.122.200 failed (Error >> NT_STATUS_RESOURCE_NAME_NOT_FOUND) >&gt...

...other samba servers. It seems to be something unique to this one. I tried querying group lists with "net" which pointed to the max server protocol being a possible factor. root at weirdserver:~# net groupmember list IT -U Administrator Enter Administrator's password: smb1cli_req_writev_submit: called for dialect[SMB3_11] server[127.0.0.1] root at weirdserver:~# testparm -v . server max protocol = SMB3 . root at okserver:~# net groupmember list IT -U Administrator Enter Administrator's password: smb1cli_req_writev_submit: called for dial...

...other samba servers. It seems to be something unique to this one. I tried querying group lists with "net" which pointed to the max server protocol being a possible factor. root at weirdserver:~# net groupmember list IT -U Administrator Enter Administrator's password: smb1cli_req_writev_submit: called for dialect[SMB3_11] server[127.0.0.1] root at weirdserver:~# testparm -v : server max protocol = SMB3 : root at okserver:~# net groupmember list IT -U Administrator Enter Administrator's password: smb1cli_req_writev_submit: called for dial...

...always code up what you require and propose it as a patch for >>> Samba. >> >> I think this isn't (exactly) a Samba problem. The problem is we can't >> enmerated shares exposed from MacOS. But our Windows and MacOS clients can. >> >> We get: >> smb1cli_req_writev_submit: called for dialect[SMB3_00] server[mac_svr2] >> Error returning browse list: NT_STATUS_REVISION_MISMATCH >> >> I think this is some sort of Mac problem(?) Thanks for everyone's time. >> Unless you have some hints with regards to the above. > > Can you log a bug...

..., Thunderbird splits > some lines): > > smbclient -L 192.168.122.200 > Unable to initialize messaging context > Enter WORKGROUP\yvan's password: > Anonymous login successful > > Sharename Type Comment > --------- ---- ------- > smb1cli_req_writev_submit: called for dialect[SMB3_11] > server[192.168.122.200] > Error returning browse list: NT_STATUS_REVISION_MISMATCH > Reconnecting with SMB1 for workgroup listing. > do_connect: Connection to 192.168.122.200 failed (Error > NT_STATUS_RESOURCE_NAME_NOT_FOUND) > Failed to connect with...

...via samba wrote: > Hello, > > I'm trying to use the "notify" API of libsmbclient, testing against a > Samba AD DC. The function is returning with errno=22 (mapped from > NT_STATUS_REVISION_MISMATCH), and I'm getting the following error > message: > > smb1cli_req_writev_submit: called for dialect[SMB3_11] > server[dc1.example.com] > > It looks like libsmbclient is, for some reason, using SMB1 but needs > to be using SMB3_11. > > Note that the following command (which, like my code, forces the use > of Kerberos) works just fine: > > $ smbclie...

...gt; > > You could always code up what you require and propose it as a patch for > > Samba. > > I think this isn't (exactly) a Samba problem. The problem is we can't > enmerated shares exposed from MacOS. But our Windows and MacOS clients can. > > We get: > smb1cli_req_writev_submit: called for dialect[SMB3_00] server[mac_svr2] > Error returning browse list: NT_STATUS_REVISION_MISMATCH > > I think this is some sort of Mac problem(?) Thanks for everyone's time. > Unless you have some hints with regards to the above. Can you log a bug on bugzilla.samba.org, at...

...gt;>>> for >>>> Samba. >>> >>> I think this isn't (exactly) a Samba problem.? The problem is we can't >>> enmerated shares exposed from MacOS.? But our Windows and MacOS >>> clients can. >>> >>> We get: >>> smb1cli_req_writev_submit: called for dialect[SMB3_00] server[mac_svr2] >>> Error returning browse list: NT_STATUS_REVISION_MISMATCH >>> >>> I think this is some sort of Mac problem(?)? Thanks for everyone's >>> time. >>> Unless you have some hints with regards to the above....

...e if this is a CentOS issue >> smbclient -L dap001 -N >> Unable to initialize messaging context >> Anonymous login successful >> >> ?????????????? Sharename???????????? Type?????????? Comment >> ?????????????? ---------???????????? ----?????????? ------- >> smb1cli_req_writev_submit: called for dialect[SMB2_10] server[dap001] >> Error returning browse list: NT_STATUS_REVISION_MISMATCH > For this specific error, see > https://bugzilla.samba.org/show_bug.cgi?id=14151 > https://bugzilla.samba.org/show_bug.cgi?id=14152 > > It appears to be an issue with smbcli...

On 9/27/19 1:11 PM, Rowland penny via samba wrote: > On 27/09/2019 18:57, Christopher Cox via samba wrote: >> On 9/27/19 12:48 PM, Rowland penny via samba wrote: >>> On 27/09/2019 18:33, Christopher Cox via samba wrote: >>>> >>>> I understand the "Function Discovery" side and wsdd (which is fine >>>> for local same network discovery