none
Exchange 2003 Intra-Org Server "Unreachable" RRS feed

  • Question

  • My company opened up a new remote site and I have installed infrastructure services, such as DC and Exch.

    We have three other remote sites, all running the same OS and Exchange versions.

    I've setup the new server identically to the others, yet when I look at the "Status" of the servers from the remote site, they are all "Unreachable", when I look at the "Status" from the other servers, only the new server is "Unreachable".

    All remote site are connected to HQ via VPN over the Internet. As far as I can tell, and from what our network teams says, there is no "blockage" on the connection.

    I need some help diagnosing this issue, or being able to point the finger at our network team will work too :)

    I can telnet from and to all sites on port 25, can hit the DC's on 386(I think it was)

    Friday, June 10, 2011 8:10 PM

Answers

  • Hi Wmikef,

    Do you mean that you could not find the new DC and exchange server in the ADUC and the ADSS?
    If so, how about to use the DCdiag tool to get some information?
    And then check the DC replication properly.
    If you use the EXBPA tool, are all the exchange servers including the new exchange server shows work well? Please confirm it.
    If all are right, please retrieve some session on the new server using the NETMON to analyze the issue.
    Confirm again all the windows firewall, and other third party firewall configured well.
    Check the mailflow setting on the new exchange server, what is the connector you configured on the hub server?
    Then we could narrow down the issue.

    Regards!
    Gavin 
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    tngfb@microsoft.com
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Gavin-Zhang Tuesday, July 5, 2011 9:27 AM
    Friday, June 17, 2011 4:53 AM

All replies

  • 1. There's a number of ports that I'd check and see if they are open (relevant ones).  You can use portquery to test. - http://technet.microsoft.com/en-us/library/bb124075(EXCHG.65).aspx & http://support.microsoft.com/kb/555381

    2. I'd also run the exchBPA which would provide some useful information.

    3. Think you were refering to port 389


    Sukh
    Friday, June 10, 2011 11:04 PM
  • Hi Wmikef,

    Any update for your issue?
    Above gave some good information.
    Please check the needed ports are achieved.

    Regards!
    Gavin
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    tngfb@microsoft.com
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, June 13, 2011 10:01 AM
  • I  had checked the first reference already, only about 1/2 of the ports would be used in our environment.

    We don't use POP3 or IMAP4...the one caveat is port 102 X.400 which I beleive is used in Excahnge 5.5

    As foir the second reference, the firwall service is truned off by default... I did telnet on all ports and was successful with the exception of 35211/2 which is AD replication, which I would not expect to work from Exchange server to DC...

    Port 389 is open to the local DC and as well as the remote DC.

    BPA does not show anything out of the ordinary

    Monday, June 13, 2011 7:38 PM
  • Next step is to run a network trace from one of sites to the new site.

    Monday, June 13, 2011 7:50 PM
  • 1. Have you  actually got a mailflow issue or is it just the status you are worried about?

    2. I've seen issues whereby status has been show as yours but all exch communication is working fine,


    Sukh
    Monday, June 13, 2011 8:01 PM
  • There is actually a flow issue, it does seem to flow, but there is an exceptionally long delay.

    It seems to try to use the "Org"  tranfer, then falls back to the routing connector

    Monday, June 13, 2011 10:16 PM
  • I was hoping to avoid this, but it's looking like there is not other option.

    Just not very sure of what I would be looking for in the trace (netmon capture)

    Monday, June 13, 2011 10:17 PM
  • Hi Wmikef,

    Do you mean that you could not find the new DC and exchange server in the ADUC and the ADSS?
    If so, how about to use the DCdiag tool to get some information?
    And then check the DC replication properly.
    If you use the EXBPA tool, are all the exchange servers including the new exchange server shows work well? Please confirm it.
    If all are right, please retrieve some session on the new server using the NETMON to analyze the issue.
    Confirm again all the windows firewall, and other third party firewall configured well.
    Check the mailflow setting on the new exchange server, what is the connector you configured on the hub server?
    Then we could narrow down the issue.

    Regards!
    Gavin 
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    tngfb@microsoft.com
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Gavin-Zhang Tuesday, July 5, 2011 9:27 AM
    Friday, June 17, 2011 4:53 AM
  • Hi wmikef,

    Any update for your issue?

    Regards!
    Gavin
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    tngfb@microsoft.com
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, June 20, 2011 5:06 AM