similar to: kinit user works, kinit user@domain.local doesn't

---------- Forwarded message ---------- From: Dania Ramirez Moya <dania181087 at gmail.com> Date: 2015-03-30 16:45 GMT-04:00 Subject: Re: Fwd: samba_dnsupdate failed with RuntimeError: kinit for SMB4ECONOMIA$@ECONOMIA failed (Cannot contact any KDC for requested realm) To: Rowland Penny <rowlandpenny at googlemail.com> Cc: samba <samba at lists.samba.org> Hello rowland I tested

Thank you Louis for that answer! Actually I did get kinit and samba_dnsupdate working, though I am unsure how. I tried some changes to krb5.conf in the [realms] and [domain_realm] sections, als well as setting dns_lookup_realm = false to true, but reverted it all back to the initial file: [libdefaults] default_realm = INTRANET.MAYWEG.NET dns_lookup_realm = false dns_lookup_kdc = true After a

Hi everyone, unfortunately, I managed to break my Samba AD DC configuration :-( and would like to ask the experts on this list. When restarting my Samba AC DC I noticed, that it didn't come up properly. samba outputs the following lines to /var/log/syslog > Nov 24 12:46:52 addc01 samba[30784]: /usr/sbin/samba_dnsupdate: > RuntimeError: kinit for ADDC01$@MYDOMAIN.LAN failed (Cannot

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 = MAYWEG.NET realm = INTRANET.MAYWEG.NET netbios name = server13 smb ports = 139, 445

Timo Altun schrieb am 19.03.2015 10:30: > As I wrote in my first mail, Kerberos does work. I can successfully request > and list a ticket on the AC DC. OK, then next things, which come to my mind are: is the keytab, you set in named.conf.options readable for the user, under which bind is run. Then, is the /etc/bind/namedb writable for bind. And in the end, it might be a screwed up

Ok, I setup a new smb.conf and rebooted. Winbind doesn't seem to pass on the domain users anymore and the DNS Update during domain join still fails. For some reason, although I have all samba 3.5.6. packages installed on this debian squeeze samba -V or samba-tool are unknown commands. Maybe this is why the dns update fails, some missing tools or commands? wbinfo -u and wbinfo -g return domain

I'm trying to test Samba4 as an AD style pdc. following the instructions at http://wiki.samba.org/index.php/Samba4/HOWTO at step 9 I get root at pdc:~# kinit administrator at MYDOMAIN.COM kinit: Cannot contact any KDC for realm 'MYDOMAIN.COM' while getting initial credentials root at pdc:~# and yet host -t SRV _kerberos._udp.mydomain.com gives _kerberos._udp.mydomain.com has

On 28/03/15 21:15, Dania Ramirez Moya wrote: > > Hello, thank you Rowland for you response > Yes, it is.This domain was installed with a single label, just > ECONOMIA. Is that a problem? It could be, the realm name is usually the DNS domain name, whilst the windows domain name is just one word and is usually the left hand part of the realm name. i.e. if the DNS domain name is

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 sendto addresses!). Unfortunately the problem with samba_dnsupdate remains after the changes. I did changed the smb.conf, krb5.conf, and

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

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

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 =

Hi there, I am struggling with samba4 and the internal dns and kerberos. It seems that DNS is the problem. When I aske for kerberos dns entrys on my workstation, I get this (11.22.33.202 is the samba4 server): root at lit2:~# dig _kerberos._udp.DOMAIN.LOCAL @11.22.33.202 ; <<>> DiG 9.7.3 <<>> _kerberos._udp.DOMAIN.LOCAL @11.22.33.202 ;; global options: +cmd ;; Got

Hello! I've followed your tutorial to change the IP Address of our Samba AD DC: https://wiki.samba.org/index.php/Changing_the_IP_Address_of_a_Samba_AD_DC But the samba_dnsupdate tool always crashes with this output: samba_dnsupdate --verbose Unknown parameter encountered: "ks" Ignoring unknown parameter "ks" IPs: ['192.168.68.201'] Looking for DNS entry A

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

I spoke too soon in my last email. My DNS is not working. The host commands from the AD DC how-to all fail with NXDOMAIN. nslookup says server can't find nikola.ozco.home. Basically the same message. Here is a dump of my many tries. ----------------------------------------------------------------------------------------------------------------- nikola ~ # export

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:

August 21, 2017 5:34 PM, "Rowland Penny via samba" <samba at lists.samba.org> wrote: > On Mon, 21 Aug 2017 15:37:03 +0000 > "A. James Lewis" <james at fsck.co.uk> wrote: > >> OK, obviously I am slightly sanitising the output here, but I'm >> preserving the case, and just replacing local names with generic ones >> as I did for the

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

I just pushed out klibc-1.2.1; it actually has a working kinit. There are still pieces missing, but at least it works for ipconfig+nfsroot, which has been my test configuration. There is code to handle initrd already in kinit, but it hasn't been tested and so is almost certainly broken; I think the code to load a ramdisk from a floppy or other block device is not yet there. -hpa