On 9/27/19 1:32 PM, Rowland penny via samba wrote: ....snippity...> I repeat, smbclient never had anything to do with network browsing, so > it is unlikely to have anything to do with Network Discovery. Perhaps > you are thinking of libsmbclient ? this can be used by other packages 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.
On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote:> On 9/27/19 1:32 PM, Rowland penny via samba wrote: > ....snippity... > > I repeat, smbclient never had anything to do with network browsing, so > > it is unlikely to have anything to do with Network Discovery. Perhaps > > you are thinking of libsmbclient ? this can be used by other packages 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.Can you log a bug on bugzilla.samba.org, attach your smb.conf and a smbclient debug level 10 and a wireshark log trace. I wish you'd reported this on Monday, we just spent a week in the lab with Apple engineers and we'd have investigated and almost certainly fixed it if we'd known about it (mostly we were checking MacOS client access to Samba, not the other way around :-). Thanks, Jeremy.
On 9/27/19 1:39 PM, Jeremy Allison via samba wrote:> On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you are thinking of libsmbclient ? this can be used by other packages 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. > > Can you log a bug on bugzilla.samba.org, attach your smb.conf > and a smbclient debug level 10 and a wireshark log trace. > > I wish you'd reported this on Monday, we just spent a week > in the lab with Apple engineers and we'd have investigated > and almost certainly fixed it if we'd known about it (mostly > we were checking MacOS client access to Samba, not the other > way around :-).Most Mac Admins laugh at us for doing it too. We are all alone.
On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote:> On 9/27/19 1:32 PM, Rowland penny via samba wrote: > ....snippity... > > I repeat, smbclient never had anything to do with network browsing, so > > it is unlikely to have anything to do with Network Discovery. Perhaps > > you are thinking of libsmbclient ? this can be used by other packages 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_MISMATCHThis 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->protocol > PROTOCOL_NT1) { DBG_ERR("called for dialect[%s] server[%s]\n", smb_protocol_types_string(state->conn->protocol), smbXcli_conn_remote_name(state->conn)); return NT_STATUS_REVISION_MISMATCH; } Have you explicitly requested SMB2 in your smb.conf or on your smbclient command line ?
On 9/27/19 5:38 PM, Jeremy Allison wrote:> On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you are thinking of libsmbclient ? this can be used by other packages 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 > > 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->protocol > PROTOCOL_NT1) { > DBG_ERR("called for dialect[%s] server[%s]\n", > smb_protocol_types_string(state->conn->protocol), > smbXcli_conn_remote_name(state->conn)); > return NT_STATUS_REVISION_MISMATCH; > } > > Have you explicitly requested SMB2 in your smb.conf or on > your smbclient command line ? >Specifying -m SMB2 I get: smb1cli_req_writev_submit: called for dialect[SMB2_10] server[mac_svr2] Error returning browse list: NT_STATUS_REVISION_MISMATCH
On 9/27/19 1:39 PM, Jeremy Allison wrote:> On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you are thinking of libsmbclient ? this can be used by other packages 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. > > Can you log a bug on bugzilla.samba.org, attach your smb.conf > and a smbclient debug level 10 and a wireshark log trace. > > I wish you'd reported this on Monday, we just spent a week > in the lab with Apple engineers and we'd have investigated > and almost certainly fixed it if we'd known about it (mostly > we were checking MacOS client access to Samba, not the other > way around :-). >Took a while to get a bugzilla account. Submitted https://bugzilla.samba.org/show_bug.cgi?id=14151