similar to: Using isc-dhcp for DDNS with Samba4 internal DNS

Displaying 20 results from an estimated 10000 matches similar to: "Using isc-dhcp for DDNS with Samba4 internal DNS"

2015 Jun 24
2
Using isc-dhcp for DDNS with Samba4 internal DNS
On 24/06/15 14:17, Luca Olivetti wrote: > El 24/06/15 a les 14:30, James ha escrit: >> Hello, >> >> Is it possible to use isc-dhcp for DDNS with Samba internal DNS? I >> would rather not use bind as I understand you can't use Windows DNS tool >> to manage. Thanks. > > Yes, it is possible, look here: > > >
2015 Jun 24
2
Using isc-dhcp for DDNS with Samba4 internal DNS
El 24/06/15 a les 17:02, James ha escrit: > On 6/24/2015 10:13 AM, Rowland Penny wrote: >> On 24/06/15 14:17, Luca Olivetti wrote: >>> El 24/06/15 a les 14:30, James ha escrit: >>>> Hello, >>>> >>>> Is it possible to use isc-dhcp for DDNS with Samba internal DNS? I >>>> would rather not use bind as I understand you can't
2015 Jun 25
0
Using isc-dhcp for DDNS with Samba4 internal DNS
El 24/06/15 a les 22:12, Luca Olivetti ha escrit: >> I appreciate all the responses. I do not want to lose the ability for >> clients to update DNS. It appears I will if I follow the link posted. > > No, there's no problem, since the script waits 5 seconds in order to > give the client time to update its record. And if the client doesn't do > it, the the script
2015 Feb 27
8
Internal DNS strangeness in 4.1.16
Hi, ? I have just provisioned a new samba setup with 2 DCs running ISC DHCPd in failover and I?m trying to get it to play nice with samba internal DNS but I?m having some issues. 1) I?m using on commit, etc triggers in the dhcpd config to call a script that calls samba-tool to add, delete or update DNS. This script works fine when I call it from the command line as the dhcpd user but when called
2019 Oct 11
4
dns replication error due to deleted records
El 11/10/19 a les 16:59, Luca Olivetti via samba ha escrit: > El 11/10/19 a les 16:12, Rowland penny via samba ha escrit: >> Try running this on a DC: >> >> samba-tool ldapcmp ldap://DC1 ldap://DC2 >> --filter='whenChanged,dc,DC,cn,CN,ou,OU' >> >> Replace 'DC1' and 'DC2' with your actual DC short hostnames >> >> It should
2019 Oct 10
2
dns replication error due to deleted records
El 10/10/19 a les 20:41, Rowland penny via samba ha escrit: >> It turns out that dc2 chokes on "\0ADEL" dns records, supposedly >> deleted objects. > > What you have there is known as a tombstone record and Samba has a tool > to remove them: > > samba-tool domain tombstones expunge NC > --tombstone-lifetime=TOMBSTONE_LIFETIME > > Where
2019 Oct 10
2
dns replication error due to deleted records
El 10/10/19 a les 21:07, Rowland penny via samba ha escrit: >> > It works in a similar way to how I update dns records and I have similar > records in AD and they replicate. Oh, but they do. Until the replication chokes on those deleted records. Never happened until September 25 (though I realized only today when a manually added host resolved erratically). > > Can you post
2018 Sep 03
5
winbindd crashing -- how to auto-heal?
El 3/9/18 a les 17:13, Rowland Penny via samba ha escrit: > Yes, but it depends on how you run Samba. If you run Samba as a > standalone server you only need to run 'smbd', but running 'nmbd' as > well would be a good idea. > > If you run Samba as a PDC or BDC, the same as a standalone server goes. > > Anything else needs both smbd and winbind running. It
2018 Sep 03
2
winbindd crashing -- how to auto-heal?
On Mon, 3 Sep 2018 15:37:03 +0200 Luca Olivetti via samba <samba at lists.samba.org> wrote: > El 3/9/18 a les 15:23, Robert Marcano via samba ha escrit: > > >> > >> I run this cron job every minute. Winbind usually crashes once or > >> twice a day > >> > >> #!/bin/bash > >> getent group | grep -q 513 && exit 0 >
2019 Oct 11
2
dns replication error due to deleted records
On 11/10/2019 14:58, Luca Olivetti via samba wrote: > El 10/10/19 a les 20:23, Luca Olivetti via samba ha escrit: >> Today I noticed something that has been going on for some weeks: >> >> I have 2 dc, (dc1 and dc2) both debian buster with the distro >> provided samba (4.9.5), recently upgraded from stretch. >> >> samba-tool drs showrepl on dc2 says >>
2019 Oct 10
4
dns replication error due to deleted records
Today I noticed something that has been going on for some weeks: I have 2 dc, (dc1 and dc2) both debian buster with the distro provided samba (4.9.5), recently upgraded from stretch. samba-tool drs showrepl on dc2 says DC=DomainDnsZones,DC=samba,DC=wetron,DC=es Default-First-Site-Name\DC1 via RPC DSA object GUID: 89812346-9037-43b0-86ab-c5052f55125d
2010 May 03
3
win 7, samba 3.4.7, error 0x000003e6 with some printers
Hello, I'm testing windows 7 with samba 3.4.7 and I'm using PrintUIEntry to connect the printers. With some of those printers the connection fails (client side) with error 0x000003e6. The strange thing is that: 1) trying the same connection against samba 3.0.11 works (alas, no domain functionality with that old version) and 2) two of the failing printers share the same driver with
2016 Apr 19
2
samba security updates broke NT4 DC setup
I've been running a NT4-style domain with a samba 3.x PDC using a LDAP back end and it's mostly worked very will for a long time. However since yesterday, clients are having problems with the domain. I saw that updates came out on all my systems - my PDC and BDC are ubuntu 12.04 LTS. The samba version there still seems to be 3.6x. A client with a problem that was working is Ubuntu
2016 Mar 12
2
The sad state of samba 4 adaption for home/small business routers.
El 12/03/16 a les 18:27, Jeremy Allison ha escrit: > On Sat, Mar 12, 2016 at 06:07:25PM +0100, Luca Olivetti wrote: >> Unfortunately it seems it is using a really old version of samba [...] >> Version 1.9.16p10 >> -D become a daemon >> -p port listen on the specified port >> -d debuglevel set the
2016 Apr 15
5
samba 4.4.2 freeradius authentication with ntlm_auth
Hi; Samba team say "It is recommended that administrators set these additional options, if compatible with their network environment:" ntlm auth = no I use samba with FreeRadius. I configure "ntlm_ auth = no" but freeradius users not connected to wifi. I use ntlm_auth in FreeRadius side.. best regards
2017 Apr 22
2
Samba AD with internal DNS: Can't resolve aliases anymore
Am 22.04.2017 um 14:56 schrieb Luca Olivetti via samba: > Check nsswitch.conf. Make sure you just have "iiles dns" in the hosts > line. Yes, that's the case. Bye... Dirk -- Dirk Heinrichs <dirk.heinrichs at altum.de> GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015 Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch:
2017 Apr 05
1
Filter query
Hi Luca, thank you very much for the tip. I’ve tried to run it with the filter the web page suggests and I got an empty set. I took a look at one of the user objects and I couldn’t see any samAccountType there. > On 04 Apr 2017, at 19:54, Luca Olivetti via samba <samba at lists.samba.org> wrote: > > El 04/04/17 a les 16:17, Juan García-Pardo via samba ha escrit: >> The
2018 Sep 02
2
winbindd crashing -- how to auto-heal?
El 2/9/18 a les 01:03, Luca Olivetti via samba ha escrit: > El 1/9/18 a les 03:03, Jamie Jackson via samba ha escrit: >> Hi folks, >> >> Every couple days any one of my project's 10 or so RHEL VMs can't be >> logged >> into with a domain account (active directory integration). Our admin goes >> in with a local account and restarts winbind to fix it.
2018 Sep 03
2
winbindd crashing -- how to auto-heal?
El 3/9/18 a les 16:35, Jamie Jackson via samba ha escrit: > I didn't set this up, but I assume the sysadmins didn't run it because > they, like Luca, probably assumed that smbd was for server functionality I didn't assume, it's the documentation that says so. In fact, the winbindd man page says that the winbind daemon provides services to smbd and ntlm_auth, not the
2010 Apr 29
2
Samba 3.3.12/3.4.7/3.5.2 on "ancient" server stops responding/dies
Hello, I'm trying to upgrade samba (TPTB are going to introduce win7 workstations) on my old server (mandrake 10.0) currently running 3.0.11. I setup a virtual machine to do some testing and I built rpms for 3.5.2 (apart from the other problems it has this one https://bugzilla.samba.org/show_bug.cgi?id=7263) then for 3.4.7 and finally for 3.3.12. Each one of them has problems, the most