Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Send mail but not receive on Exchange 2013
Hello,
We are about ready to start co-existence and migration from Exchange Server 2007 (Update Rollup 12) to Exchange Server 2013 SP1. I have set up a test mailbox on the new server. I am able to send email both internally and externally from that account, but I cannot receive mail in that account. I have been following closely the steps outlined on the Exchange Server Deployment Assistant as well as here - http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part11.html. The only special things to be aware of are:
- our 2007 server does not use SSL at all. We have added the name of this server, plus a legacy namespace to the SSL cert for the 2013 server. The cert has been exported from the 2013 server and added as an exchange certificate, but not yet enabled.
- we have not yet enabled Outlook Anywhere on the 2007 server.
- we using a new service name (mail) for the new server and discontinuing the name used on the old server, so that is not an issue to transfer
- We are using ORF as our spam filter. It is not going to be installed on the 2013 server until tomorrow.
We are hoping to complete all of the service-disrupting changes in the early morning hours in just a few days, following the steps outlined by Simon here: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_28350139.html
We are well aware that this is going to cause an issue with our Android and Windows Phone users, and they all understand upfront that their email will be disrupted on their phones until we can re-configure their devices (our MDM solution will allow us to edit iPhone ActiveSync settings, but not Android/WP).
Sorry for the long question, and I probably didn't give all the relevant information. I appreciate any help that you can give, or even to point me in the direction of how to troubleshoot this issue.
Thanks!
We are about ready to start co-existence and migration from Exchange Server 2007 (Update Rollup 12) to Exchange Server 2013 SP1. I have set up a test mailbox on the new server. I am able to send email both internally and externally from that account, but I cannot receive mail in that account. I have been following closely the steps outlined on the Exchange Server Deployment Assistant as well as here - http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part11.html. The only special things to be aware of are:
- our 2007 server does not use SSL at all. We have added the name of this server, plus a legacy namespace to the SSL cert for the 2013 server. The cert has been exported from the 2013 server and added as an exchange certificate, but not yet enabled.
- we have not yet enabled Outlook Anywhere on the 2007 server.
- we using a new service name (mail) for the new server and discontinuing the name used on the old server, so that is not an issue to transfer
- We are using ORF as our spam filter. It is not going to be installed on the 2013 server until tomorrow.
We are hoping to complete all of the service-disrupting changes in the early morning hours in just a few days, following the steps outlined by Simon here: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_28350139.html
We are well aware that this is going to cause an issue with our Android and Windows Phone users, and they all understand upfront that their email will be disrupted on their phones until we can re-configure their devices (our MDM solution will allow us to edit iPhone ActiveSync settings, but not Android/WP).
Sorry for the long question, and I probably didn't give all the relevant information. I appreciate any help that you can give, or even to point me in the direction of how to troubleshoot this issue.
Thanks!
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
See the articles will help your create or modifies your default receive connector and anonymous.
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
So, I have followed the instructions from Mojahid's link and have verified that the Default Receive connector (both FrontEnd and Hub Transport) allows anonymous connections, but I still cannot receive mail in the test mailbox. Though I did not perform the shell command Get-ReceiveConnector "Relay E15MB1" | Add-ADPermission -User 'NT AUTHORITY\Anonymous Logon' -ExtendedRights MS-Exch-SMTP-Accept-Any-Re
Can the user send messages to themselves?
Create a second user on the new server. Can the two new users send mail to each other?
Create a second user on the new server. Can the two new users send mail to each other?
Yes. Users can send to themselves and between accounts both located on the Exchange 2013 server.
If it helps at all, I looked on the Exchange 2007 server. Attached is the error that is coming up when I try to send from either externally or a 2007 mailbox to a mailbox on the 2013 server.
If it helps at all, I looked on the Exchange 2007 server. Attached is the error that is coming up when I try to send from either externally or a 2007 mailbox to a mailbox on the 2013 server.
See if this article applies to you. Is Exchange 2007 on the latest service pack and cumulative update?
http://support.microsoft.com/kb/976108/en-us
http://support.microsoft.com/kb/976108/en-us
I don't believe this article applies to our situation. We do not use an edge transport server, and we are on SP3, Update Rollup 12.
No. This is a dumb question, but I'm wondering from the screenshot if I need to manually create an MX record for my 2013 server? As I'm looking in DNS, we do not have any MX records internally.
nslookup.png
nslookup.png
No, you don't need any MX records internally. Externally I am guessing you MX record points to your 2007 server, where mail flow is still probably routing primarily.
Seems like this blogger had the same problem.
http://jerridwills.com/2013/05/19/451-4-4-0-dns-query-failed/
Seems like this blogger had the same problem.
http://jerridwills.com/2013/05/19/451-4-4-0-dns-query-failed/
Gareth. Thank you so much for your persistence in helping me with this issue. While the blog entry itself didn't solve my problem, the first comment on the post did. We had Google public DNS set as the secondary DNS server on the NIC. As soon as I removed that secondary DNS entry, mail flowed. I have also noticed a significant speed increase with ActiveSync - not sure if that is real or placebo yet.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial