Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 250
  • Last Modified:

Exchange 2013 - cannot send or receive mail. QUE only says submission ...

Everything has been working fine since I REDID the server from an intial intstallation. However, as of 10AM this morning, nothing is send or receive. I have rebooted three times. Compared it to another client's Exchange 2013.

This is one of the errors that keeps coming up:
Inbound authentication failed with error UnexpectedExchangeAuthBlob for Receive connector

I try to stop and restart the transport service, and the service will not start again once stopped.
0
niccross
Asked:
niccross
  • 5
  • 3
  • 2
1 Solution
 
niccrossAuthor Commented:
NO VM and no two servers...everything on single server.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
everything on single server

is this on a domain controller?
0
 
niccrossAuthor Commented:
Yes it is on a domain controller. I got the Exchange server to send and receive but it only lasted 2 hours. I finally got it now to send to external. I have it able to send and receive internally.

Externally .. different story. External receiving does not work.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Seth SimmonsSr. Systems AdministratorCommented:
is the connection from the outside making it to the exchange server?
from the outside do you get a response on port 25 through telnet?

you can also try the remote connectivity analyzer

https://testconnectivity.microsoft.com/¿
0
 
niccrossAuthor Commented:
Telnet I get a response from just fine. Remote Connectivity works. no bounce backs.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
ok...what happens when you send from something like a google or hotmail account to your server?  is it returned or delivered or seemingly go off in a black hole?
0
 
niccrossAuthor Commented:
black hole
0
 
Simon Butler (Sembee)ConsultantCommented:
Have you got anonymous enabled on the default receive connector?
Did you install Exchange 2013 SP1? If so there is a known issue with transport, but if internal email is working then it isn't that.
It is something with your receive connectors.

Simon.
0
 
niccrossAuthor Commented:
It's CU3 not SP1. I even created new connectors. I thought it was DNS but not and then I tried the cert but no
0
 
Simon Butler (Sembee)ConsultantCommented:
If you created new connectors then if it isn't done correctly you will get the results you are seeing.
Check this blog posting for more details on what you may have done.

http://exchangemaster.wordpress.com/2014/01/24/incorrectly-adding-new-receive-connector-breaks-exchange-2013-transport/

Simon.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now