GAL via ADAM

[tekkey2007]

Hello All,

Has anyone had success or even tried to access the GAL externally with
Entourage configured to use ADAM as the LDAP source? If so, any info,
docs, steps, etc. would be greatly appreciated.

I was originally having issues with getting ADAM to sync over the
users from AD. Now that I have that issue resolved and have all my
users in ADAM with their e-mail addresses, it looks like I am having a
problem with authentication. When we try to do a lookup we get an
error, "An unknown error (-17768) occurred.".

Does anyone know what authentication method Entourage uses? I was
under the impression that since the ADAM instance was running on a
domain member, it would use pass-through authentication to pass the
Entourage credentials to AD.

Again, any help would be greatly appreciated.

Thanks!

 

[tekkey2007]

Hello All,

Has anyone had success or even tried to access the GAL externally withEntourageconfigured to use ADAM as the LDAP source?  If so, any info,
docs, steps, etc. would be greatly appreciated.

I was originally having issues with getting ADAM to sync over the
users from AD.  Now that I have that issue resolved and have all my
users in ADAM with their e-mail addresses, it looks like I am having a
problem with authentication.  When we try to do a lookup we get an
error, "An unknown error (-17768) occurred.".

Does anyone know what authentication methodEntourageuses?  I was
under the impression that since the ADAM instance was running on a
domain member, it would use pass-through authentication to pass theEntouragecredentials to AD.

Again, any help would be greatly appreciated.

Thanks!

I have this working now. Well, kind of. My users are able to do
address book lookups in Entourage while outside the network with no
VPN connection needed. The address book actually resides in an ADAM
instance running on the Exchange front-end server. The above error
message (17768) still shows up sporadically though. But, if you close
the error message everything still seems to work fine.

I think it may be related to the search base in the LDAP config. The
search base I have listed is in the form of dc=domain,dc=net, which is
tha name of the ADAM application partition that holds the address book
entries. Anyone know what can be causing the above error?

Thanks.