similar to: Cloning from a backup: unable to reach any KDC in realm

Andrew Bartlett wrote: > Don Kuenz wrote: >> >> Greetings, >> >> This post pertains to a Disaster Recovery (DR) scenario on a Samba 4.8 >> server. The DR server was provisioned as a standalone host, on a >> network isolated from the Production Server (PS). >> The DR's /var/db/samba4 directory, which contains the private >> directory,

On Fri, 2019-11-15 at 20:16 +0000, Don Kuenz via samba wrote: > > Greetings, > > This post pertains to a Disaster Recovery (DR) scenario on a Samba > 4.8 > server. The DR server was provisioned as a standalone host, on a > network isolated from the Production Server (PS). > The DR's /var/db/samba4 directory, which contains the private > directory, was then

On Thu, 19 Jul 2018 17:33:46 +0200 Anton Blau via samba <samba at lists.samba.org> wrote: > Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: > > On Wed, 18 Jul 2018 23:21:41 +0200 > > Anton Blau via samba <samba at lists.samba.org> wrote: > > > >> Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: > >> > > It is touched on here:

On Wed, 18 Jul 2018 23:21:41 +0200 Anton Blau via samba <samba at lists.samba.org> wrote: > Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: > > On Wed, 18 Jul 2018 13:49:39 +0200 > > Anton Blau via samba <samba at lists.samba.org> wrote: > > > > Hmm, your REALM is 'SMBDOMAIN.FILE.DUCK' but your dnsdomain appears > > to be just

Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: > On Wed, 18 Jul 2018 23:21:41 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: >> > It is touched on here: > > https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Parameter_Explanation >

On Mon, 23 Jul 2018 23:09:58 +0200 Anton Blau via samba <samba at lists.samba.org> wrote: > Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: > > On Thu, 19 Jul 2018 17:33:46 +0200 > > Anton Blau via samba <samba at lists.samba.org> wrote: > > > >> Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: > >>> On Wed, 18 Jul 2018 23:21:41

Try change your resolv.conf from : >nameserver 127.0.0.1 >domain intranet.mayweg.net to nameserver 192.168.11.250 search intranet.mayweg.net >The only thing I was unsure about, was which hostname to enter >for Kerberos >Server and Kerberos admin server when asked during the >installation of the >packages.. Try these defealt settings for kerberos.. You didnt have to

can you run these commands and tell us the output. ( copy past it. ) SETFQDN=`hostname -f` SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SETSERVERIP=`hostname -i` echo "==========Test DNS Records ===============================" echo "Testing : dns entries" if [ -z "`host -t SRV _ldap._tcp.${SETDNSDOMAIN}. | grep 'not found'`" ]; then echo

Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: > On Wed, 18 Jul 2018 13:49:39 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > > Hmm, your REALM is 'SMBDOMAIN.FILE.DUCK' but your dnsdomain appears to > be just 'duck' > > Rowland > I read https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ - but I am not sure that my

Greetings, The process to join a new samba 4.6 DC to an existing samba 4.1 DC repeatedly caused: samba_dnsupdate --verbose --all-names to fail on the new DC with: Failed to connect host x.x.x.x on port 49152 - NT_STATUS_CONNECTION_REFUSED Noted: both samba versions are obsolete and will be updated post haste. Regardless, samba_dnsupdate was accidentally invoked on the new DC while the

On 22/03/16 14:38, Daniele Manfredi wrote: > Il 22/03/2016 14.45, Rowland penny ha scritto: >> On 22/03/16 13:35, Daniele Manfredi wrote: >>> Good afternoon, >>> I have installed a fileserver with samba4 environment. >>> This is configured to works as AD-DC even if I only use it as a >>> fileserver (at the moment). >>> All seems to works fine

On 20/03/15 11:13, Timo Altun wrote: > Hi guys, > > thanks again for the quick answers. First, the smb.conf on the linux > fileserver. It is quite long, as I took the old file (working version from > samba3 configuration) and only made adjustments, like adding the realm. > > /etc/samba/smb.conf: > [global] > ### Browsing/Identification ### > > workgroup =

Good morning! First of all thanks Rowland for the fast answer yesterday! I realized that samba-technical might have been the wrong mailing list and switched it to the normal samba users list (hopefully it worked, as it does get a bit confusing with spamgourmets addresses!). Unfortunately the problem with samba_dnsupdate remains after the changes. I did changed the smb.conf, krb5.conf, and hosts

On Thu, 14 Feb 2019 21:43:43 +0200 Ashley via samba <samba at lists.samba.org> wrote: > > On 2019/02/14 21:12, Rowland Penny via samba wrote: > > On Thu, 14 Feb 2019 19:14:19 +0200 > > Ashley via samba <samba at lists.samba.org> wrote: > > > >> Hi there > >> > >> I have migrated from an older version of Samba DC to Samba 4.9.4 >

Thank you for the answers Peter and Rowland and sorry to everybody for the spam...switched to another e-mail address and hope my messages will arrive only once from now on. As I wrote in my first mail, Kerberos does work. I can successfully request and list a ticket on the AC DC. kinit administrator at INTRANET.MAYWEG.NET Password for administrator at INTRANET.MAYWEG.NET: klist Ticket cache:

On Thu, 14 Feb 2019 19:14:19 +0200 Ashley via samba <samba at lists.samba.org> wrote: > Hi there > > I have migrated from an older version of Samba DC to Samba 4.9.4 AD. > Running Centos 7. One server with everything on...  (AD and file > server) Bind 9.9.4 > > Built from source. > Followed directions in the wiki. > All seems to go fine, but when I startup

Version 4.0.0alpha18-GIT-957ec28 After starting samba -i -d3, wbinfo -i someuser gives this: ldb_wrap open of secrets.ldb using SPNEGO Selected protocol [8][NT LANMAN 1.0] Cannot reach a KDC we require to contact cifs/hh3.site at SITE : kinit for HH3$@SITE failed (Cannot contact any KDC for requested realm) SPNEGO(gssapi_krb5) NEG_TOKEN_INIT failed: NT_STATUS_NO_LOGON_SERVERS ldb_wrap open of

Hi list: I joined Samba4.1.7 to Windows2k3 R2 domain, when I run: *samba_dnsupdate --verbose --all-names* IPs: ['192.168.186.137'] Skipping PDC entry (SRV _ldap._tcp.pdc._msdcs.${DNSDOMAIN} ${HOSTNAME} 389) as we are not a PDC Skipping PDC entry (SRV _ldap._tcp.pdc._msdcs.${DNSFOREST} ${HOSTNAME} 389) as we are not a PDC Traceback (most recent call

Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: > On Thu, 19 Jul 2018 17:33:46 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: >>> On Wed, 18 Jul 2018 23:21:41 +0200 >>> Anton Blau via samba <samba at lists.samba.org> wrote: >>> >>>> Am 18.07.2018 um

I had freshly installed an Ubuntu Server 12.04lts and Samba 4.0.1 using the internal DNS. I followed the official HowTo until "kinit administrator at DOMAIN.LOCAL" It didn't work (cannot contact any kdc...) A "netstat" showed that "avahi-daemon" was running at: 807/avahi-daemon: r udp 0 0 10.0.0.20:389 0.0.0.0:* After removing that package