locked
Exchange 2016 no mail in or out or internally RRS feed

  • Question

  • Hi All

    New to exchange 2016 on premise.   Have installed windows 2012 R2 and exchange 2016.

    Have created the users mailboxes and AD accounts via the EMC, connected outlook 2016 clients to those mailboxes.

    Cannot send email between mailboxes and cannot send or receive mail from external to the organisation.

    With exchange 2016, do you need an edge transport server as well as a mailbox server?  thought i found an article that said i didnt.

    Not sure what i'm doing wrong.

    Any help appreciated.

    Cheers

    Dave

    Monday, February 13, 2017 10:20 AM

All replies

  • Hi Dave,

    Have you configured Send connector?

    Have you published MX record with public DNS registrar?

    What is the NDR that you get 


    • Edited by Akabe Monday, February 13, 2017 10:26 AM
    Monday, February 13, 2017 10:23 AM
  • Hey Akabe

    I have confirgured the send connector, seems pretty simple, really only three entries to make.

    The MX record is published as i'm migrating this company from exchange 2003 on an SBS server.

    I'm getting no NDRs at all.  go through message trace nothing, check mailboxes via outlook and OWA, nothing.

    its strange.

    Dave

    Monday, February 13, 2017 10:32 AM
  • Interesting.

    Do you see the MSEXCH attributes in user's AD accounts via Attribute editor?

    Are AD accounts enabled?

    Is internal and external mail flow not working?

    Get-mailboxdatabasecopystatus?

    Also, run

    Test-Mailflow Mailbox1 -TargetMailboxServer Mailbox2
    

    Also check if Exchange services i.e Transport service/Mailbox transport submission/deleivery service etc are enabled

    run Get-service *Exchange* in the shell

    • Edited by Akabe Monday, February 13, 2017 10:46 AM
    Monday, February 13, 2017 10:37 AM
  • Get-mailboxdatabasecopystatus reports mounted and healthy

    I dont see MSEXCH attributes in users AD accounts, but those tab disappear with Exchange 2007 didnt they?

    The AD users were created through the exchange ECP at the same time the mailboxes were created.

    Monday, February 13, 2017 10:45 AM
  • I have added few more details in my last comment 

    When you enable the mailbox, the MSEXCH attributes get stamped on user mailboxes

    Get-mailbox -identity "Affected mailbox" | fl 

    Get-mailbox -identity "Affected mailbox" | fl  Reci*

    ?

    Have you added the custom domain as an authoritative domain in Exchange ?

    get-accepteddomain

    Also run

    Get-Queue -Filter {MessageCount -gt 100}
    



    • Edited by Akabe Monday, February 13, 2017 10:52 AM Added info
    Monday, February 13, 2017 10:50 AM
  • Get-mailbox -identity "Affected mailbox" | fl

    this spewed out a lot of stuff.

    Get-mailbox -identity "Affected mailbox" | fl Reci*

    result

    RecipientLimits      : Unlimited
    RecipientType        : UserMailbox
    RecipientTypeDetails : UserMailbox

    Get-Queue -Filter {MessageCount -gt 100}

    Just returns back to the powershell prompt with no results.

    Monday, February 13, 2017 11:08 AM
  • Ok

    1. You can simply run Get-queue to see if the emails are stuck in the queue?

    2. The recipienttypedetails seems to be correct -> It is user mailbox 

    3. What about get-accepteddomain ? Is your custom domain added as an authoritative domain - Just wanted to make sure 

    4. What about running the below command:-

    Test-Mailflow Mailbox1 -TargetMailboxServer Mailbox2

    5. Run, Get-service *Exchange* in the shell and see if all the services are up and running

    Monday, February 13, 2017 11:15 AM
  • correct internal and external mail flow not working.

    the test-mailflow command, i couldnt get that to run

    services are running.

    Monday, February 13, 2017 11:16 AM
  • 1.  Looks empty

    Identity                   DeliveryType Status MessageCount Velocity RiskLevel OutboundIPPool NextHopDomain
    --------                   ------------ ------ ------------ -------- --------- -------------- -------------
    servername\Submission      Undefined    Ready  0            0        Normal    0              Submission

    3.

    Monday, February 13, 2017 11:18 AM
  • 3. looks good, the FQDN is auth and default.

    4.

    Monday, February 13, 2017 11:19 AM
  • sorry keyboard issues.

    4. can not get that command to run

    5. yes all services are running

    Monday, February 13, 2017 11:20 AM
  • 1. Test-ServiceHealth | FT Role,RequiredServicesRunning -AutoSize  (What does this command show)

    2.  Check the Network ports for Exch 2016 Mail flow to work (Refer below article):-

    https://technet.microsoft.com/en-us/library/bb331973(v=exchg.160).aspx

    3. Run Get-transportservice | fl *DNS* in the exchange management shell

    4. Also check below log file:-

    C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\Connectivity

    5. For test-mailflow use below article:-

    https://practical365.com/exchange-server/exchange-2013-test-mail-flow/


    • Edited by Akabe Monday, February 13, 2017 11:31 AM
    Monday, February 13, 2017 11:30 AM
  • Apart from above, can you verify

    What happens when two internal users send emails to each other? Are emails stuck in Drafts folder via Outlook and OWA both?

    Monday, February 13, 2017 11:52 AM
  • 1. required services all running

    2. ok went through that doc, a little confusing but i think I understand.  I cut the receive connectors back to the client frontend connector, using port 25 and accepting on all IPs and all IPs.

    3.  ExternalDNSAdapterEnabled : True
    ExternalDNSAdapterGuid    : 00000000-0000-0000-0000-000000000000
    ExternalDNSProtocolOption : Any
    ExternalDNSServers        : {}
    InternalDNSAdapterEnabled : True
    InternalDNSAdapterGuid    : 00000000-0000-0000-0000-000000000000
    InternalDNSProtocolOption : Any
    InternalDNSServers        : {}
    DnsLogMaxAge              : 7.00:00:00
    DnsLogMaxDirectorySize    : 100 MB (104,857,600 bytes)
    DnsLogMaxFileSize         : 10 MB (10,485,760 bytes)
    DnsLogPath                :
    DnsLogEnabled             : False
                                

    4.  hasent been a log since late Jan, probably the last time the server was rebooted :)

    5.  these commands seem to hang up the PS, and do nothing

    Monday, February 13, 2017 11:56 AM
  • If you have removed default receive connector then that is your issue. Recreating the connector should help you. Reboot the server and then run the command via Exchange shell 

    Set up receive connector with below artcile

    - https://technet.microsoft.com/en-us/library/aa996395%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396

    • Edited by Akabe Monday, February 13, 2017 12:01 PM
    • Proposed as answer by ccccsadasd Monday, May 27, 2019 1:53 AM
    Monday, February 13, 2017 11:59 AM
  • i just disabled it.  testing. but it hasnt helped so i can enable it again.
    Monday, February 13, 2017 12:02 PM
  • what is the difference between the client frontend, client proxy, default frontend, default and outbound proxy frontend?
    Monday, February 13, 2017 12:04 PM
  • Look at below article to get clarity:-

    - https://technet.microsoft.com/en-us/library/aa996349%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396

    Also you need to recreate the Default receive connector that wil work on port 25 

    • Proposed as answer by David Wang_ Thursday, March 2, 2017 9:00 AM
    Monday, February 13, 2017 12:06 PM
  • thanks will read.  recreated, or at least re enabled the default receive connector.
    Monday, February 13, 2017 12:10 PM
  • You welcome.

    You can then test the mailbox internal and external to see if its working. See if emails are getting stuck in drafts folder. Else you should be good 

    Do share your final output with us 


    Monday, February 13, 2017 12:15 PM
  • I did notice emails getting stuck in the drafts folder.  But that was generally happening when using OWA to test sending.

    Monday, February 13, 2017 8:20 PM
  • Hi,

    "With exchange 2016, do you need an edge transport server as well as a mailbox server?"

    The Mailbox server in Exchange 2016 includes all of the server components from the Exchange 2013 Mailbox and Client Access server roles. And the edge server is not essential.

    In addition to above suggestions (recreate the receive connector), I suggest you refer to the following link to create a new send connector to test:

    https://technet.microsoft.com/en-us/library/jj657457(v=exchg.160).aspx


    Best Regards,
    David Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by David Wang_ Tuesday, February 21, 2017 1:59 AM
    Tuesday, February 14, 2017 2:35 AM
  • I did notice emails getting stuck in the drafts folder.  But that was generally happening when using OWA to test sending.

    If that is the case, its all subjected to Receive connector 

    Internal mail will flow  through the Transport service on a Mailbox server in one of the following ways:

    • Through a Receive connector.

    • From the Pickup directory or the Replay directory.

    • From the Mailbox Transport Submission service.

    • Through agent submission.

    Hence as suggested before by recreating the receive connector (default) the issue should be fixed 

    Let us know if you need further help.

    I hope by now the issue would be fixed 

    • Proposed as answer by David Wang_ Tuesday, February 21, 2017 1:59 AM
    Tuesday, February 14, 2017 1:07 PM
  • Hello aintnoguru,

    I hope by now the issue would be resolved. Let us know if you need further assistance 


    Regards, Abrar Kaberi | MCSA Office 365 | MCSA Exchange server 2010 with 2008 Active Directory Configuration | Red Hat Certified Engineer | https://www.linkedin.com/in/abrar-kaberi-46a483102/

    Monday, February 20, 2017 8:49 AM
  • If the reply above is helpful to you, please also mark it as answers so that someone who has similar issue could find the solution as soon as possible.

    Thank you for understanding.

    Best Regards,
    David Wang
    TechNet Community Support


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 2, 2017 7:23 AM
  • Thank you very much!! 100% that was the issue in my case

    Monday, May 27, 2019 1:53 AM
  • I had the same issue with Exchange 2019 (no internal mailflow), but non of the above solutions fit for me.

    This worked for me:

    I had to remove the second (Alternate) DNS in my NIC configuration on the Exchange server, the primary (Preferred) should the IP of the DNS server. Also configured DNS lookup, select the Custom settings then add the local DNS server IP even if it is already there with your NIC settings.

    After that, restart Transport and Transport Frontend. This also fixed my external mail flow!

     


    • Edited by Nitwit2020 Wednesday, December 11, 2019 1:36 PM
    Wednesday, December 11, 2019 1:35 PM