Active Directory, Child domain logins with ad login authority, help needed!

Hello, I've successfully configured SGD 4.2.983 to login using Active Directory as a login authority. In my base domain let's say domain.com) I can create users, and use DSI to publish apps based on groups, etc.

When I create a child domain (child1.domain.com) a user from this domain cannot login to the server. I've setup my kerberos (krb5.conf file) to contain the child domain, and using kinit, can get a ticket from the child1.domain.com domain, but when I try to login with the web interface, I get: (this is using either user@child1, user@child1.domain.com or either with caps or without)

2006/10/13 12:18:21.763 (pid 4593)server/ldap/error#1160756301763

Sun Secure Global Desktop Software (4.2) ERROR:

LDAP call failed: lookupLink-.../_ldapmulti/forest/("DC=CHILD1,DC=DOMAIN,DC=COM") 1ms javax.naming.PartialResultException: [LDAP: error code 10 - 0000202B: RefErr: DSID-0310063C, data 0, 1 access points

ref 1: 'CHILD1.DOMAIN.COM'

]; remaining name 'DC=CHILD1,DC=DOMAIN,DC=COM'

A call to LDAP failed. This might mean LDAP users cannot log in.

Check the operation was correct, the LDAP configuration is valid, and the

LDAP server is still running.

From other articles on the net, I've found that the ldap error code seems to be a referral error. But couldn't find anything so far in the docs or on this forum concerning my problem.

Does anyone have a similar working setup? This server is going to be used by many separate divisions, and using child domains simplifies management by allowing people from each division to manage their division entirely.

Thanks for your time!

[1670 byte] By [Oriso_Solutions] at [2007-11-26 10:47:06]
# 1
Have you tried to set the depth of searches? http://docs.sun.com/source/819-4309-10/en-us/base/standard/using_dsi.html#neste d
carmelomtta at 2007-7-7 2:59:20 > top of Java-index,Desktop,Sun Secure Global Desktop Software...
# 2

Sadly yes, I did try, but it didn't change anything at all, I get the same error, almost word for word (except for the time and id of the instance of the error).

I'm wondering, since using ad:// didn not work for me for authenticating, ldapp:// did though, if it can cause this problem. I'm working on getting authentication to work with the ad:// url and will see if having set the depth search to 1 (since I don't intend to go further in child domains) will help.

If not, I assume it's an AD problem where my account that does have rights on both domain cannot access the child somehow, but I'm totally blank as to how I'll resolve this.

Thanks for your help though!

Oriso_Solutions at 2007-7-7 2:59:20 > top of Java-index,Desktop,Sun Secure Global Desktop Software...
# 3

For those who might have the same problem, or a similar one, the problem was two fold:

1) I had ldap://domain.com as a ldap url, instead of ad://domain.com.

I had this because ldap:// worked, whereas ad:// did not. The reason was.... too long a password for the admin account . It ended up working when I tried another account with a shorter password.

2) since I had put it a depth of 1 on the previously posted link reference, it worked afterwards.

Hope this might help people who get the same problems!

Oriso_Solutions at 2007-7-7 2:59:20 > top of Java-index,Desktop,Sun Secure Global Desktop Software...