• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 325
  • Last Modified:

transition from exchange 2007 to exchange 2010 but mail flow not working internally.

i have done transition from exchange 2007 to exchange 2010 but mail flow not working internally.
0
Yogesh_Exchange_Expert
Asked:
Yogesh_Exchange_Expert
  • 5
  • 5
  • 3
  • +1
1 Solution
 
Madan SharmaConsultantCommented:
is it working externally ? will you please elaborate your question so that we can assist you better ? if you have any error message or log also post them here.
0
 
Yogesh_Exchange_ExpertAuthor Commented:
nothing simple new migration installed new exchange 2010 mail flow not working between old and new servers. externally its working internally not working.
0
 
numero_unoCommented:
Check the receive connectors on both systems(2007 and 2010) and also ensuet that you have enabled the "Exchange server authentication" method.


0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Madan SharmaConsultantCommented:
you need to check the setting for you routing connector between your exchange2003 and exchange2010 if your didn't find any misconfiguration you can also remove the old and create new routing connector by using exchange2010 power shell with following command:-
New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Ex2010Hub1.contoso.com" -TargetTransportServers "Ex2003BH1.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true

for more details have a look at http://technet.microsoft.com/en-us/library/aa997292.aspx
0
 
Yogesh_Exchange_ExpertAuthor Commented:
no i have migrated from exvhange 2007 to 2010
0
 
Madan SharmaConsultantCommented:
0
 
Yogesh_Exchange_ExpertAuthor Commented:
i am getting below message while doing tracking

The message has been queued on server 'dc-u' since 10/19/2011 8:47:42 AM (UTC-07:00) Mountain Time (US & Canada). The last attempt to send the message was at 10/19/2011 8:53:09 AM (UTC-07:00) Mountain Time (US & Canada) and generated the error '451 4.4.0 Primary target IP address responded with: "451 5.7.3 Cannot achieve Exchange Server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.'.
0
 
Madan SharmaConsultantCommented:
Make sure that Exchange Authentication is enabled, and that in the receive connector,
go to Server Configuration -> Hub Transport -> Receive Connectors go to authentication tab and Ensure that Exchange Server authentication is enabled.
Rinse and repeat if necessary
0
 
Madan SharmaConsultantCommented:
also have look at this link
0
 
AkhaterCommented:
cannot achieve exchange authentication is usually due to firewall misconfiguration when each server is in a different AD site.

is this the case? are each of these servers in a different site with firewalls in between ? if so disable any smtp inspection on the firewalls
0
 
Yogesh_Exchange_ExpertAuthor Commented:
SMTP inspection is disabled also exchange authentication is enabled.
0
 
AkhaterCommented:
if when you telent the banner is 220******************************** then it is the firewall (PIX) answering and not exchange this is a typical error and it means that SMTP inspection is NOT disabled
0
 
Yogesh_Exchange_ExpertAuthor Commented:
tried to disable esmtp service but no use and smtp inspection is already disabled.
0
 
AkhaterCommented:
when u telnet now are you seeing the exchange banner?
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.

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