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
On 03/10/2019 20:30, Christopher Cox via samba wrote:> 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 >I am not the expert here, but: A) you are using Samba as a standalone server 'security = user' B) you also seem to want to use another server for passwords 'password server = ldap.skopos.me' C) Samba tries to use kerberos : ???? Enter SKOPOS\ccox's password: cli_session_creds_prepare_krb5: Doing kinit for ccox at SKOPOS to access doc_svr2 ???? kerberos_kinit_password: as ccox at SKOPOS using [MEMORY:cliconnect] as ccache and config [(null)] ???? And fails: ???? Kinit for ccox at SKOPOS to access doc_svr2 failed: Cannot find KDC for requested realm ???? But then seems to authenticate via kerberos: ???? Kinit for ccox at SKOPOS to access doc_svr2 failed: Cannot find KDC for requested realm Do you want to use kerberos ? If so, change 'security = user' to 'security = ads' and it might work. Can you also tell us just how you are trying to connect to the Samba server, are you using smbclient, a GUI or what ? Rowland
On Thu, Oct 03, 2019 at 08:59:35PM +0100, Rowland penny via samba wrote:> On 03/10/2019 20:30, Christopher Cox via samba wrote: > > > > > > > Took a while to get a bugzilla account.? Submitted > > https://bugzilla.samba.org/show_bug.cgi?id=14151 > > > I am not the expert here, but: > > A) you are using Samba as a standalone server 'security = user' > > B) you also seem to want to use another server for passwords 'password > server = ldap.skopos.me' > > C) Samba tries to use kerberos : > > ???? Enter SKOPOS\ccox's password: cli_session_creds_prepare_krb5: Doing > kinit for ccox at SKOPOS to access doc_svr2 > ???? kerberos_kinit_password: as ccox at SKOPOS using [MEMORY:cliconnect] as > ccache and config [(null)] > > ???? And fails: > > ???? Kinit for ccox at SKOPOS to access doc_svr2 failed: Cannot find KDC for > requested realm > > ???? But then seems to authenticate via kerberos: > > ???? Kinit for ccox at SKOPOS to access doc_svr2 failed: Cannot find KDC for > requested realm > > Do you want to use kerberos ? > > If so, change 'security = user' to 'security = ads' and it might work. > > Can you also tell us just how you are trying to connect to the Samba server, > are you using smbclient, a GUI or what ?This isn't talking to a Samba server, it's smbclient talking to a MacOS/X server. wireshark trace on that bug is corrupt, but as it's a 4.9.x build I'm guessing this is a path in the client libraries that messes up and allows an SMB1 frame to be sent on an SMB2 connection. I vaguely remember such bugs getting fixed by Metze in the past. But I'll take a look at the specific version and see. Jeremy.