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

x
?
Solved

Exchnage server 2013 send and receive internaly

Posted on 2014-07-18
14
Medium Priority
?
281 Views
Last Modified: 2014-08-05
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.
0
Comment
Question by:Golchehr
  • 7
  • 6
14 Comments
 
LVL 4

Expert Comment

by:Philip Portnoy
ID: 40205792
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
 
LVL 12

Expert Comment

by:Md. Mojahid
ID: 40205895
0
 

Author Comment

by:Golchehr
ID: 40209864
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
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 4

Expert Comment

by:Philip Portnoy
ID: 40209873
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
 

Author Comment

by:Golchehr
ID: 40209892
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
 
LVL 4

Expert Comment

by:Philip Portnoy
ID: 40209936
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
 

Author Comment

by:Golchehr
ID: 40209952
Yes, Here is the screenshot.
Exchnage.png
0
 
LVL 4

Expert Comment

by:Philip Portnoy
ID: 40210234
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
 

Author Comment

by:Golchehr
ID: 40212660
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
 
LVL 4

Expert Comment

by:Philip Portnoy
ID: 40212867
You're getting problems with OWA as well, so it's not connectivity.
There IS something wrong with send/receive connectors.
0
 

Author Comment

by:Golchehr
ID: 40213031
My Exchange version is 15.0 (Builds 516.32)
0
 
LVL 4

Expert Comment

by:Philip Portnoy
ID: 40213167
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
 

Accepted Solution

by:
Golchehr earned 0 total points
ID: 40232367
Issue is fixed by editing DNS lookup in Server properties in exchange center
0
 

Author Closing Comment

by:Golchehr
ID: 40240760
We need to add the DNS for local DNS server manually.
0

Featured Post

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.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

579 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question