similar to: "Samba 4" - "smbd"; "can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL" error but only for a single domain user ("Server 2008 R2" domain, "Server 2008" functional level forest).

I have tested the patch against 4.3.1 compiled from sources but it does not seem to work. Either I did something wrong while compiling, or the patch dosen't fix the problem. ERROR(<type 'exceptions.ValueError'>): uncaught exception - unable to parse dn string File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run return

To be clear, I mean the patch from Andrew Barlett, 24.09.2015 09:57. It is tested, it works and thus should get upstream, shouldn't it? Dňa 02.11.2015 o 14:14 Rowland Penny napísal(a): > On 02/11/15 12:32, Mgr. Peter Tuharsky wrote: >> I think the tool should act consistently. I.e., it can cope with >> automatically provisioned groups - when they exist in imported domain

I think the tool should act consistently. I.e., it can cope with automatically provisioned groups - when they exist in imported domain too, it simply displays a warning "group already exists" and goes on. I think this is the right behaviour that should apply to users too. Peter Dňa 01.11.2015 o 19:54 Rowland Penny napísal(a): > On 01/11/15 18:30, Andrew Bartlett wrote: >> On

Good day oh technical ones . I was running Samba 4 (client only, not using it as a DC so effectively running Samba 3 code from the Samba 4 tree) and, other than a little "Gotcha!" regarding decoding Kerberos PACs, it was all working perfectly. Then recently I had to upgrade, to "4.2.0pre1-GIT-b505111" (I had to upgrade the OS on the server

Hello Everyone, I am fairly new to puppet and I would like to run som unit tests. I hope rspec is the right tool for it. Unfortunately, after setting it up, when I try to execute it I receive the following error: Failures: 1) helloworld Failure/Error: it { should include_class(''helloworld'') } Puppet::Error: Error converting value for param

Good day oh technical ones . I was running Samba 4 (client only, not using it as a DC so effectively running Samba 3 code from the Samba 4 tree) and, other than a little "Gotcha!" regarding decoding Kerberos PACs, it was all working perfectly. Then recently I had to upgrade, to "4.2.0pre1-GIT-b505111" (I had to upgrade the OS on the server

We observe a difference between a Windows 7 client and Windows 2003/XP client when accessing directories that should be accessible via the UNIX accounts primary group GID. Windows client refuses access. Ignoring for now why the two different client behaviours (either some subtle difference in the requests or the way the Samba reply is dealt with) the question is what should be the correct

I have a set of Linux boxes with (nearly) working Samba configurations. Windows users can get in and work with shares. My one problem is that the local user "joe" is not the same as the domain user that logs into Samba. And that means that users cannot access their own home directories, unless I relax the Linux permissions. This is not surprising, given the way Samba was configured

On Fri, 25 Aug 2017 16:03:08 +0200 "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org> wrote: > Rowland, > > > I'm following this thread because I'm trying to use Linux member > server (Debian 9) and use Windows AD users in Linux (filesystem etc). > > It seems I have working Kerberos and to a degree, Winbind too, > because both > >

Hi, I thought Samba4 was able to do everything what was doing Samba3. According to that isn't it possible for you to add a new DC into your NT4 domain which runs Samba4? As it is a DC in addition to others DC (those running Samba3) your domain should continue to work as it did for years. You would just get another DC running more recent Samba. I expect that Samba4 as filesrv is able to

Thank You Rowland. I did it like You say, killed avahi, added the record without domain suffix, but nothing changed, and the record seems no different compared to other records added with the suffix some time before. My Samba DNS record looks like this (and I see nothing special in there):   Name=, Records=3, Children=0     SOA: serial=39, refresh=900, retry=600, expire=86400, minttl=3600,

On 04/20/2016 5:22 AM, Mgr. Peter Tuharsky wrote: > Hallo > > The Debian team was unable to keep 4.1.17 patched, so they switched to > 4.2 branch. However, fileserver at this version (4.2.10) is no more able > to communicate with DC at samba 3.5 (unable to authenticate users - got > weird rpc version error in log) > > Please, are there any parameters that could make this

Rowland, thank You, but this removes only the NS record, but the faulty domain A records remain. How to deal with them, I don't know. They behave unlike the ordinary A records. Name=, Records=8, Children=0     SOA: serial=27, refresh=900, retry=600, expire=86400, minttl=3600, ns=blacktux.interbronz.local., email=hostmaster.interbronz.local. (flags=600000f0, serial=27, ttl=3600)     NS:

Thank You, Rowland, for Your answer Dňa 6. 11. 2018 o 11:43 Rowland Penny via samba napísal(a): > On Tue, 6 Nov 2018 11:00:26 +0100 > "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org> wrote: > >> Hi, >> >> we have a network-hosted app for windows that is being executed from >> smb share. The app worked well with Windows up to 7. >>

Hello, I am stuck with a error when setting password for a couple of specific users. This error makes impossible to set the password for the affected users. In Windows I get an operation error but the samba-tool output is more informative: samba-tool user setpassword user2 --newpassword= New Password: ndr_pull_error(11): Pull bytes 2 (../librpc/ndr/ndr_basic.c:103) ERROR: Failed to set

OK, I've traced this a little further on now. I think I have followed the trail via the following items that call or refer to each other in turn: - python samba-tool ntacl sysvolreset - source3/smbd/pysmbd.c: SMB_VFS_FSET_NT_ACL( fsp, security_info_sent, sd); - source3/include/vfs_macros.h:#define SMB_VFS_FSET_NT_ACL smb_vfs_call_fset_nt_acl - source3/smbd/vfs.c:NTSTATUS

Well, finally I found the recommendations against .local here: https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ However, still, the originating wiki should AFAIK be more verbose. https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller For now it only says "Make sure that you provision the AD using a DNS domain that will not need to be

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mgr. > Peter Tuharsky via samba > Verzonden: woensdag 20 februari 2019 10:28 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba + BIND9 DLZ. DNS dosen't resolve > FQDN, only short hostname > > Well, the mystery is solved. It WAS Avahi, in a way...

On Thu, 2015-11-19 at 12:54 +0100, Javier Amor Garcia wrote: > Hello, > > I am stuck with a error when setting password for a couple of > specific > users. This error makes impossible to set the password for the > affected > users. > > In Windows I get an operation error but the samba-tool output is more > informative: > > > samba-tool user setpassword

Hello List We run a Solaris9 Server running Samba 3.0.20, Local Users (no winbind) but authenticating against ADS. There are up to 800 concurrent users, mostly Windows XP SP3. When clients access MyDocuments, which is redirected to the Samba share, we observe several "Session Setup AndX Request"s followed by "Session Setup AndX Response, Error: