Event ID 5015Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=xxx,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=xxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rcapl,DC=com for connector CN=Internet Mail SMTP Connector (xxxx),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=xxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rcapl,DC=com in routing tables with timestamp 6/20/2008 4:22:28 AM. Microsoft Exchange is ignoring the source transport server.Event ID 5010No route has been created for public folder hierarchy CN=Public Folders,CN=Folder Hierarchies,CN=First Administrative Group,CN=Administrative Groups,CN=xxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xxx,DC=com in routing tables with timestamp 6/20/2008 4:22:28 AM. Recipients will not be routed to this public folder. Check the routing logs for further information.Event ID 5016The Active Directory topology service could not discover any route to connector CN=Internet Mail SMTP Connector (xxx),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=RCAPL,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rcapl,DC=com in the routing tables with the timestamp 6/20/2008 4:22:28 AM. This connector will not be used.Anyone can help to solve this problem ?Regards,amilaamila-kumanayake.blogspot.com

It sounds as if your configuration is all correct, but for some reason the 2007 Hub server in the second site has not updated its routing table to detect the route through the first site to the routing group connector and then to 2003. The error messages all indicate that recipient resolution happened okay, the server just can't figure out how to get to its destination. What's the Active Directory replication schedule between the two sites? It's possible that the site does not yet know about the routing group connector. If you can, try forcing Active Directory replication between the two sites. An AD notification of configuration changes should cause the routing tables to update. You can compare the routing configuration logs in both sites and the output of the get-outinggroupconnector cmdlet. The information pulled up should throw some light on what is causing the problem. You can try forcing Active Directory replication between the two sites. In Exchange Server 2003 ESM, right click the Exchange 2003 Server and ensure that the 2007 has full permissions.