[24922] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Kerberos referrals

daemon@ATHENA.MIT.EDU (Buck Huppmann)
Thu Nov 10 11:07:08 2005

Date: Thu, 10 Nov 2005 11:06:18 -0500
From: Buck Huppmann <buckh@pobox.com>
To: "Douglas E. Engert" <deengert@anl.gov>,
        Josh Howlett <josh.howlett@bristol.ac.uk>
Message-ID: <20051110160618.GC21134@dsl092-173-085.wdc2.dsl.speakeasy.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43726E86.5080607@anl.gov>
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu

> This may be the real problem. If there was a way to update the GC to go
> to the default realm. Hey its LDAP. I asked around, and it looks like it
> could be possible but no one knows how to do it.

assuming you're talking about the default realm being a non-Windows-AD;

and if the client requests a ticket for a fully-qualified hostname in-
stance (seems to depend on whether they manage to resolve the host by DNS
or NetBIOS first);

and if you're talking Windows 2003 AD servers and you do that netdom.exe
/foresttransitive trust establishment stuff with the default realm;

and everything is in the right phase;

then you can netdom.exe /addtln:uk (as long as that doesn't conflict with
anything more specific already added to the namesuffixes list[s]) along
with all the other TLDs you care about, to that default-realm trustedDomain
object. (yeah, i can't seem to wildcard the root, in my experimenting)

see the tail end of

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/539c5381-db4f-445f-aac0-2df5448181c1.mspx

for this particular netdom [ab]usage

and, yes, i realize it's tedious and error-prone and maybe not at all the
tree you're barking up
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post