Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

Exchange server 2013 in Windows server 2012 VM
It was working fine then start the issue.
Firewall is managed externally and the last report said:
"I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
Can you verify that the mail server is set up so as to allow port 25? "
Today I was able to telnet the server from home: successfully 
220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS
250-AUTH NTLM 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 XRDST
Also the receive - send connectors seems ok
Mx record point to Microsoft protection:
dualtemp-com.mail.protection.outlook.com.
Again, OWA is able to access and send/receive emails internal but never external even no bounceback  just it never arrive.
Help me please. This is my first admin chaos...

Hi,
Is there any update with your issue?
If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
For more information about Exchange 2013 mail flow, here is a blog for your reference.
Exchange 2013 Mail Flow Demystified…Hopefully
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange Server 2013 cannot connect to Shell getting error Message

    New-PSSession : ******* Connecting to remote server ki-edm-vsrv-01 failed with the following error message :
    [************,TimeStamp=2014-03-18 3:05:46 PM] Access is
    denied. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : -2144108173,PSSessionOpenFailed

    It will be nice if you provide more info:
    What version of Exchange 2013 are we talking about - RTM, CU1, CU2, CU3 or SP1
    Is this a CAS, MBX or multirole server
    Did you remove the default Exchange self-signed certificate
    Are you trying to connect locally or remotely
    Step by Step Screencasts and Video Tutorials

  • Exchange Server 2013 - Lab setup with internal emails only

    Hi,
    I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
    go over the internet. 
    I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
    Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
    Regards,
    Nithin

    Hi,
    You need not to configure send/receive connectors for internal email.
    The following article for your reference:
    http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
    Default Receive connectors created during setup
    Certain Receive connectors are created by default when you install the Mailbox server role.
    Default Receive connectors created on a Mailbox server running the Transport service
    When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
    These connectors are the following:
    Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
    Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
    Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
    mentioned, their TransportRole value is HubTransport.
    To view the default Receive connectors and their parameter values, you can use the
    Get-ReceiveConnector cmdlet.
    Default Receive connectors created on a Front End Transport server
    During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
    connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
    Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
    Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
    Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
    In a typical installation, no additional Receive connectors are required.
    Niko Cheng
    TechNet Community Support

  • If the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

    if the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

    thanks for your reply!
      what's protection software can use for exchange server 2013?
    Hi,
    Most (if not all) of the bigger vendors has a product that supports Exchange 2013, so look them up.
    Exchange 2013 has some Anti-Spam and Anti-Malware Protection functionality that you can read about here:
    http://technet.microsoft.com/en-us/library/jj150481(v=exchg.150).aspx
    Martina Miskovic

  • Configuring Multiple domain Email addresses in Exchange server 2013 for Send/Receive

    I've setup an exchange server 2013 , I have an requirement to setup email addresses for multiple domain account.
    For example - My primary email addresses - [email protected] however i need to setup multiple domain email account for single AD user.
    Example
    [email protected]
    [email protected]
    [email protected]
    I was able to setup account to receive email from different users to single mailbox users however how can i send mails from other domains email address apart from primary domain email 
    Thank you
    Benhur

    Hello,
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.
    Cara Chen
    TechNet Community Support

  • Exchange Server 2013: no send/receive after failed CU1- CU2 and machine restore

    Hi!
    For several reasons, I decided to fully restore my Exchange Server 2013 machine today.
    The machine is virtualized on Hyper-V.
    I rebooted the server and recovered from backup and Exchange seems to be working fine. However, I cannot receive or send mail. If I try to send a message it goes to the "drafts" folder. OWA and EMC is working. I can not send mail between interna mailboxes
    either. Outlook says disconnected.
    When running the Exhchange Connectivity Analyzer, I get the following:
    - Receive: Connection was successful but no banner was received.
    - Send: Successfull. However when trying to send mail to external mailbox it does not reach that mailbox.
    Mailflow was working perfectly at the time of the backup.
    Help is much appreciated!
    UPDATE 1: When telnet on local server i get SMTP banner. But not on other computers in same subnet.

    OK. After fiddeling around in ADSIedit and trying to rebuild my Exchange environment I ended ut breaking it completely.
    I then restored both my DC (Exchange schema CU2) and my EX (Exchange schema CU1). Scema Versions where the inconsistent as stated.
    Then I uninstalled the KB2874216 successfully. After that i tried to Upgrade Exchange to CU2. The Upgrade failed at Mailbox Role: Mailbox Service With error Message:
    The following error was generated when "$error.Clear();
              if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
                if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
                  $sysMbx = $null;
                  $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
                  $dispname = "Microsoft Exchange";
                  $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0)
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if ($dbs.Length -ne 0)
                      $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                      if ($arbUsers.Length -ne 0)
                        $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
                  else
                    if ($mbxs[0].DisplayName -ne $dispname )
                       set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
                    $sysMbx = $mbxs[0];
                  # Set the Organization Capabilities needed for this mailbox
                  if ($sysMbx -ne $null)
                      Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                      set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;
                      # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
                      # This can be remove after BUG(O15#2555914) is fixed.
                      if ($sysMbx.RetentionPolicy -eq $null )
                         $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
                         set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
                  else
                    Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
                else
                  write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox. Property Name: Database".
    Seems the problem was corrupted arbitrary system mailboxes from previous Exchange 2010 to Exchange 2013 migration.
    The solution for me was to restore the corrupted arbitrary mailboxes using this
    LINK. It is for 2010 but Works on 2013.
    I am now currently on Exchange CU2 on both my EX server and on my DC. Now I have to check mail flow and will report back.

  • Exchange server 2013 mail send and received problem

    Hi Support,
    I have Install Exchange server 2013 and create mail box and local send received locally but days back i have not able to mail send and received. what setting are required for user mail send and received locally. and how to create mx and txt record for my
    domain.

    Hi,
    According to your description, I know that the Exchange server can send/receive internally at beginning, however doesn’t work now. Please correct me if there is anything misunderstand.
    Great checklist from S.Nithyanandham. Additionally, how about sending/receiving via OWA? And any error messages when can’t send and receive?
    Please make sure the Message Tracking has been enabled and run following command to output track log and check detail information:
    Get-MessageTrackingLog |FL > "c:\Track Search.txt"
    For more information about Message Tracking logs, please refer to below article:
    http://technet.microsoft.com/en-us/library/bb124926
    If you want to communicate externally, you need to contact ISP to register DNS MX record.
    Best Regards,
    Allen Wang

  • Exchange server 2013 send and received issue

    Hi Support,
    I have install Exchange Server 2013 with server 2012 ( my domain not resisted but mail send & received in local for practice then live ) but few days back some changes in dns and ecp and mail stop sending and receiving. how to verify my exchange server
    2013 working fine. Please give the step check perpoes.     

    dear Pardeep, you said it was working fine then you did some DNS changes..
    i would suggest you best troubleshooting step is to go to exrca.com and perform the tests and from there we take it up.
    Secondly you can verify your config from the below link.
    http://www.techieshelp.com/exchange-2013-step-by-step-configuration/        
    in DNS you need to make sure you have atleast MX and A record done for your server having email services installed.
    for ECP... i would we would take this later lets check the mail sending and receiving first. use the above links
    MARK AS USEFUL/ANSWER IF IT DID
    Thanks
    Happiness Always
    Jatin

  • Internal NAV2013 to relay email externaly through our internal exchange server 2013

    ello,
    We are using NAV 2013 to externally relay email outside and inside through our in house Exchange server 2013.
    I created a new Frontend connected with "TYPE" Custom and selected specific ip to configure relay through exchange server.
    Once created the Receive connectors I want only Anonymous permission to be set under permission group and not exchange users as this is allowing external 3rd party exchange server to relay emails through our exchange server.
    When i edit the properties of the exchange server to uncheck Exchange Server it gives me an error
    "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative."
    My motive is that I want to allow only the NAV2013 to relay emails through our exchange and no other exchange server or any other application for security reasons.
    Once i created a Receive Connectors bydefault TLS is selected and then i put a tick mark on Anonymous but as soon as i save i get error "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter
    to a value of ExternalAuthoritative." and it doesn't let me save unless i select Exchange Server
    I have followed the same link that you provided me.
    There is another problem as well, I have restricted a distribution group from receiving email from external to the organisation but as soon as i created this relay connectors this group starts receiving email external to the organisation which is very strange.
    I tested by disabling the relay connector and then sending email from gmail and then i get a bounce in gmail and the DG doesn't receive email but as soon as I enable relay connector the distribution group starts receiving email.
    I have also recreated the connector as well but still the same issue.
    Please help

    Hi,
    Please double check whether the "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative" is an error, we can safely ignore it if it
    is only a warning message. 
    I found a related KB for your reference even if the Exchange server version is mismatched.
    Exchange 2010: Get-ReceiveConnector warns that an Exchange 2007 connector is corrupted and in an inconsistent state
    http://support.microsoft.com/kb/2291884
    Please double confirm the following setting:
    Authentication tab: Checked TLS and Externally Secured.
    Permission Groups: Anonymous users, Exchange Servers
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange Server 2013 SP1 - Internal Email Flow slowness

    Hi Fellows,
    I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
    I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
    When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
    Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
    Header analysis shows the message exchange between mailbox servers is taking time. any clue?
    Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
    Network communication, Storage performance, Server performance are all as good as we love to.
    Thanks.
    J.A

    Hello,
    When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
    Cara Chen
    TechNet Community Support

  • Help with Moving Emails from Exchange Server 2013

    Hi Team,
    Help, I need a solution on how to copy incoming and outgoing emails together with their attachments and was hoping someone could help with a solution I need to find for this problem.
    1) I have a need to copy all incoming and outgoing emails & attachments from Exchange Server 2013 mailboxes on a daily basis, so they can be archived into an external 3rd party database overnight.
    I believe that the first step is that I can set up another Exchange mailbox, through Journaling to receive these emails. 
    Is there any way that these emails can then be moved direct from the Journaling mailbox that I have created, to a shared folder on the network? If so what format would they be sent out as e.g. .msg, .ems and what is the process?
    Failing that, could they be sent to an Outlook client (not another Exchange mailbox) on the network and stored in a .pst file? (I have a program that will export them from .pst)
    I would really appreciate any assistance that you can provide in this matter.
    Regards, Greg.

    Hi,
    You can set auto-forward on journaling mailbox and auto-forward emails to another mailbox. Why don’t directly archive the emails from the journaling mailbox “an external
    3rd party database”.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Exchange Server 2013 internal and external DNS records

    I recently installed Exchange Server 2013 and I've register a pubic ip too for exchange server. How can I create internal DNS as well MX record for my Exchange server to send and receive internet mails. It's my first time configuring exchange for a organization.
    registered domain name=====np.bbcmediaaction.org
    public ip=====202.166.212.221

    Hi,
    For external mail flow, we need the following DNS records: MX records for the domain part of the external recipient, A records for the destination messaging servers. For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/bb676467(v=exchg.150).aspx
    Additionally, to ensure external mail flow works well, we also need to configure send connector.
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx   
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange Server 2013 - Send E-Mail

    I am very new to Exchange Server.  I managed to install 2013 and I can send e-mail on-premises with no problem.  When I follow what I believed to be the step-by-step instructions for connecting a Send Connector so I could send e-mail on-line I
    can't get it to work.  I set it up and try an e-mail and the e-mail just sits in the drafts folder forever (as in 2 days now).  I can't send any other e-mail now either.  They just sit in the drafts folder.
    Finally I try to delete the on-line draft message and it won't delete.  I delete the Send Connector and the draft finally will delete after nearly 10 hours.  I can again send on-premises e-mail but nothing else.
    Can someone be kind enough to step an old man through the exact process needed in order to set up and send and receive e-mail to the internet? 
    Greatly appreciated. 
    dave

    It looks to me like I'm going to have to give up.  I understand a lot of what you post, but I can't get the same results. (see my attachment).  I wish I had some step-by-step tutorials available that I could learn from instead of trying to
    fit bits and pieces of a puzzle together without having all of the pieces.
    Looking at my previous post.  Did I set up the DNS addresses properly on my Domain Server?  Am I accessing them correctly from the Exchange Server?  I don't know.
    Attached is a Word document that shows what I get when I follow your above instructions.  I can do the NSLOOKUP, set type=MX and then Rowley.xyz, but then nothing else is the same.  If I can't get the same results you do, then I can't go anywhere.
    Everyone had to start at the beginning and learn, but I'm totally lost now as to what would be the starting point and each subsequent step.
    Thank you for your assistance.  If I could get the answers to the DNS questions above I will try again from scratch.
    I realize it's not you, it's me, someone who is trying to learn something new without a "guide book" to work from and without a "mentor/instructor".   I have purchased and read several books on Server 2012 and Exchange Server 2013,
    just to get this far, but no further.
    dave

  • CANNOT ACCES EXCHANGE ADMIN CENTER (ECP) ON EXCHANGE SERVER 2013. GOT HTTP 500 INTERNAL SERVER ERROR

    HI, I just installed Exchange server 2013 Standar SP1 on a windows server 2012.  I have 3 servers one is a Domain Controller, the other one has the MBX role, and the last one the CAS role,  first i installed the MBX and after the CAS role, i passed
    prerequisite check without any issue.  However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp
    I got HTTP 500 Internal Server Error saying  "This website cannot display the page.  Most likely causes: 1. The website is under maintenance. 2. The website has a programming error."   I tried access ECP at https://localhost/ecp and
    I got the same problem.  Under either cases I was able to see the logon page of  ECP and I was able to enter my credential (e.g. domain\user name, password).  However I got HTTP 500 Internal Server Error at the next page.
    I appreciate your help, on my case.

    Hi,
    The link that Jatin points to should be this.
    https://social.technet.microsoft.com/Forums/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients
    Please view the Application Pool to check whether the version of .NET Framework is 4.0 and try the following command.
    %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i.
    If this does not help then please check if there is any warnings or errors in Event Log and take your time to post them for my further troubleshooting.
    Thanks.

  • Exchange Server 2013 POP3 Service on CAS cannot after Upgrade to SP1

    Exchange Server 2013 POP3 Service on CAS cannot after Upgrade to SP1
    When I manual start MSExchangepop3 Service on CAS It show "The Microsoft Exchange POP3 Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
    In event log show POP3 EventID 1018 , 1019 , 1036
    It said like this blinding already use (0.0.0.0)
    The point is "IF I SET BINDING FOR 995 , MSEXCHANGE POP3 Service will automatic stop"
    Does anyone face this issue please?
    Thank you

    You could check what (if anything) else is running on that port.
    From a command prompt, type netstat -ano | find 995
    This will give you the Process Identifier (PID) for the process that is running on port 995. Then you can open Task Manager, add PID as an additional column, and find out what that process is.
    Hope that helps.

Maybe you are looking for