Re: ldap on exchange 2003

Thanks! That was very helpful.
Do your mac users use entourage for email and if so what do they put for the
ldap address when prompted during setup of the directory (I think that's what
it is called)?
Do they just put dc1.domain name.com or whatever it is?

"Per Hagstrom" wrote:

Betsey wrote:
Thank you but I can do a google search myself, I would like links or support
on this from Microsoft. First I just want to know how to tell if my AD
server/exchange 2003 server is setup already, then if it is I need to know
how to find the address (i.e. ldap.itd.wmich.edu).
I have a mac client who needs to be able to query ldap in exchange so she
can get the global address book for Entourage and I don't know if we have it
setup and if we do what the address is to put in the Entourage program.

Betsey

"Mark Arnold [MVP]" wrote:

On Tue, 30 Oct 2007 12:39:01 -0700, Betsey
<Betsey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi.
We are running Exchange 2003. I would like to know how to tell if we have
ldap setup and if so what the address is.
Also, if it isn't setup I'd like to find instructions on how to set it up.
Thanks!
You've got a bit of reading to do.
http://www.google.co.uk/search?hl=en&q=%22Active+Directory%22+LDAP&meta=
Essentially your DCs are your "LDAP servers" and they are the systems
you interrogate to find directory information.

What has made you ask anyway?


I think all the Active Directory Domain Controllers have LDAP running by
default. Should be running on port 389. (636 for SSL)
My Exchange server, which isn't installed on a DC does not run LDAP by
default but we have Mac users and they talk to the DC's instead for LDAP
communication.

If you login to the server and open a command prompt you can use this
command to check if the server is listening on either port:

netstat -an | FIND "389"

You could always run telnet from a command prompt to check on it as well:

telnet serverip 389

Either you get "Could not open connection..." or the screen goes black
if the server actually is listening on this port.

Hope that helps you.

/ Per


.

Relevant Pages

  • Re: ldap on exchange 2003
    ... So I tried this 'DC.Domainname.lan' as the ldap server. ... With her credentials it fails and says the username is incorrect. ... setup and if we do what the address is to put in the Entourage program. ...
    (microsoft.public.exchange.admin)
  • Re: LDAP - howto get linux to talk to exchange/AD
    ... I agree - problem is DEFINITELY ldap authentication; ... my exchange server is setup to accept clear text, ... and my exchange server. ... My setup is a Novell Netware server hidden from the ...
    (Debian-User)
  • Re: ldap on exchange 2003
    ... Yes, to reply to you other question, you would use dc.domain.lan as the LDAP server. ... So yeah, if you have the option to use Outlook via Citrix, that would probably be the best way to go, if you are looking for the best client with most features. ... I have a mac client who needs to be able to query ldap in exchange so she can get the global address book for Entourage and I don't know if we have it setup and if we do what the address is to put in the Entourage program. ...
    (microsoft.public.exchange.admin)
  • Re: Win2K server
    ... Is there anything I can check to verify that the DNS is working properly? ... Go to a DOS prompt. ... then there is no name server. ... name server, AD setup will work. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Moving away from NIS. Options?
    ... Your setup is even older than ours. ... LDAP, and newer Solaris do as well, although they have more ... >We have an old Sun box running SunOS 4.1.3 acting as our NIS ... >server and we would like to move away from using this ...
    (RedHat)