search for: mac_svr2

...ys 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.

...>>> 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_writev_submit...

...>>> 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, attach your smb.conf &...

...>>> 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, attach your smb.conf &...

...ropose 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, attach your smb.conf and a smbclient debug leve...

...ropose 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_writev_submit() if (state->conn-&gt...

...gt;> 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 bugzi...

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