similar to: REVISION_MISMATCH

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

Dear everybody, I want to give a shout "Did anybody test smbclient4 against smbd4 using SMB2". I failed to do so. I always got the error NT_STATUS_REVISION_MISMATCH. I don't believe that my configuration is wrong. I am checking the source code, but I really want somebody to tell me if they have done it and succeeded. Thanks Jun

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 >

Thank you for answer. Logged in as Guest, then went to Security tab. I see `Everyone', it is given all permissions. Then I went to `Current permissions' tab (I have localized OS at the moment, so probably it is not correct name) and typed in `Everyone' and `Guest' as well: all five permission types are checked. $ smbclient -L 192.168.0.100 -m SMB2     Sharename      

Shanks for the hint! Very strange that the default is only to use a deprecated protocol… Anyway, this option has no effect on this issue… Yvan Le 31/05/2019 à 18:53, Kris Lou via samba a écrit : > Most likely, your Windows 10 (file server) is disallowing SMB1 connections, > which is the default for smbclient. > > You can force smbclient to use a higher protocol with "smbclient

Most likely, your Windows 10 (file server) is disallowing SMB1 connections, which is the default for smbclient. You can force smbclient to use a higher protocol with "smbclient -m SMB2" https://www.samba.org/samba/docs/current/man-html/smbclient.1.html Kris Lou klou at themusiclink.net On Fri, May 31, 2019 at 9:45 AM Yvan Masson via samba <samba at lists.samba.org> 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

Hi all, Sorry for this question which has certainely already been answered, but I could not find info in the list nor in the wiki. From my Debian laptop running testing (samba 4.9.5) and with an empty smb.conf (I wanted to be sure that only default values are used), I can not browse shares of a Windows 10 machine (sorry, Thunderbird splits some lines): smbclient -L 192.168.122.200 Unable to

I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared printer that I cannot set up but I am not sure if this is a CentOS issue or a Samba issue. When I run the printer setup 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 ??????????????

Hi All, I am trying to migrate shares from my Win2k12 R2 AD server(SJCLAB2.LOCAL) to Ubuntu 16.04 samba fileserver present in same domain. Samba version is 4.3.11-Ubuntu. Before migrating shares I was able to successfully join fileserver to Active Directory. Below is my samba server configuration. #======================= Global Settings ======================= [global] workgroup =

Hi all, Actually I have just updated my ubuntu pc with kernel 3.8.4 and did try succesfully with mount with cifs type with win7 pc with smb2 protocol.But I encountered failure with the tools, smbtree or smbclient or smbclient4 to list out the share directory.. Are these clients tools already support SMB2 protocol?Thanks for take time to read, thousand thanks! Regards,Wong

On 10/14/2019 1:54 PM, Giulio via samba wrote: > On Mon, Oct 14, 2019 at 5:55 PM gw1500 via samba <samba at lists.samba.org> wrote: >> I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared >> printer that I cannot set up but I am not sure if this is a CentOS issue >> smbclient -L dap001 -N >> Unable to initialize messaging context >>

We have the situation where we are trying to send to a server that has a cluster configuration. When we negotiate, it tells us to talk 3.11. When we actually try to send the file, the share's max protocol is actually only 3.02 and so the Microsoft server sends a NT_STATUS_SMB_BAD_CLUSTER_DIALECT, which means they expect the client to reconnect negotiating only 3.02 as max protocol. Looking

Setting my domain controllers to use SMB2 breaks windows domain authentication for Windows clients. I don't know why. The clients in question are Windows 7 and Windows 2008 R2. Once I set the domain controllers and problem member server to server max protocol = NT1 server min protocol = NT1 client max protocol = NT1 client min protocol = NT1 the

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

On Wed, 21 Jun 2017 11:55:47 -0400 Gaiseric Vandal via samba <samba at lists.samba.org> wrote: > I increased the logging to 10 on the problem member server. Didn't > see anything of interest. > > I did a packet capture on the PDC while typing " net rpc testjoin" > from both the problem member server (4.4.14) and a working member > server (4.4.13) > >

I increased the logging to 10 on the problem member server. Didn't see anything of interest. I did a packet capture on the PDC while typing " net rpc testjoin" from both the problem member server (4.4.14) and a working member server (4.4.13) e.g SMB: ----- SMB Header ----- SMB: SMB: CLIENT REQUEST SMB: Command code = 0x72 SMB:

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

Good catch. I had set server max protocol to NT1 after upgrading from samba 3.x to 4.x . Some windows clients had problems with SMB2 and file shares (tho this should not really be an issue with the domain controllers.) I have now set the dc's to server max protocol = SMB2 server min protocol = NT1 and the client machine to be client max protocol = SMB2

Hello again, Jeremy, first of all, I am terribly sorry for my late reply. I tried to send my posting many times, but my mail has always been silently discarded by the Samba mail servers due to my main mail provider (GMX - a very large German mail provider with millions of customers) having been blacklisted by SORBS. For the time being, SORBS is still unwilling to delist them for unknown