Go Premium for a chance to win a PS4. Enter to Win

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

Exchange 2013 messages getting stuck in drafts in OWA

Completely new install from Hypervisor all the way up.

VMware vSphere 5.1U1
Domain Controller VM
Exchange 2013 CAS/MAILBOX VM

Just installed Exchange 2013 and followed Microsoft's post-installation tasks, and I have not touched the receive connectors at all.  I logged into OWA and tried to send an email to my gmail account and the item gets stuck in drafts folder.  I went into ECP and set the DNS servers to use my DC to resolve internal addresses (10.8.0.10) and set the external DNS server to google (8.8.8.8).  This didn't work.  I then set the IP in HOSTS files   10.8.0.15    exch1.domain.local.  This also failed.  Ran Test-mailflow and that failed.  I'm lost.
0
Mike
Asked:
Mike
  • 4
  • 2
  • 2
  • +1
4 Solutions
 
amclaughlin01Commented:
I would check the Outlook client and see if it shows as being connected or disconnected?

Are they able to send internally?

Are you using OWA?  If so, do you get the same results?

This might help narrow down where the problem is stemming from.
0
 
amclaughlin01Commented:
Another thing.  Have you watched the Exchange queue viewer to see if the message is every reaching the queue once you hit send?
0
 
MikeIT ManagerAuthor Commented:
Using OWA.  Queues are empty.

Also, mail is being delivered fine.
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
Simon Butler (Sembee)ConsultantCommented:
Do you have a Send Connector on the server? They aren't created by default.

Simon.
0
 
Md. MojahidCommented:
you just need to configure the DNS server settings under the Server properties in ECP, heres the link:-

http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages/
0
 
MikeIT ManagerAuthor Commented:
Simon - Yes I have a Send Connector; configured it exactly like I have for past Exchange servers, and confirmed configuration with Microsoft's post-installation tasks, as well as other independent sources.

Md. Mojahid - I've tried that already.  I have both internal and external resolution manually configured to go through my Domain Controller which forwards requests to google (8.8.8.8)
0
 
Simon Butler (Sembee)ConsultantCommented:
The usual reason for something going in to Drafts is a problem with Transport. The service being stopped or the connector not being recognised. It can also happen when there is not enough disk space. It is unusual to happen on a fresh build though.

Simon.
0
 
MikeIT ManagerAuthor Commented:
Not sure what the issue was, i blew it up and am starting from scratch and just deploying 2010. Too many problems from the get go is never a good sign and i just cant afford to continue troubleshooting when I know it doesnt really offer any real advantages over 2010.
0
 
MikeIT ManagerAuthor Commented:
Uninstalled software
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now