Re: Unfollowed continuation reference

Stu wrote:
> I have a user "user1" who is in the the following DN
> CN=Computers,DC=ctronsoft,DC=com
> 
> When I issue the command
> 
> 
> host=corpntpd01
> port=389
> startingDN="CN=Computers,DC=ctronsoft,DC=com"
> 
> ID="CN=rndtest,OU=Generic User IDS,DC=ctronsoft,DC=com"
> PASSWORD="tsetdnr"
> 
> 
> $CTRONHOME/bin/ldapsearch -T -h $host -p $port  -w $PASSWORD -D "$ID" -
> b "$startingDN" "(&(cn=user1)(objectclass=*))"
> 
> Everything works fine and I get back my results!!!
> 
> Yet when I issue the same query but change my startingDN from
> ""CN=Computers,DC=ctronsoft,DC=com" to  "DC=ctronsoft,DC=com"
> 
> I get back all my values plus the following.
> 
> Unfollowed continuation reference(s):
>     ldap://ForestDnsZones.ctronsoft.com/DC=ForestDnsZones,DC=ctronsoft,DC=com
> Unfollowed continuation reference(s):
>     ldap://DomainDnsZones.ctronsoft.com/DC=DomainDnsZones,DC=ctronsoft,DC=com
> Unfollowed continuation reference(s):
>     ldap://ctronsoft.com/CN=Configuration,DC=ctronsoft,DC=com
> 
> Can anybody tell me why this is happening and how I can prevent this
> from either my application or AD server.

AD uses continuation references for everything.  There is really no way 
you can get around this.  AD clients must be able to handle all of these 
continuation references.