From owner-freebsd-ports@FreeBSD.ORG Wed Mar 5 03:30:12 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 858492CE for ; Wed, 5 Mar 2014 03:30:12 +0000 (UTC) Received: from foccosweb.foccosweb.com (foccosweb.foccosweb.com [198.154.229.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 63B357B0 for ; Wed, 5 Mar 2014 03:30:12 +0000 (UTC) Received: from 200-207-142-128.dsl.telesp.net.br ([200.207.142.128]:60950 helo=CPDMARCELO) by foccosweb.foccosweb.com with esmtpa (Exim 4.82) (envelope-from ) id 1WL1lX-0004kp-Mo for freebsd-ports@freebsd.org; Tue, 04 Mar 2014 23:41:04 -0300 From: "William Marcelo Piovezan" To: Subject: Re: samba36 on 10-RELEASE can't join AD Date: Tue, 4 Mar 2014 23:41:02 -0300 Message-ID: <0d7401cf381c$5b5bb410$12131c30$@uli.com.br> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: Ac84GhVVH4hTBXjZQOatlyftzhJWrQ== Content-Language: pt-br X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - foccosweb.foccosweb.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - uli.com.br X-Get-Message-Sender-Via: foccosweb.foccosweb.com: authenticated_id: william@uli.com.br Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2014 03:30:12 -0000 Hi,=20 =20 I'm getting exactly the same problem as described in this message. I was using FreeBSD 9.2 with samba36 working in a Windows environment, = the DC is Windows 2012. I=B4ve just updated to FreeBSD 10 and could not join AD anymore. Kinit = works perfectly buy net ads join returns the following error: =20 Failed to join domain: failed to connect to AD: Looping detected inside krb5_get_in_tkt =20 After several retries, the computer account at Windows DC has been = locked (maybe due to domain policy). I=B4ve deleted the account and tried to = join again but the same problem happened. But for some reason the computer account is added to the Windows DC even with the Samba error. Trying = wbinfo -u returns nothing so I suspect the machine has not been added at all. Is there anyone that could solve or workaround this problem? I have the latest samba36.22 with heimdal installed. =20 > I can't seem to join AD with samba36 on 10-RELEASE: >=20 > pacija at server:/usr/local/etc % sudo net ads join -U pacija > Enter pacija's password: > kerberos_kinit_password pacija at EXAMPLE.ORG failed: Looping > detected > inside krb5_get_in_tkt Failed to join domain: failed to connect to AD: > Looping detected inside krb5_get_in_tkt >=20 > Kerberos seem to work OK, i can get tickets with kinit. Same krb5.conf > and smb.conf on another 9.2-RELEASE machine are joining AD without > problem. >=20 > Any suggestions? > -- > Marko Cupa=E6 < = marko.cupac at mimar.rs > > _______________________________________________ > = freebsd-ports at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to " freebsd-ports-unsubscribe at freebsd.org > " =20 =20