search for: nfigurator

Did you run the command to disable the password check or complexabilty on all you DC's? That is needed. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: dinsdag 24 oktober 2017 15:33 > Aan: samba at lists.samba.org > Onderwerp: [Samba] 'check password script'

...ialize'' /home/20062/data/rubygems/gems/gems/mongrel-1.0.1-i386-linux/lib/mongrel.rb:720:in `new'' /home/20062/data/rubygems/gems/gems/mongrel-1.0.1-i386-linux/lib/mongrel.rb:720:in `run'' /home/20062/data/rubygems/gems/gems/mongrel-1.0.1-i386-linux/lib/mongrel/configurator.rb:271:in `run'' /home/20062/data/rubygems/gems/gems/mongrel-1.0.1-i386-linux/lib/mongrel/configurator.rb:270:in `each'' /home/20062/data/rubygems/gems/gems/mongrel-1.0.1-i386-linux/lib/mongrel/configurator.rb:270:in `run'' /home/20062/data/rubygems/gems/gems/mon...

Somebody knows if Samba 4.1 supports to join Windows 2012 server as a secondary DC?? Because after compiling samba 4.1 in an ubuntu server i try to join to a Windows 2012 server and get this error: root at samba41:~/compilar/samba-4.1.0# /root/compilar/samba-4.1.0/bin/samba-tool domain join zentyal.it.com DC -Uadministrator --realm=zentyal.it.com Finding a writeable DC for domain

Make a note: it is better to disable 'check password script' in the DC(s) before trying to join a new DC. ;( root at vdcpp1:~# samba-tool domain join ad.my.dom DC -U"MYDOM\administrator" --dns-backend=BIND9_DLZ Finding a writeable DC for domain 'ad.my.dom' Found DC vdcsv1.ad.my.dom Password for [MYDOM\administrator]: workgroup is MYDOM realm is ad.my.dom Adding

On 12 April 2016 at 07:31, Rowland penny <rpenny at samba.org> wrote: > > The schema is in another NC, so use the 'cross-ncs' switch to see the > schema. Thanks Rowland - adding --cross-ncs worked and I can now see the schema extensions using ldbedit. I can confirm that my schema extensions are definitely present, including as mentioned in the record below, which I

> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : samedi 26 août 2017 12:00 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > ... > On Sat, 26 Aug 2017 11:28:00 +0400 > > Hi, > > > > I have begun to add a new 4.6.7 DC (following

On 12/04/16 22:21, Jonathan Hunter wrote: > > > On 12 April 2016 at 07:31, Rowland penny <rpenny at samba.org > <mailto:rpenny at samba.org>> wrote: > > The schema is in another NC, so use the 'cross-ncs' switch to see > the schema. > > > Thanks Rowland - adding --cross-ncs worked and I can now see the > schema extensions using

I was playing around again with Windows and when you add members to silos, or remove them, it should not set/unset assigned silo on the user. So I've got a new pull request in Draft state still where I remove that functionality, as well as add some new commands to samba-tool user command. It turned out to be easier to add sub commands to user, as edit user wasn't quite what I thought

UNCLASSIFIED Hi Andrew and Roland, I originally installed samba-4.1.7 on CentOS 6.5. I successfully joined the domain. I intended to take over from the 2003 server but because the domain was being heavily used, I delayed seizing the roles. Now I really, really want to replace the 2003 server. The network is currently not in use and I want to complete the job while I have an opportunity. If I

Thanks Rowland. In here, I can see the objects I have created using my schema extensions, but I cannot see the schema classes or attributes themselves; I don't know if that is the problem. I'm not sure if by running ldbedit on sam.ldb, this does not include the contents of CN=Schema,CN=Configuration,DC=mydomain,DC=... or if it does include this part of the AD tree and these items are

> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : lundi 21 août 2017 16:34 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Mon, 21 Aug 2017 15:52:01 +0400 > HB via samba <samba at lists.samba.org> wrote: > > > Hello all,

Guys, > On 10/02/2020 14:40, L.P.H. van Belle via samba wrote: >> @Rowland. >> >> I now see he only mailed me. >> Here you go.. > No, he emailed me as well, but I missed this: > samba-tool domain join domain.com DC -k yes --dns-backend NONE > --server=vm-dc1.domain.com > Why did he do that ? why no dns server ????? This is b/c we used to host AD zone on

Hai, Ok. I did more digging, this is a link Dennis showed which might help.. https://www.itprotoday.com/windows-78/q-how-can-i-create-domaindnszones-directory-partition Now, if i go throught the mailing list and lookup everything abotu this part. > Could not find machine account in secrets database: Failed to fetch > machine account password for DOM from both secrets.ldb (Could not

After I upgraded my installation of R for OS X (Tiger) to 1.12, it consistently crashes when calling the function acf() [stats lib]. Roberto Osorio

A problem here getting winbind traffic to be encrypted using Kerberos. I have set up a test environment with a pair of servers (actually lxc containers): - samba server (ubuntu 16.04, stock samba 4.3.11) - client machine (ubuntu 16.04) joined with "net ads join" and winbind The client machine has the following in /etc/samba/smb.conf: ------- [global] #netbios name = client-ad

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >