GAL/LDAP issues with Entourage 2004

G

GVanWagner

I've verified with our IT folks that LDAP is on, and requires a login,
however, when I attempt connect through Tools/Directory Services, I get an
error: -3253 (whatever that indicates). I'm never given a opportunity to
login. Does Entourage automatically assume that the login is the same as the
email address? Our internal network is setup as xxxx.crp, not xxxx.com and
my login for the LDAP server is (I'm told) [email protected]. Is that the
issue, or am I missing something? If it is the issue, is there a
fix/workaround?

Thanks
 
D

Dave Cortright

I've verified with our IT folks that LDAP is on, and requires a login,
however, when I attempt connect through Tools/Directory Services, I get an
error: -3253 (whatever that indicates). I'm never given a opportunity to
login. Does Entourage automatically assume that the login is the same as the
email address? Our internal network is setup as xxxx.crp, not xxxx.com and
my login for the LDAP server is (I'm told) [email protected]. Is that the
issue, or am I missing something? If it is the issue, is there a
fix/workaround?

Thanks

Go to Tools:Accounts:Directory Services and create a new LDAP account using
you company's server and your .crp credentials. See if that works. You don't
need to use the built in LDAP field in the Exchange account. It's merely a
convinience (for those without weird setups like yours, of course :)
 
G

GVanWagner

Unfortunately, that doesn't work, although I now sometimes get an error that
says that directory services was unable to perform the search. I'm not sure
if that's an improvement or not.
 
S

Steve Gualandri

GVanWagner said:
Unfortunately, that doesn't work, although I now sometimes get an error that
says that directory services was unable to perform the search. I'm not sure
if that's an improvement or not.


When you get the error message "Directory Services was unable to
perform the search", do you see Error 17799 in the bottom left hand
corner of the error window? LDAP/GAL used to work for me using Office
X. Since I upgraded to Office 2004, I get the same error message that
you get. It also says Error 17799. I cannot find the meaning of
error code 17799.
 
Top