General discussion

  • Creator
    Topic
  • #2280900

    RPC errors between Exchange 5.5 and E2k

    Locked

    by thetechguy ·

    We have installed two exchange 2000 servers into exiting exchange 5.5 site which has two exchange 5.5 servers.
    MAILSRV1 – Exchage 5.5 server SP4
    MAILSRV2 – Exchange 5.5 server SP4
    MAILSRV3 – E2K server SP3
    MAILSRV4 – E2K server SP3

    MAILSRV1,2 eventlog is logging the following errors every 10 minutes and there is no mail flow from MAILSRv1,2 to MAILSRV3,4. If users who are having mailboxes on MAILSRV3,4 sends mail, it is stuck in X400 queue.

    Source : MSExchangeMTA
    Category : Interface
    Event ID : 9318
    Description:
    An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 79, NT/MTA error code: 5. Comms error 5, Bind error 5, Remote Server Name MAILSRV4 [MAIN BASE 1 500 %10] (14)

    Source : MSExchangeMTA
    Category : X.400 Service
    Event ID : 289
    Description:
    A connection to /O=ABC/OU=XYZ/CN=CONFIGURATION/CN=SERVERS/CN= MAILSRV4/CN=MICROSOFT MTA could not be opened. [MTA XFER-IN 17 26] (12)

    Source : MSExchangeMTA
    Category : Interface
    Event ID : 9318
    Description:
    An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 80, NT/MTA error code: 5. Comms error 5, Bind error 5, Remote Server Name MAILSRV3 [MAIN BASE 1 500 %10] (14)

    Source : MSExchangeMTA
    Category : X.400 Service
    Event ID : 289
    Description:
    A connection to /O=ABC/OU=XYZ/CN=CONFIGURATION/CN=SERVERS/CN= MAILSRV3/CN=MICROSOFT MTA could not be opened. [MTA XFER-IN 17 26] (12)

    Microsoft article Q327004 explains this problem but that did not work for us.

    I tried putting all the mailservers on the same switch. Ping, net view commands work fine. I tried Rpings also.

    Please help. This is very urgent.

All Comments

  • Author
    Replies
    • #3376009

      Reply To: RPC errors between Exchange 5.5 and E2k

      by compgirlfhredi ·

      In reply to RPC errors between Exchange 5.5 and E2k

      In the Application event log on the Exchange 2000 Server computer, you may see some event ID message 9318?s from the message transfer agent (MTA) and event ID messages 1025?s from the MSExchangeIS private information store after you apply the changes described in Q316886. These event ID messages are warnings that may be due to Name Resolution failure using cached DNS naming information in Active Directory. These event ID messages are typically removed in three to six days. Some customers have reported that they removed these warnings more quickly by rebooting their Global Catalog Servers.
      If necessary, use Network Monitor to capture network traces, then view these traces from Network Monitor for any network issue.
      Occurs when Exchange server is unable to locate another Exchange server on the network. I have received both 9318 and 9322 when one of the servers is offline or when using dual-homed Exchange servers and Netbios over TCP/IP. Problem on dual-homed exchange servers resolved by adding specific interfaces to be used by each server to each Exchange server’s HOST and LMHOST file. See Q266312, Q303156, Q191594 and Q279537.

      • #3376008

        Reply To: RPC errors between Exchange 5.5 and E2k

        by compgirlfhredi ·

        In reply to Reply To: RPC errors between Exchange 5.5 and E2k

        Turn off the NAT service. For Exchange Server computer or clusters that are connected with site connectors, create an X400 connector, and then configure the address. This can occur if the network binding that the MTA needs to use is not the first binding available

      • #3376007

        Reply To: RPC errors between Exchange 5.5 and E2k

        by compgirlfhredi ·

        In reply to Reply To: RPC errors between Exchange 5.5 and E2k

        I received this error in conjuntion with error 9318. It looks as though there is a problem with the DNS on the Server in the message “SERVERS/CN=EFJ-DMZ-00/”. The fix to this problem appears to be the same as 9318, which is to make sure your secondary name server is a legitimate DNS server. If not remove it. After doing this both error messages (9318, and 289) disappeared.The MSExchange MTA service was had stopped on the E2k server. Started service and errors ended.

        This issue can occur as a result of poor network quality. See Q257727, Q157630 for details.
        Also, as per Q169716, in order for the MTAs to communicate successfully via a configured connector, each connector involved must be configured for a connection schedule other than “Never”. The Schedule tab on the connector’s property page provides control over when the connector is available.
        Q196381 indicates that this message can occur when the X400 connector has to pass through a firewall to reach the remote site.

    • #3375796

      Reply To: RPC errors between Exchange 5.5 and E2k

      by ssvkumar ·

      In reply to RPC errors between Exchange 5.5 and E2k

      Hi,

      RPC errors are common when MTA’s are not able to communicate within themselves.You may have to look at this problem at a different level.

      1).Since you said you are installing the M3 & M4 in the same site, i don’t think so there is a requirement of any connector with E5.5(if at all you are configuring these into different site).Assuming you are installing these in the same site, RPC errors can be possible with a mis-configured DNS at W2K level.(none of the messages will be sent out from E2K server without proper DNS settings)

      ****************

      If you have installed the E2K into different site, then better go for a “Inter office replication” connector which is much more easier for sharing GAB and can also transmit messages between E5.5 & E2K.

      After Interoffice connector you may also have to configure any of the MTA transport for sending/receiving messages.

      All the best

Viewing 1 reply thread