Pro4ia
asked on
Exchange 2003 removal from coexistence with 2010 - SMTP 5.0.0 problem
Experts,
I have a problem with inbound delivery to our Exchange 2010 server after removing our Exchange 2003 server.
Prior to removal, all inbound emails were being pointed to our Barracuda and fwded to Exchange 2010 (was setup this way for about a week). Outbound email has no problems.
Right after the removal, I am getting this NDR from external senders and no inbound mail is being received.
Delivery has failed to these recipients or distribution lists:
recipient@domain.com
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
Diagnostic information for administrators:
Generating server: mail.domain.com
recipient@domain.com
#< #5.0.0> #SMTP#
the error code doesn't really tell me much. What could be the problem here?
I have a problem with inbound delivery to our Exchange 2010 server after removing our Exchange 2003 server.
Prior to removal, all inbound emails were being pointed to our Barracuda and fwded to Exchange 2010 (was setup this way for about a week). Outbound email has no problems.
Right after the removal, I am getting this NDR from external senders and no inbound mail is being received.
Delivery has failed to these recipients or distribution lists:
recipient@domain.com
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
Diagnostic information for administrators:
Generating server: mail.domain.com
recipient@domain.com
#< #5.0.0> #SMTP#
the error code doesn't really tell me much. What could be the problem here?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes as mentioned in OP, barracuda has been pointing to the Exchange 2010 for almost a week now.
You shouldn't need to recreate it.
You have all the accepted domains configured?
You have all the accepted domains configured?
ASKER
yes the setting has been copied over during coexistence with Ex 03.
ASKER
after removal of Exchange 2003, is rebooting Exchange 2010 recommended?
It may be worth a go, can't say I've ever had to.
Can you telnet to the exchange server on port 25 and send an email following these steps: http://support.microsoft.com/kb/153119
From the exchange management shell run: get-accepteddomain and post the results please
Can you telnet to the exchange server on port 25 and send an email following these steps: http://support.microsoft.com/kb/153119
From the exchange management shell run: get-accepteddomain and post the results please
Also, can you set port 25 to go directly to the exchange server instead of the barracuda? This will help is eliminate this as the problem.
ASKER
[PS] C:\Users\pro4ia\Desktop>ge
Name DomainName DomainType Default
---- ---------- ---------- -------
domainfoods.org domainfoods.org Authoritative False
domainfoods.com domainfoods.com Authoritative False
domain.com domain.com Authoritative False
domainfoodsco.com domainfoodsco.com Authoritative True
domainfoodsco.com is our primary public email domain
Name DomainName DomainType Default
---- ---------- ---------- -------
domainfoods.org domainfoods.org Authoritative False
domainfoods.com domainfoods.com Authoritative False
domain.com domain.com Authoritative False
domainfoodsco.com domainfoodsco.com Authoritative True
domainfoodsco.com is our primary public email domain
Can you try the telnet test and the port 25 redirect?
ASKER
I have successfully performed the manual SMTP test from inside the network.
currently our MX is pointing to barracuda and no telnet is allowed to Exchange 2010 server directly from outside. could this be a problem?
currently our MX is pointing to barracuda and no telnet is allowed to Exchange 2010 server directly from outside. could this be a problem?
It shouldn't be as long as the barracuda is doing what it's told.
You should be able to change port 25 to go to your exchange server instead of the barracuda on your router/firewall.
This will help identify if the problem is exchange or the barracuda.
You should be able to change port 25 to go to your exchange server instead of the barracuda on your router/firewall.
This will help identify if the problem is exchange or the barracuda.
ASKER
we might have something here.. after redirecting tcp 25 directly to Exchange 2010, I was able to receive an outside email.. i'm rebooting barracuda as I type this
I guess when I mentioned trying to change the NAT on your firewall in my first post this was overlooked?
ASKER
chopper - sorry it looks like i overlooked it. I don't manage the barracuda myself so after looking at the setting myself, there was a tab in there that has all accepted domains and which server it should be pointing to. corrected this and inbound emails are now happy again. will split points.
appreciate the help from both of you.
appreciate the help from both of you.
ASKER
perhaps it has to do with recipient connector or routing groups. prior to uninstalling Exchange 2003, I did remove the Ex03 <-> Ex10 routing group connectors.
I did check the default receive connector and made sure anonymous is checked. should i try recreating it?