similar to: DC's are still unavailable when PDC halted

Displaying 20 results from an estimated 400 matches similar to: "DC's are still unavailable when PDC halted"

2017 Nov 13
1
[airween@gmail.com: DC's are still unavailable when PDC halted]
Hi folks, sorry for the re-post, I need some help to solve this problem. Since my previous e-mail, we made a set-up: there is a Clear Pass device (Aruba), which controlls the network access for users. Between the CP and these two DC's there is a load balancer. But, when we stopped the DC1, which was set up first, and the DC2 works continously, then the authentication of users is stopped
2017 Nov 08
2
DC's are unavailable when PDC halted
Hi, On Wed, Nov 08, 2017 at 03:21:28PM +0000, Rowland Penny wrote: > On Wed, 8 Nov 2017 14:33:28 +0100 > Ervin Hegedüs <airween at gmail.com> wrote: > > > When I turned off the open-ldap2, and open-ldap works, then the > > wbinfo -a returns with succeed, but only after 30 seconds. > > > OK, the problem here is not that you have turned off the first DC, it
2017 Nov 08
0
DC's are unavailable when PDC halted
On Wed, 8 Nov 2017 17:20:09 +0100 Ervin Hegedüs <airween at gmail.com> wrote: > Hi, > > > On Wed, Nov 08, 2017 at 03:21:28PM +0000, Rowland Penny wrote: > > On Wed, 8 Nov 2017 14:33:28 +0100 > > Ervin Hegedüs <airween at gmail.com> wrote: > > > > > When I turned off the open-ldap2, and open-ldap works, then the > > > wbinfo -a returns
2012 Mar 25
1
how to speed up OpenSSH command execution (and a speed analysis)
Hi. I recently did some investigation about how to get out the last microseconds of executing commands via OpenSSH on remote host (of course I'm using ConnectMaster). MOTIVATION: I'm introducing Nagios (well actualla Icinga) at the local institute. We have many active checks that must run locally on the remote hosts. The "best" way to do this is using NRPE (Nagios Remote
2017 Nov 08
3
DC's are unavailable when PDC halted
Hi Rowland, On Wed, Nov 08, 2017 at 12:12:20PM +0000, Rowland Penny wrote: > On Wed, 8 Nov 2017 12:43:16 +0100 > Ervin Hegedüs <airween at gmail.com> wrote: > > > > You would be better using the DCs ipaddress rather than '127.0.0.1'. > > > You should also remove '10.10.0.1' it doesn't seem to be a DC. > > > > yes, that's the
2010 Apr 29
0
[LLVMdev] Why the same code is much slower in JIT compared to separate executable?
On 04/29/2010 12:13 PM, Yuri wrote: > Török Edwin wrote: >> How long does it take for llc to compile it? >> Remember that the JIT includes code generation time > > llc takes almost no time (0.00 user as measured by time), code is tiny. > Are you using 2.6 or 2.7, 32-bit or 64-bit? With 2.7 on x86-64 I get: lli: real 0m9.564s user 0m9.557s sys 0m0.004s a.out:
2016 Jun 07
2
Samba AD member lost domain join after reboot
I put the usermapping but this does not solve the problem. I do not use libpam_winbind and libpam-krb5 because I did not need to log in server using domain accounts, it seems to me that this is not mandatory, you confirm ? Here are the permissions of the file /etc/krb5.keytab: root at smb1:/home/adminlocal# ls -l /etc/krb5.keytab -rw------- 1 root root 2312 Jun 7 14:44 /etc/krb5.keytab Avahi
2016 Jun 07
0
Samba AD member lost domain join after reboot
I was wrong, the problem persists, it is not because of the DNS. You have the same configuration as me, but with two domains controller ? On 07/06/2016 18:05, Alexis RIES wrote: > I think I found my problem, when configuring my second domain > controller, I have created by mistake a round robin DNS entry on > "Forward Lookup Zones -> ad.samdom.local". > I speak of
2016 Jun 07
0
Samba AD member lost domain join after reboot
On 07/06/16 17:05, Alexis RIES wrote: > I think I found my problem, when configuring my second domain > controller, I have created by mistake a round robin DNS entry on > "Forward Lookup Zones -> ad.samdom.local". > I speak of round-robin because I have two fields A pointing to the > same domain > > Now I'm lost, you have a second domain controller in
2016 Jun 08
1
Samba AD member lost domain join after reboot
Hi, I used the DNS management console, right click on zone and "export list". I use Bind9, and yes it is configured. Alexis. On 07/06/2016 18:29, Rowland penny wrote: > On 07/06/16 17:05, Alexis RIES wrote: >> I think I found my problem, when configuring my second domain >> controller, I have created by mistake a round robin DNS entry on >> "Forward Lookup
2018 Jun 17
0
Connection problem due to tdb_lock failed
On Sun, 17 Jun 2018 12:06:17 +0000 Oren Kishon via samba <samba at lists.samba.org> wrote: > We are using Samba 4.6.15. We have users not being able to login. > winbindd log shows this: > > > [2018/06/14 14:48:44.300203, 0, > pid=3228] ../source3/rpc_client/cli_pipe.c:3292(cli_rpc_pipe_open_schannel_with_creds) > netlogon_creds_cli_get returned NT_STATUS_UNSUCCESSFUL
2016 Jun 07
6
Samba AD member lost domain join after reboot
I think I found my problem, when configuring my second domain controller, I have created by mistake a round robin DNS entry on "Forward Lookup Zones -> ad.samdom.local". I speak of round-robin because I have two fields A pointing to the same domain Now I'm lost, you have a second domain controller in failover? If so, could you give me your DNS configuration? I need information
2016 May 04
0
Fwd: win bind extremely slow after Upgrade to 4.2
i have now try some other options: - Fresh install of Samba AD Member - rejoin Member - change from winbindd to winbind But nothing helps. Also really slow time ls -lisa /daten/samba/ insgesamt 48 8222 4 drwxrwxrwx 8 postmaster.postmaster kontrast_ws_quack_fischer 4096 Mai 3 15:52 . 2 4 drwxr-xr-x 12 root root 4096 Jan 25 15:30 .. 145 12
2016 Jun 08
2
Samba AD member lost domain join after reboot
I conducted many tests and I noticed that I lose the domain-join on SMB1 soon as I joined SMB2 in the domain. Step 1: SMB1 "net ads join -Uadministrator" -> OK Step 2: SMB1 "net ads testjoin" -> OK Step 3: SMB2 "net ads join -Uadministrator" -> OK Step 4: SMB2 "net ads testjoin" -> OK Step 5: SMB1 "net ads testjoin" ->
2018 Jun 17
3
Connection problem due to tdb_lock failed
We are using Samba 4.6.15. We have users not being able to login. winbindd log shows this: [2018/06/14 14:48:44.300203, 0, pid=3228] ../source3/rpc_client/cli_pipe.c:3292(cli_rpc_pipe_open_schannel_with_creds) netlogon_creds_cli_get returned NT_STATUS_UNSUCCESSFUL [2018/06/14 14:53:43.896350, 0, pid=3228] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)
2005 Dec 10
0
AMD64 Bench
Hello, Today I was benchmarking DV video on a AMD64: skinkie@zwartepiet ~ $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 47 model name : AMD Athlon(tm) 64 Processor 3500+ stepping : 0 cpu MHz : 2210.197 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes
2013 Aug 16
0
[LLVMdev] [Polly] Analysis of extra compile-time overhead for simple nested loops
On 08/15/2013 03:32 AM, Star Tan wrote: > Hi all, Hi, I tried to reproduce your findings, but could not do so. > I have investigated the 6X extra compile-time overhead when Polly compiles the simple nestedloop benchmark in LLVM-testsuite. (http://188.40.87.11:8000/db_default/v4/nts/31?compare_to=28&baseline=28). Preliminary results show that such compile-time overhead is resulted by
2016 Jun 07
2
Samba AD member lost domain join after reboot
On 6/7/2016 12:31 PM, Alexis RIES wrote: > I was wrong, the problem persists, it is not because of the DNS. > You have the same configuration as me, but with two domains controller ? > > On 07/06/2016 18:05, Alexis RIES wrote: >> I think I found my problem, when configuring my second domain >> controller, I have created by mistake a round robin DNS entry on >>
2017 Apr 26
2
Setup a new samba AD DC
Il giorno mer, 26/04/2017 alle 07.27 +0100, Rowland Penny via samba ha scritto: > On Wed, 26 Apr 2017 01:55:16 +0200 > Dario Lesca via samba <samba at lists.samba.org> wrote: > > Your problem is that you need to find out just who dhcpd runs as on > fedora. On Devuan it is root and everything just works. Yes, on Debian work. And with this patch: [root at fedora-addc ~]#
2017 Nov 08
0
DC's are unavailable when PDC halted
See inline comments, extraneous lines removed from post: On Wed, 8 Nov 2017 12:43:16 +0100 Ervin Hegedüs <airween at gmail.com> wrote: > > You would be better using the DCs ipaddress rather than '127.0.0.1'. > > You should also remove '10.10.0.1' it doesn't seem to be a DC. > > yes, that's the forwarder (see in smb.conf). Most documents >