Have you configured the ADC and replicated Exchange 5.5 DS to AD ? Are the two servers in the same Site/Routing Group, if they are in different Site/Routing Groups, how are they interconnected ? Regards, Raj _____ From: Thomas Arena [mailto:arena@xxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, September 22, 2004 1:34 PM To: [ExchangeList] Subject: [exchangelist] Exchange 2003 coexisting with 5.5 http://www.MSExchange.org/ Hello, We have a new exchange 2003 server that's been added to our existing 5.5 organization. The Internet Mail Connector is on a 5.5 machine and we will keep the mail flow like that for now. All of the recipients on the 5.5 side can send and receive fine. However, when sending to the 2003 recipients from a 5.5 account or from and external account we get: did not reach the following recipient(s): a3 on Wed, 22 Sep 2004 12:18:23 -0500 The recipient was detected looping within the message transfer service The MTS-ID of the original message is: c=us;a= ;p=river oaks imagi;l=ROBDC0409221718TN3HZYH4 MSEXCH:MSExchangeMTA:ROINTDOM:ROBDC Thanks for any ideas. -thomas ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: raj.periyasamy@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx