microsoft.public.inetserver.iis.security
  Home FAQ Contact Sign in
microsoft.public.inetserver.iis.security only
 
Advanced search
July 2008
motuwethfrsasuw
 123456 27
78910111213 28
14151617181920 29
21222324252627 30
28293031    31
2008
 Jan   Feb   Mar   Apr 
 May   Jun   Jul   Aug 
 Sep   Oct   Nov   Dec 
2008 2007 2006  
total
microsoft ... iis.security Profile…
RELATED GROUPS

POPULAR GROUPS

more...

 Up
  Kerberos - Multi-domain SPN problem         


Author: bake
Date: Jul 7, 2008 15:09

I have an interesting problem with Kerberos and our network setup, i'll try
to keep it simple.

Client user is ADDomain1.com/user.
IIS Web Site service account user is ADDomain2.com/serviceuser.
DNS alias points to web site via website.NotAnADDDomain.com.
ADDomain1.com and ADDomain2.com have 2 way full trusts.

The actual URL we want to use is http://website.NotAnADDomain.com (which is
obviously not an AD domain, just domain setup via DNS). So we register the
SPN as:
SetSPN -A HTTP\host1.NotAnADDomain.com ADDomain2.com/serviceuser

So when ADDomain1.com/user talks to ADDomain1.DC (KDC) to get the kerberos
ticket, we get an KDC_ERR_S_PRINCIPAL_UNKNOWN error ("Server not found in
Kerberos database")

I assume that is due to the HTTP\website.NotAnADDomain.com SPN; the
ADDomain1 DC/KDC does not even know to point the ADDomain1.user to
ADDomain2.KDC to get the kerberos ticket. Is that right?

Is there a mapping we can put in that would tell ADDomain1.KDC that when it
gets a request for that SPN/host (website.NotAnADDomain.com), it should point
the client to the DC/KDC in ADDomain2 where the serviceuser account exists?
Show full article (1.35Kb)
6 Comments