Exchnage server 2013 send and receive internaly

I have installed Exchange server 2013. I setup send connector. I didn't setup external MX record yet.  The issue is , sending email doesn't work internally.  for example when I send an email from administrator to another user inside of organization, it wont go true. It shows in sent items but I don't see anything in inbox. I tried OWA also and I see all sent emails in Draft folder. Any idea ? I need to fix this issue first and then setup external MXrecord  to receive email from Outside.
GolchehrAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip PortnoySr. MS SQL DBA and Technical Account ManagerCommented:
Hello,

let me guess, you have CAS and Mailbox on different servers?
You need following receive connectors on every CAS and mailbox for everything to work:

MB:
1) Client Proxy (TLS, Basic (with TLS), Integrated and Exchange auth; For Exchange Servers and Exchange Users) - should listen on 465
2) Default (TLS, Basic (with TLS), Integrated and Exchange auth; For Exchange Servers, Legacy Exchange Servers and Exchange Users) - should listen on 25

CAS:
1) Client Frontend (TLS, Basic (with TLS) and Integrated auth; For Exchange Users) - should listen on 587
2) Default (TLS (with mutual Auth TLS), Basic (with TLS), Integrated and Exchange auth; For Exchange servers, Legacy Exchange Servers and Anonymous users) - should listen on 25
3) Outbound proxy (TLS (with mutual Auth TLS), Basic (with TLS), Integrated and Exchange auth; For Exchange servers and Anonymous users) - should listen on 717

#3 for CAS is probably the one that's misconfigured.
0
GolchehrAuthor Commented:
I followed all recommendation but I still have the issue.

I am not able to send or receive mails internally from exchange 2013. the users who are at exchange 2013 server  mailbox are not able to send or receive mail and the mails are going to draft folder and from their they are not going.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Philip PortnoySr. MS SQL DBA and Technical Account ManagerCommented:
Can I ask again: do you have CAS and Mailbox on the different or same server?
If they are not different make sure this connector:

2) Default (TLS, Basic (with TLS), Integrated and Exchange auth; For Exchange Servers, Legacy Exchange Servers and Exchange Users) - should listen on 25

listens on port 2525 instead of 25.
0
GolchehrAuthor Commented:
They are in same server. They are all checked. I even can't send email from any mailbox to itself. for example when I send email from Administrator to its mailbox I DONT RECEIEV ANYTHING IN INBOX !!
0
Philip PortnoySr. MS SQL DBA and Technical Account ManagerCommented:
Are you sure that you have 2525 port for one of the connectors?
This looks exactly like the issue when MB is not listening on 2525.

Can you show the screenshot?
0
GolchehrAuthor Commented:
Yes, Here is the screenshot.
Exchnage.png
0
Philip PortnoySr. MS SQL DBA and Technical Account ManagerCommented:
Can you please verify and, if necessary, re-create connectors according to this article:
http://exchangemaster.wordpress.com/2014/01/24/incorrectly-adding-new-receive-connector-breaks-exchange-2013-transport/

Please post test results (there are few commands you have to run).
0
GolchehrAuthor Commented:
I recreated but still same issue. I wonder if there is server connectivity issue. It seems after send email it doesn't get to server. I used delivery reports and it didn't results anything. My Exchange server is a VM under Hyper-V host , but client and AD are on ESXI host. They see each other.

Any idea ?
0
Philip PortnoySr. MS SQL DBA and Technical Account ManagerCommented:
You're getting problems with OWA as well, so it's not connectivity.
There IS something wrong with send/receive connectors.
0
GolchehrAuthor Commented:
My Exchange version is 15.0 (Builds 516.32)
0
Philip PortnoySr. MS SQL DBA and Technical Account ManagerCommented:
Well, to understand what's happening there we'll need to enable verbose logging.
Enable logging for Send/Receive connectors. Reproduce the issue (from OWA).
Post the log content at the time when you reproduced the issue.

All information on how to enable logging and where logs will be located can be found here: http://technet.microsoft.com/en-us/library/aa997624(v=exchg.150).aspx
0
GolchehrAuthor Commented:
Issue is fixed by editing DNS lookup in Server properties in exchange center
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
GolchehrAuthor Commented:
We need to add the DNS for local DNS server manually.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.