similar to: userAccountControl can't be set to 0x800002 (8388610, UF_ACCOUNTDISABLED | UF_PASSWORDEXPIRED):"samldb: Unrecognized account type"

Hi once again my greetings I rewrite because I'm in the same situation but this time in debian 7 using samba4.0.6. The account lockout policy does not work, got help from some colleagues but nothing I fail to solve the problem, I have recommended using Zentyal 3.0 but it's my favorite distro is debian and do not feel right changing. This time I used a Windows 7 client and I

Hello, I'm writing in regards to this issue I opened on GitHub: https://github.com/python-ldap/python-ldap/issues/275 I am able to successfully use ldapsearch to query my Samba 4.9.4-Debian DC: ldapsearch -LLL -Y GSSAPI -H ldap://samba-dc.ad.example.com -b "dc=ad,dc=example,dc=com" "(objectClass=user)" "sAMAccountName" However, when I try to use python-ldap I

Hi list ! I've been trying to get a fileserver with kerberised NFS4 and Samba going on a RHEL 6.3 box, with a 2k8r2 AD backend, using the rpm's provided by Redhat. (3.5.10-125) I also tried the rpms from sernet (both 3.6 and 3.5) with no success... The Join to the domain works: # net ads join createcomputer="Servers/LINUX systems"

I am using the shovel deploy.rb from http://nubyonrails.com/pages/shovel I have SwitchTower-ized my app, copied the shovel deploy.rb file and put my settings in it. But when I run "rake remote_exec ACTION=setup_lighty" from the local app root it has no effect. It should prompt for a password for at least throw an error? I just get returned to the DOS prompt. If I do "rake

hi, we want to replace our nt4 pdc/bdc with samba and we use windows nt4 terminal servers with citrix in our environment. as far as i know, we will get a problem here. (extensiver reading of the mailing list led me to this conclusion) regarding: http://ma.ph-freiburg.de/tng/tng-users/2001-05/msg00224.html >Terminal Server has its own User Manager (which has an extra button -

On Sat, 2018-01-06 at 11:11 +0000, Antonios Kalkakos via samba wrote: > I have an AD with two Debian Stretch Samba 4.5.12 DCs. The Samba and Heimdal Kerberos 7.1.0 packages are installed from Debian repositories. Management is done from MS-RSAT installed on a Windows 7 Pro client. > > When I select the option "Account is sensitive and cannot be delegated" (in Active Directory

On Wed, 2018-01-31 at 16:15 +0000, Antonios Kalkakos wrote: > On 6/1/2018 23:55, Andrew Bartlett wrote: > > On Sat, 2018-01-06 at 11:11 +0000, Antonios Kalkakos via samba wrote: > > > I have an AD with two Debian Stretch Samba 4.5.12 DCs. The Samba and Heimdal Kerberos 7.1.0 packages are installed from Debian repositories. Management is done from MS-RSAT installed on a Windows 7

On Tue, 27 Jun 2017 18:55:04 +0300 Alexander Bokovoy <ab at samba.org> wrote: > On ti, 27 kesä 2017, Rowland Penny via samba-technical wrote: > > On Tue, 27 Jun 2017 17:57:10 +0300 > > Alexander Bokovoy <ab at samba.org> wrote: > > > > > On ti, 27 kesä 2017, Rowland Penny via samba-technical wrote: > > > > > > > > > > >

On 6/1/2018 23:55, Andrew Bartlett wrote: > On Sat, 2018-01-06 at 11:11 +0000, Antonios Kalkakos via samba wrote: >> I have an AD with two Debian Stretch Samba 4.5.12 DCs. The Samba and Heimdal Kerberos 7.1.0 packages are installed from Debian repositories. Management is done from MS-RSAT installed on a Windows 7 Pro client. >> >> When I select the option "Account is

I have an AD with two Debian Stretch Samba 4.5.12 DCs. The Samba and Heimdal Kerberos 7.1.0 packages are installed from Debian repositories. Management is done from MS-RSAT installed on a Windows 7 Pro client. When I select the option "Account is sensitive and cannot be delegated" (in Active Directory Users and Computers under the Account tab) for a user account regardless of its

Greetings - In an offline-test environment, I just took a first crack at a classic upgrade of our Samba 3.6.9 (389-DS LDAP backend) environment to Samba 4.1.13 AD. Among other issues, I see that we have some group/SID issues to address. From the upgrade output: Could not add group name=guests ((68, "samldb: Account name (sAMAccountName) 'guests' already in use!")) Could not add

I've just install centos 5.0 on new PC. However it gives this error while installing per-Date-Calc: [root at piranha tmp]# perl -ivh perl-Date-Calc-5.4-1.2.2.1.i386.rpm Unrecognized character \xED at perl-Date-Calc-5.4-1.2.2.1.i386.rpm line 1. what could be the problem? --beast

Hi, I'm having strange warning from asterisk when I try to dial GSM Gateway: -- Executing [1011501522xxx at sm:1] NoCDR("SIP/ibm-b2c52848", "") in new stack -- Executing [1011501522xxx at gsm:2] Dial("SIP/ibm-b2c52848", "Zap/R3/501522xxx") in new stack -- Requested transfer capability: 0x00 - SPEECH [Jul 13 11:58:50] WARNING[18208]:

Hi list, I recently setup debian "testing/unstable" and did a package install of Xen with apt. The problem I''m having is when I do: xm create -c www.cfg I get the following errors: Using config file "/etc/xen/www.cfg". Error: (22, ''Invalid argument'') Looking at /var/log/xen/xend-debug.log I see: ==> /var/log/xen/xend-debug.log <== ERROR:

Hello all, I have successfully setup winbind with clients pointing to a central ldap server, and have had great results for ssh service logins, however i get wierd problems with gdm login attempts after winbind has been running for a while. Oct 10 14:45:26 ctilinux6 pam_winbind[2398]: request failed, but PAM error 0! Oct 10 14:45:26 ctilinux6 pam_winbind[2398]: internal module error (retval = 3,

https://bugzilla.samba.org/show_bug.cgi?id=3173 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From wayned@samba.org 2005-10-16 16:39

''-Wdeclaration-after-statement'' isn''t supported by gcc 3.3 which is what I am currently using. It was introduced into Config.mk in changeset 7973:c7508abc5b6b. I backed out the changes and everything appears to be building okay. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On

Even with gcc-4.1.1, gcc does not return an error if an option is not supported It just ouput a message to stderr but does not return a value different from 0. The result is that there is some warnings about every unrecognized option and compilation continue. barton syslinux-3.36 # gcc -dumpversion 4.1.1 barton syslinux-3.36 # gcc -ZZZ dummy.c; echo $? gcc: unrecognized option '-ZZZ' 0

Hi, LLVM-gcc can't recognize this option, don't know why, because the gcc in Mac OS X (quite old, compared to 4.2) can recognize it. - Filipe Cabecinhas

Hi Filipe, > LLVM-gcc can't recognize this option, don't know why, because the gcc > in Mac OS X (quite old, compared to 4.2) can recognize it. mainline gcc-4.2 doesn't recognize this option as far as I can see. Since llvm-gcc is based on gcc-4.2, it has inherited this behaviour from it. Ciao, Duncan.