Recursos para Profesionales de TI > Página principal de foros > Exchange Server 2010 > Not receiving internet e-mail on Exchange Server 2010

Respondida Not receiving internet e-mail on Exchange Server 2010

  • domingo, 13 de febrero de 2011 5:47
     
     

    Hello;

    Recently I installed an Exchange Server 2010 with Edge Transport role and then an Exchange 2010 server with Hub Transport, Mailbox, and Client access.  I used Edge Sync file to connect the two.  I set up a Receive connector on the Edge Transport role before I did this.  On the Hub Transport role on the second server I set up a Send connector but I cannot receive or send e-mail with it.

    I did make sure that my Domain provider had redirected my e-mail redirecting the a record to the 75.xxx.xxx.xxx Static IP address that I'm using.  I also set my Mx record to go to mail.xxxx.com and pinged it to make sure it was resolving the domain name to the correct IP address.  Mail should be going here but I'm not getting anything. 

    What have I missed? Can anyone help me?

    Thanks,

     


    David Kellett

Respuestas

Todas las respuestas

  • domingo, 13 de febrero de 2011 7:55
     
     
    make sure that Anonymous has been selected in the Permission groups on your Edge Server's receive connector.
    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • domingo, 13 de febrero de 2011 15:25
     
     

    It is and I am still not receiving any e-mails.

    Thank you,

     


    David Kellett
  • domingo, 13 de febrero de 2011 21:20
     
     
    Do the Exchange message logs show anything received?  Does the firewall have anything about SMTP connections from the internet being denied?  is port 50636 open for the Edgesync with HT? 
  • domingo, 13 de febrero de 2011 22:53
     
     

    The Exchange Message logs show activity in the connection logs only.  I don't see anything else.  The SMTP is not blocked by the firewall.  How do I check to see if port 50636 is open?

    Thanks,

     


    David Kellett
  • domingo, 13 de febrero de 2011 23:08
     
     
    A- First check:
    open
    select Internet E-mail test
    select Inbound SMTP E-mail
    please Copy and paste the result here
    B-Second Check
     Use the EMC to enable or disable protocol logging on connectors
    1. Perform one of the following steps:
      • To modify an existing Receive connector on an Edge Transport server, in the console tree, select Edge Transport, and then in the work pane, click the Receive Connectors tab.
      • To modify an existing Receive connector on a Hub Transport server, expand Server Configuration in the console tree, and select Hub Transport. In the result pane, select the server that has the Receive connector that you want to modify, and then click the Receive Connectors tab.
    2. In the work pane, select the Receive connector to modify.
    3. Under the name of the Receive connector in the action pane, click Properties to open the Properties page.
    4. Click the General tab and use the drop-down box next to Protocol logging level to enable or disable protocol logging. None disables protocol logging, and Verbose enables protocol logging.
    5. After you make your protocol logging selection, click Apply to save changes and remain on the Properties page, or click OK to save changes and exit the Properties page.

    then run this command to change the location of the protocol log path

    Set-TransportServer Edgeservername -ReceiveProtocolLogPath "C:\Receive SMTP Log"

    try to send E-mail for yourself

    Please copy and paste the log file contetnts here

     

     


    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • lunes, 14 de febrero de 2011 4:15
     
     

    Mohamed;

    1.) Results as follows:

    Testing inbound SMTP mail flow for domain davidk@gokicomputing.com.
     ExRCA failed to test inbound SMTP mail flow.
     Test Steps
     Attempting to retrieve DNS MX records for domain gokicomputing.com.
     ExRCA wasn't able to retrieve MX records from DNS.
      Tell me more about this issue and how to resolve it
     Additional Details
     No MX records were found in DNS for SMTP domain gokicomputing.com.

    2.) Followed those instructions but the folder is empty.

    Thanks,

     


    David Kellett
  • lunes, 14 de febrero de 2011 7:21
     
     

    your problem is very clear and simple you don't have MX record for gokicomputing.com domain , Please contact your ISP for creating one.

     


    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • lunes, 14 de febrero de 2011 9:53
     
     

    While Mohamed is right and you need to contct your ISP to setup an MX record or 2 you can test this externally anyway and from a machine outside your network with internet connectivity create a send connector in Outlook Express or Microsoft Outlook to send email to your external IP address, you can then send some test emails to check you are recieving them, if you are then connectivity within the system is good and you will have already tested half the system.

    Just an idea...

     

    Phil

  • lunes, 14 de febrero de 2011 15:47
     
     

    Reran the first test and got the following results:

      Testing inbound SMTP mail flow for domain davidk@gokicomputing.com.
      ExRCA failed to test inbound SMTP mail flow.
     
    Test Steps
     
    Attempting to retrieve DNS MX records for domain gokicomputing.com.
      One or more MX records were successfully retrieved from DNS.
     
    Additional Details
      MX Records Host mail.gokicomputing.com, Preference 10
    Testing Mail Exchanger mail.gokicomputing.com.
      One or more SMTP tests failed for this Mail Exchanger.
     
    Test Steps
     
    Attempting to resolve the host name mail.gokicomputing.com in DNS.
      The host name resolved successfully.
     
    Additional Details
      IP addresses returned: 75.160.168.18
    Testing TCP port 25 on host mail.gokicomputing.com to ensure it's listening and open.
      The port was opened successfully.
     
    Additional Details
      Banner received: 220 mail.gokicomputing.com Microsoft ESMTP MAIL Service ready at Mon, 14 Feb 2011 08:41:27 -0700
    Attempting to send a test e-mail message to davidk@gokicomputing.com using MX mail.gokicomputing.com.
      Delivery of the test message failed.
     
    Additional Details
      The server returned status code 550 - Mailbox unavailable. The server response was: 5.7.1 Unable to relay
    Exception details:
    Message: Mailbox unavailable. The server response was: 5.7.1 Unable to relay
    Type: System.Net.Mail.SmtpFailedRecipientException
    Stack trace:
    at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception)
    at System.Net.Mail.SmtpClient.Send(MailMessage message)
    at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()


    David Kellett
  • lunes, 14 de febrero de 2011 23:21
     
     
    Have them setup your MX FQDN and IP as the lowest priority, then find out if they will provide a mail spool or find a mail spool provider online.  Then if your Exchange infrastructure or internet link is down, it will send the email to the next priority in the MX list until your systems are back online.  this will keep your system from sending NDRs if a portion goes offline. 
  • lunes, 14 de febrero de 2011 23:59
     
     

    I guess your first problem has gone , i've checked your domain and found the new created MX . 

    Your problem now is coming from the Edge server which is rejecting the incoming mail because the mailbox is not available.

     

    Run this command from your hub server

    start-edgesynchronization t

    wait for a minutesvthen run the test again and feed me back


    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • martes, 15 de febrero de 2011 0:14
     
     

    Mohamed;

    I run that command and I get the following message:


    RunspaceId     : 25536d2f-555b-4372-9766-e23ebae92771
    Result         : CouldNotConnect
    Type           : Configuration
    Name           : ENTERPRISE
    FailureDetails : The LDAP server is unavailable.
    StartUTC       : 2/15/2011 12:15:45 AM
    EndUTC         : 2/15/2011 12:15:45 AM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0

    RunspaceId     : 25536d2f-555b-4372-9766-e23ebae92771
    Result         : CouldNotConnect
    Type           : Recipients
    Name           : ENTERPRISE
    FailureDetails : The LDAP server is unavailable.
    StartUTC       : 2/15/2011 12:15:45 AM
    EndUTC         : 2/15/2011 12:15:45 AM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0

    Is this what you would expect to see?

    Thank you,

     


    David Kellett
  • martes, 15 de febrero de 2011 0:24
     
     

    yes :) 

    you have a problem with EdgeSync , please confirm if you have a firewall between your Edge and Hub Server and confirm if you opened all required ports.


    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • martes, 15 de febrero de 2011 3:39
     
     

    Mohamed;

         I do not have a firewall between the edge and hub server.  How do I check if all the ports are openned?  Which ones are required?

    Thank you,

     


    David Kellett
  • martes, 15 de febrero de 2011 17:06
     
     

    Mohamed;

    I looked up the ports and all of them seem to be open.  I've even reconfigured the Edge and Hub Transport Servers.  No luck in getting e-mail to pass through.  What can I do now?

    Thank you,

     


    David Kellett
  • miércoles, 16 de febrero de 2011 23:15
     
     
    any updates
    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • jueves, 17 de febrero de 2011 6:43
    Moderador
     
     

    Hi David,

     

    Any updates on this issue?

     

    For this issue, I suggest you follow these steps to have a try:

     

    1.       Please also confirm you have closed Windows Firewall on the Edge and Hub Server.

     

    2.       Remove the Edgesubscription.

     

    3.       Restart the Transport service on Hub and ADAM service on Edge Server.

     

    4.       Create a new Edge Subscription.

     

    5.       Run Start-EdgeSynchronization and check whether it is successful.

     

    6.       Run Test-EdgeSynchronization  and  check whether it is successful.

     

    7.       If all these are successful, restarted the Transport service on Hub and ADAM service on Edge server.

     

    8.       Check the mail flow.

     

    If the issue persists , please check the event log, and paste the related information in your next post.

     

    Here are some related documents for you:

     

    Understanding Edge Subscriptions

    http://technet.microsoft.com/en-us/library/aa997438.aspx#Process

     

    Create an Edge Subscription File on an Edge Transport Server

    http://technet.microsoft.com/en-us/library/aa997590.aspx

     

    Thanks,

     

    Evan

     

     

     


    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.
  • jueves, 17 de febrero de 2011 15:50
     
     

    Evan;

    For some reason I cannot resolve the DNS for my Exchange Server.  If I type in ping ServerName by itself it resolves just fine.  But if I type in the fqdn it says "Ping request could not find the host."  The Following is in the event log:

    Log Name:      Application
    Source:        MSExchange EdgeSync
    Date:          2/17/2011 8:51:53 AM
    Event ID:      1024
    Task Category: Topology
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      KIGIANT.KIComputing.local
    Description:
    Failed to connect to the Edge Transport server ADAM instance with exception The LDAP server is unavailable..  This could be caused by a failure to resolve the Edge Transport server name ENTERPRISE.KIComputing.local in DNS, a failure trying to connect to port 50636 on ENTERPRISE.KIComputing.local, network connectivity issues, an invalid certificate, or an expired subscription.  Verify your network and server configuration.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange EdgeSync" />
        <EventID Qualifiers="49156">1024</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-02-17T15:51:53.000Z" />
        <EventRecordID>953938</EventRecordID>
        <Channel>Application</Channel>
        <Computer>KIGIANT.KIComputing.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The LDAP server is unavailable.</Data>
        <Data>ENTERPRISE.KIComputing.local</Data>
        <Data>50636</Data>
      </EventData>
    </Event>


    David Kellett
  • jueves, 17 de febrero de 2011 16:08
     
     
    Just create a Static A host record in your internal DNS for your Edge Servers
    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • jueves, 17 de febrero de 2011 16:26
     
     

    Did that, I get the same error.  Do I have to wait a certain amount of time for this to take effect?

    Thanks,

     


    David Kellett
  • jueves, 17 de febrero de 2011 16:38
     
     

    Mohamed;

    Waiting a while did the trick.  The Edge Synchronization is working now.  I've restarted the services and will get back to you with the result.


    David Kellett
  • jueves, 17 de febrero de 2011 23:20
     
     

    Mohamed;

    The Edge Synchronization passes the tests, however, I am still not receiving any external e-mail.  How can I check what is going on now?

    Thank you,

     


    David Kellett
  • viernes, 18 de febrero de 2011 15:43
     
     

    Mohamed;

    Finally got all my e-mails from the internet to work today.  After getting the Edge Synch to work I had to redo the receive connector and allowed domains.  After they were done up right I've been receiving all of my e-mails normally.  However, I still cannot send them out on the web.  When I try to check my Edge Transport Server send connectors for either Internet or INternal e-mail I get the error: The operation couldn't be performed becuase object 'Go KI xxx Internet e-mail' couldn't be found on 'localhost'. It was running the command 'Get-SendConnector -Identity 'Go KI xxx Internet e-mail''. It's rougly the same message for the Internal Send connector as well.

    Thank you,

     


    David Kellett
    • Marcado como respuesta Moroni15 viernes, 18 de febrero de 2011 15:43
    • Desmarcado como respuesta Moroni15 viernes, 18 de febrero de 2011 20:04
    •  
  • viernes, 18 de febrero de 2011 22:13
     
     
    It seems that your Send connector has been deleted the on your Edge server by mistake , just create another one .
    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • domingo, 20 de febrero de 2011 7:51
     
     
    any updates
    MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT
  • lunes, 21 de febrero de 2011 21:47
     
     

    Mohamed;

    I posted an update last week and now it is gone.  Very disturbing.  Essentially what happened is that it gave me an error when I tried to re-install my send connectors.  It tells me that it cannot perform the operation on the Edge Server as long as there is a Synch to the hub server.

    Thanks,

     


    David Kellett
  • martes, 01 de marzo de 2011 17:19
     
     

    Mohamed;

    I haven't heard back from you.  I still cannot get the Edge Transport to alter the send connectors.  Only one e-mail account seems to be receiving e-mail.  I need help.

    Thanks,

     


    David Kellett
  • martes, 01 de marzo de 2011 18:20
     
     Respondida

    As decribed in your error the systems still sees a synch to the hub server.(this is because you allready created the file it is still on the Hub transport server.)

    Try removing it

    http://technet.microsoft.com/en-us/library/aa996865.aspx

    and then recreate it.

  • domingo, 13 de marzo de 2011 13:33
     
     

    I agree. Delete your connector and recreate a new one. Also, make sure you perform your tests with precision. Start from internal email to internal, that internal to outbound. If outbound and internal work then you have your exchange server resolving dns properly and it is doing it's job. Next reply to an outbound email and see what happens. If you don't get it, try using a test site to confirm email is working properly. I forget the name but in google i always type test email address.

     

    Also, do you have antivirus? Antivirus must be configured to allow and ignore exchange and edge. If not, it will block.

  • miércoles, 16 de marzo de 2011 6:53
     
     

    Hi All,

    However I am getting the below message,

    Delivery is delayed to these recipients or groups:
     
     
    Subject: FW: Test mail
     
    This message hasn't been delivered yet. Delivery will continue to be attempted.
     
    The server will keep trying to deliver this message for the next 1 days, 18 hours and 53 minutes. You'll be notified if the message can't be delivered by that time.
    Please help me
    Ganga