Re: ADAM's LDAP ports configuration

From: Dmitri Gavrilov [MSFT] (dmitrig_at_online.microsoft.com)
Date: 09/08/04


Date: Tue, 7 Sep 2004 21:44:44 -0600

Sorry, I don't understand the question. Can you try again?

ADAM lets you select the ports. AD does not. If you have AD on a machine, it
means it is a domain controller.

-- 
Dmitri Gavrilov
SDE, Active Directory Core
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"J. Young" <anonymous@discussions.microsoft.com> wrote in message
news:7a7201c4951c$47c40c70$a301280a@phx.gbl...
>
> Using Windows 2003 Server I thought I was given the option
> to assign the LDAP port numbers through Active Directories
> Application Mode right before given the option for an
> application directory partition.
>
> In this situation Active Directory would not be the
> Primary Domain Controller (but user credentials could be
> verified through AD) and another LDAP could run on 389
> without the port conflicts. (This LDAP could be for
> descriptors and not be related to user authentication).
>
> In a nutshell, is it possible to change the Active
> Directories (assuming not a domain controller) in Windows
> 2003 server but not in Windows 2000 server.
>
> thanks Dmitri


Relevant Pages

  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, then you won't need the other ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... Made the exchange ldap anonymous, ... I receive 2 when the server restarts. ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)
  • Re: New DC behind a firewall
    ... Active Directory Replication over Firewalls ... Connecting to directory service on server mydc. ... DcDiag: a dcdiag exception raised, ... "LDAP query to speficied LDAP server on TCP port 389 failed ...
    (microsoft.public.windows.server.active_directory)
  • RE: LDAP + Active Directory
    ... Subject: LDAP + Active Directory ... LDAP server on it's rootdse. ... This list is provided by the SecurityFocus Security Intelligence Alert ...
    (Pen-Test)

Loading