Re: SRS Started - Not Listening on 379

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Rand Williams [MSFT] (randw_at_online.microsoft.com)
Date: 09/28/04


Date: Tue, 28 Sep 2004 13:40:48 -0500

Go to the ADC and get properties of the Config_CA
Verify the port it is using. The default is 379, but yours may be
different. If so, this is the port that the SRS would be using.

When Exchange 2003 is installed into a 5.5 site it detects what port 5.5 is
configured to use for LDAP.
If 5.5 is using the default Port of 389, the SRS will use the default port
of
379.
If 5.5 is configured to use a different port for LDAP, like port 390, the
SRS will
use port 390 as well.
This does not appear to create any issues.
Any ADC connection agreements configured to point to the SRS would need to
use the
SRS port of 390 as well.

NOTE: This means the Config_CA will default to using this port and any ADC
connection agreements that are configured to point to the SRS database, will
need
to be configured to use this port as well.

-- 
Hope that helps,
Rand Williams
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Adder" <asdf@asdf.com> wrote in message 
news:uGfgV6OnEHA.1800@TK2MSFTNGP15.phx.gbl...
> I'm trying to migrate from 5.5 to 2003, and one of the final steps of the
> deployment is to
> change the ADC connections to point to the new 2003 server on port 379. 
> I
> verified that the SRS service is started with no errors logged, but the
> server is not listening on that port.  Netstat does not list that port as
> active or listening, the PortQry tool also reports that the port is not
> listening either.  When I try to update my ADC connections to use the 2003
> server on that port the following error pops up:
>
> Unable to contact the Exchange server, please ensure that your connections
> are configured correctly.
> ID no: c103aa1d
> Microsoft Active Directory Connector Management
>
> In researching this problem, the advice found was to make sure the
> "Microsoft Exchange Site Replication Service" is started, as well as to 
> test
> the ports, with no further information.  Service started, port not
> listening....
>
> Any thoughts?
>
> -David
>
> 


Relevant Pages

  • Re: Administrative Groups Question
    ... I moved back the few mailboxes I had moved to 2003 back to the 5.5 server. ... I dont know what to do about SRS, It doesnt make any sense to me. ... server ADC connectors and set up ADC to syncronise with the new 2003 server ... listening on that hard-coded port. ...
    (microsoft.public.exchange.admin)
  • Re: MSADC 8355 LDAP Result failed
    ... The ADC is not supposed to "listen" on any ports that I'm ... Exchange 5.5 server and the Active Directory domain controllers. ... think of no reason that it would "listen" to anything on that port. ... server LDAP port if it is a DC but not the ADC LDAP port. ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... The LDAP errors seemed to be caused by my enabling logging in the ADC ... I receive 2 when the server restarts. ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... The ADC tools now all run!! ... The LDAP errors seemed to be caused by my enabling logging in the ADC tools ... I receive 2 when the server restarts. ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... I made sure that the user for the adc service ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)