Re: MSADC 8355 LDAP Result failed

The server that is "computername" in the event log is my DC win2ksp3 that I
want to install exchange 2003 on. It is running Norton Antivirus on it. I
have another DC that is my global catalog server.

I actually tested LDP from my PC and the DC. It connects to the DC that is
giving me the errors above and gives me a page full of information telling me
it is getting 1 entry. When I connect to the exchange 5.5 server, I just get
that it connected and getting 0 entries unless I enable anonymous access for
ldap through Exchange then it says 1 entry. Do I have to leave anonymous
access enabled?

"Al Mulnick" wrote:

I'm at a loss. The ADC is not supposed to "listen" on any ports that I'm
aware of. It open communications from a random port to tcp 389 on the
Exchange 5.5 server and the Active Directory domain controllers. I can
think of no reason that it would "listen" to anything on that port.

What server is "computername" in your event log? Is that your DC?
When you tested via LDP, what server were you on when you tested? Were you
on the DC and connected to itself? Was it the DC that answered?

Do you have any security software running on that DC that might be
interferring?



"jjneedshelp" <jjneedshelp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6E1151BE-B026-4ED6-BE79-75950541293E@xxxxxxxxxxxxxxxx
I didn't start receiving the LDAP errors until I installed ADC. The event
source is MSADC. The knowledgebase documents tell how to change the
exchange
server LDAP port if it is a DC but not the ADC LDAP port. For some reason
ADC is trying to start on port 389, but it is already in use since the
server
is a DC. I ran through all the deployment tools in order, and then
installed
ADC. That is when I changed the LDAP port on the exchange server, when
the
ADC tools were dimmed and wouldn't run.

I tried the LDP.exe utility, and I can connect to both servers.

I do not have many users. Only about 50.

Thank you for your help.

"Al Mulnick" wrote:

Huh? ADC isn't listening to tcp 389 last I checked (admittedly, it's
been a
while).
Your DC should be, however.

Try using LDP.EXE to connect to the DC specifically and see that it's
listening on tcp 389. You can use the same tool to verify that your 5.5
server is listening on 390.

If I remember correctly, there should be something that discusses running
ADC on a DC in your readme files. Might be worth a look. Also, I if you
have
a lot of users, putting the ADC on a DC is a performance drag - something
to
consider.




"jjneedshelp" <jjneedshelp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2DC1247A-DB41-4FEE-81A4-3F6D825A8B4D@xxxxxxxxxxxxxxxx
After installing ADC from Exchange sp2 I receive the error:

Event Type: Information
Event Source: MSADC
Event Category: LDAP Operations
Event ID: 8355
Description:
LDAP Result failed to receive a response from directory 'computername'
within 30 minutes.

Event Type: Information
Event Source: MSADC
Event Category: LDAP Operations
Event ID: 8006
Opening LDAP session to directory computername on port 389.


It is trying to run ADC on port 389, but this server is also a DC.
This
server is going to be my new Exchange 2003 running on win2ksp4. I need
to
migrate my exchange 5.5sp3 winnt4sp6a to it. I am able to change the
LDAP
port on my exchange 5.5 server to 390 and specify that in the ADC
tools,
but
cannot change the ldap port for ADC. Tried uninstalling and
reinstalling
ADC
from deployment tools, but does not help. None of the tools will run.
I
can
do step 1 in deployment tools, but the rest of the steps are dimmed.
Is
there any way to change the port for ADC?







.

Relevant Pages

  • Re: MSADC 8355 LDAP Result failed
    ... want to install exchange 2003 on. ... When I connect to the exchange 5.5 server, ... think of no reason that it would "listen" to anything on that port. ... ADC is trying to start on port 389, but it is already in use since the ...
    (microsoft.public.exchange.setup)
  • RE: DNS and Exchange issues
    ... with the Exchange Server after you have installed the patch 888619. ... XFOR: Telnet to Port 25 of IMC to Test IMC Communication: ... Start Exchange System Manager. ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • 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: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.setup)
Loading