similar to: DHCP-DNS problems

Displaying 20 results from an estimated 2000 matches similar to: "DHCP-DNS problems"

2017 Dec 18
5
DHCP-DNS problems
On 18 December 2017 at 16:20, Rowland Penny via samba <samba at lists.samba.org > wrote: > > > Even this looks wrong, I would expect something like this: > > Dec 18 07:43:59 dc3 dhcpd: DHCPREQUEST for 192.168.0.111 from > cc:4e:ec:e9:c8:d3 via eth0 > Dec 18 07:43:59 dc3 dhcpd: DHCPACK on 192.168.0.111 to cc:4e:ec:e9:c8:d3 > via eth0 > Dec 18 07:47:33 dc3 dhcpd:
2017 Dec 18
0
DHCP-DNS problems
On Mon, 18 Dec 2017 15:55:10 +0000 Kristján Valur Jónsson via samba <samba at lists.samba.org> wrote: > Hello there. > So, I have a Samba AD setup, with DHCP and samba_dlz setup as > described in the wiki. > > However, I find that after a while, dynamic DHCPD updates stop > working. The fix is for me to restart the named server. > > When in this state, I get log
2018 Jan 02
0
DHCP-DNS problems
On Tue, 2 Jan 2018 15:11:59 +0000 Kristján Valur Jónsson <kristjan at rvx.is> wrote: > Here are log files from my two DCs that are set up in redundant DHCP > mode. One of them is running with the -v flag in dhcp-dyndns, hence > is much more verbose. > dc02 is the primary, dc03 is secondary > log_dc02, log_dc03, show a failed dyndns session from Fridriks_iphone. > >
2018 Dec 28
6
replication failing for 4.9.4
Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >
2018 Dec 28
1
replication failing for 4.9.4
so the DC with FSMO is not done first?     Van: Kristján Valur Jónsson [mailto:kristjan at rvx.is] Verzonden: vrijdag 28 december 2018 17:08 Aan: L.P.H. van Belle Onderwerp: Re: [Samba] replication failing for 4.9.4 dc01 is still running 4.7.7.  No need to restart it.  There is also still a DC03 running 4.7.7.  the only one I've upgraded is DC02.  resolv.conf on DC02 is configured with
2019 Jan 02
2
replication failing for 4.9.4
On Wed, 2 Jan 2019 09:54:24 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 2 Jan 2019 09:45:56 +0000 > Kristján Valur Jónsson <kristjan at rvx.is> wrote: > > > Any thoughts? Have code, will debug. The error itself is > > meaningless to me and I am deeply and utterly unfamiliar with samba > > code, but if you have any thought or
2018 Jan 09
3
samba_dlz shutting down on named reload
Hello there. I´ve been having problems with dynamic dns update by dhcp on my samba ADDC running on CentOS 7 on an RPI2. After a while, the dhccp_dyndns.sh stops stops being able to authenticate with named. for the longest time I was stumped with this, exploring all kinds of kerberos issues, but found out that *restartint* named did resolve the issue. I have finally traced this problem down to a
2018 Aug 15
2
DDNS with bind9 and isc-dhcp-server
Hello List, Hello Rowland :-) again I'm having problems with the DDNS. I did it as shown in the wiki. I took all teh scripts from the wiki the dhcp-dyndns.sh is Version: 0.8.9 I configured everything including the failover. When I start the two DHCP-Server everything is perfect. I see the right messages in the log, the two DHCP-Servers are talking to each other. When a Client ask for an
2017 May 17
3
Samba AD DNS problem
Hello there. I have a setup with Samba AD and a Named backend. Everything has been working fine, until a few days ago, I cannot start the DNS snap-in from windows. I get a dialog box saying "Access was denied. Would you like to add it anyway?" If I enable level 3 debugging in the samba.conf, I get the following: [2017/05/11 07:25:30.413481, 3]
2017 Nov 30
2
Samba AD /dns /dhcp
Hello there. I hope I'm in the right place for some Samba AD advice. I recently added two extra ADs to a setup I inherited. Originally there was a single Samba AD with BIND9_DLS config. DHCP was separate. Subsequently I installed Samba on two Raspberry Pis to act as backup servers. Basically, I followd this set of instructions:
2019 Jan 02
0
replication failing for 4.9.4
On Wed, 2 Jan 2019 09:45:56 +0000 Kristján Valur Jónsson <kristjan at rvx.is> wrote: > Any thoughts? Have code, will debug. The error itself is > meaningless to me and I am deeply and utterly unfamiliar with samba > code, but if you have any thought or experiments in mind... > > On Fri, 28 Dec 2018 at 16:07, Rowland Penny via samba > <samba at lists.samba.org>
2019 Jan 02
0
replication failing for 4.9.4
Ok, but is there another upgrade path possible, e.g. via 4.8? I am upgrading via source build, btw. The reason I'm asking is because i've been asked me to check using samba git 'master" source to check that pesky bind restart bug ( https://bugzilla.samba.org/show_bug.cgi?id=13214) Since this is in production, I need to get my environment up to "latest" in order to do
2018 Dec 28
0
replication failing for 4.9.4
On Fri, 28 Dec 2018 15:38:59 +0000 Kristján Valur Jónsson via samba <samba at lists.samba.org> wrote: > Hi there. > I'm trying to upgrad from 4.7.7 to 4.9.4. > I built from source, running on centos 7.6 on a Raspberry Pi. > When testing on a secondary DC, my "samba-tool drs showrepl" errors > out with: > > ERROR(<class
2018 Dec 28
0
replication failing for 4.9.4
Hai, DC1, did you reboot it or just restarted services, i advice a reboot. Then on DC2. Samba internal DNS by accident? If so, stop samba, set log level = 10 Start it wait 30 sec, stop it. Now change the resolv.conf so DC1 is the first contacted. and start it again. Test again. Now im out the office in 15 min, but try this. Keep these logs, a samba dev may ask for it. Greetz,
2019 Feb 25
2
AD-DC samba_gpoupdate failing
Well, I had a look at the python bindings and the error handling was in shambles. I fixed libgpo/pygpo.c and I now get: gpos = ads.get_gpo_list(creds.get_username()) SystemError: Failed to get machine token for 'DC01$' (CN=DC01,OU=Domain Controllers,DC=rvx,DC=is) (the failing call is status = gp_get_machine_token(self->ads_ptr, frame, dn,
2018 Jan 30
2
Samba 4.7.4 + bind9 DLZ /backend/ dropping delegated domain
No, I'm reading the dlz_bind9.c code. I've found and fixed the problem. It turns out that using a reference counted singleton is a bad idea. The singleton is defunct after reload. If we simply create a new state object and destroy the old one as bind is trying to let us do, things work out fine. This works, at least, for bind9.9. I cant test with the older (9.8), so it is possible that
2018 Jan 17
2
samba_dlz shutting down on named reload
To a user, samba_dlz just doesn't work correctly with bind. There are two obvious options a) bind is broken somehow and unloads all modules when reloading b) samba_dlz is somehow broken in the way that it interfaces with bind, perhaps it misinterprets the signal to 'reload' when it receives it from bind. As a user, i have no way of knowing which is it is, all that I know is that
2018 Jan 19
1
samba_dlz shutting down on named reload
On 17 January 2018 at 16:00, Kristján Valur Jónsson via samba < samba at lists.samba.org> wrote: > Well, I had a cursory glance dlz_bind9.c and also the bind9 source code I > could find ( > http://users.isc.org/~each/doxygen/bind9/dlz__dlopen__driver > _8c-source.html) > and didn´t see any provision for 'reload' in there. > bind is clearly calling the dlz_destroy()
2018 Jan 02
0
DHCP-DNS problems
On Tue, 2 Jan 2018 16:15:14 +0000 Kristján Valur Jónsson <kristjan at rvx.is> wrote: > Sure, here it is. > However, notice that named appears to enter a state where it refuses > the updates, and restarting *only *named, fixes it. Unsure how to > explain that. I also tried removing the cached samba credentials > from /tmp and recreating them, etc, but no luck. The
2017 Apr 25
3
Setup a new samba AD DC
Il giorno mar, 25/04/2017 alle 13.26 +0100, Rowland Penny via samba ha scritto: > On Tue, 25 Apr 2017 14:07:05 +0200 > Dario Lesca via samba <samba at lists.samba.org> wrote: > > > I have setup a new Samba Active Directory DC on Fedora 25 and > > samba- > > 4.5.8-1.fc25.x86_64, rebuild from src.rpm with dc option enable. > > > > This system