Routing to 2003 server

Routing to 2003 server (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Message Routing

Message

frist44 -> Routing to 2003 server (8.Jan.2009 3:33:31 PM)
I would like to have mail from 2007 server sent to 2003 server for Internet deliver because the 2003 server is in a datacenter with mail security appliances in front of it. The 2007 server is in an office remote to the data center. I can't get the mail to go from 2007 to 2003. I have recreated the Routing Group connectors several times and still no luck. Any specifics I can check or look for?

jveldh -> RE: Routing to 2003 server (8.Jan.2009 4:02:55 PM)
Hi, I assume you followed the following Technet article: http://technet.microsoft.com/en-us/library/aa997292.aspx If not follow it and let me know if it works after that.

John Weber -> RE: Routing to 2003 server (8.Jan.2009 4:18:06 PM)
you included the bidirectional:$true ? can the 2007 server see the 2003 server by name? does mail get from 2003 to the 2007 server? we need a tad more info.

frist44 -> RE: Routing to 2003 server (8.Jan.2009 4:30:47 PM)
I did follow this. This was my guide for attempting to recreate the routing groups. I did include the bidrectional attribute. The 2007 can see the 2003 server by name. Mail successfully goes from the 2003 to 2007. quote: ORIGINAL: jveldh Hi, I assume you followed the following Technet article: http://technet.microsoft.com/en-us/library/aa997292.aspx If not follow it and let me know if it works after that.

frist44 -> RE: Routing to 2003 server (8.Jan.2009 4:53:35 PM)
I recreated them again. I'm noticing that mail is not moving either way now. In the Event logs of the 2003 machine, i have this error: Failed in reading Connector's DS Info Process Id: 1400 Process location: C:\WINDOWS\system32\inetsrv\inetinfo.exe ConnectorDN: CN=FAXmaker:i386 (PNM4),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=PNMMSSM,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com Hr:c004038a Attribute:[homeMTA] This connector isn't actually in Exchange. I can't see it anywhere. That machine name (PNM4) isn't an exchange server. Awhile back is was listed in the Exchange name and I think someone tried to get it out (This was before me). Everytime Exchange tries to transport, I see this error, but I don't see any activity for transporting to the 2007 machine. do you think this has anything to do with it?

jveldh -> RE: Routing to 2003 server (8.Jan.2009 4:55:34 PM)
Hi, Is there any warning displayed in the mail queue that contains the mails that need to be send to the Exchange 2003 server ?

frist44 -> RE: Routing to 2003 server (8.Jan.2009 5:20:01 PM)
I was able to remove that machine (PNM4) from AD and the errors in the event logs of Exch 2003 have gone away. The messages are still in the queue of each machine (2003 and 2007) waiting to go from one to the other. There is nothing obvious in the queues that indicate what the issue is. This is so frustrating. Seems like such a simple thing. Is there authentication or something that I'm missing???? I change the authentication and network address on the receive connector on the 2007 machine to all the 2003 machine.

frist44 -> RE: Routing to 2003 server (9.Jan.2009 4:00:38 PM)
Should I be able to send an email through telnet from exchange server to exchange server? If so, I can't. We have a site to site VPN through 2 Cisco ASA devices and I'm wondering if that's doing something. There aren't really any rules on the L2L.

jveldh -> RE: Routing to 2003 server (9.Jan.2009 4:32:24 PM)
Hi, Can you ping the other server ?

frist44 -> RE: Routing to 2003 server (9.Jan.2009 5:14:05 PM)
yes i can ping both devices.

frist44 -> RE: Routing to 2003 server (9.Jan.2009 5:17:57 PM)
If I'm in the site of the exchange server, I can telnet to it on port 25 and send mail. If i'm at the other site, I can NOT send mail through the exchange server. Could the router be doing something to it?

frist44 -> RE: Routing to 2003 server (9.Jan.2009 5:23:56 PM)
If I telnet to the other site's Exchange server from outside the site, it connects and responds as 220****************************** And then everything else I type is : 500 5.3.3 Unrecognized command If i'm within the particular site and do the same thing, i get a normal reponse.

Subashes -> RE: Routing to 2003 server (10.Jan.2009 2:19:05 AM)
I had same kind of problem, it’s an issue ASA. I fixed by disabling it: no fixup protocol smtp 25 Refer the Microsoft KB for details. http://support.microsoft.com/kb/295725

Subashes -> RE: Routing to 2003 server (10.Jan.2009 2:25:42 AM)
Or Configuration --> Service Policy Rules --> General/Global Policy --> Edit ---> Rule Actions --> Untick ESMTP Click OK --> Apply --> Save Or en (password) conf t no fixup protocol smtp 25 (ctrl+z) wr me exit Ref : http://www.experts-exchange.com/Security/Software_Firewalls/Enterprise_Firewalls/Cisco_PIX_Firewall/Q_22967873.html

jveldh -> RE: Routing to 2003 server (10.Jan.2009 8:03:03 AM)
Hi, So to summary you can't telnet from the Exchange server to the Exchange server which sends e-mail to the internet ?

frist44 -> RE: Routing to 2003 server (10.Jan.2009 10:07:08 AM)
quote: ORIGINAL: jveldh Hi, So to summary you can't telnet from the Exchange server to the Exchange server which sends e-mail to the internet ? That is correct. quote: ORIGINAL: Subashes I had same kind of problem, it’s an issue ASA. I fixed by disabling it: no fixup protocol smtp 25 I guess I have to make this change on both site's ASA?

Subashes -> RE: Routing to 2003 server (10.Jan.2009 12:16:14 PM)
You have to, if you have problem to telnet both ways [8\|]. Basically I feel it’s a problem with mailguard. You may also try by updating the firmware.

jveldh -> RE: Routing to 2003 server (10.Jan.2009 5:06:12 PM)
Hi, Yes check the ASA it's probably causing the issue.

frist44 -> RE: Routing to 2003 server (11.Jan.2009 10:27:59 AM)
quote: ORIGINAL: Subashes Or Configuration --> Service Policy Rules --> General/Global Policy --> Edit ---> Rule Actions --> Untick ESMTP Click OK --> Apply --> Save Or en (password) conf t no fixup protocol smtp 25 (ctrl+z) wr me exit Ref : http://www.experts-exchange.com/Security/Software_Firewalls/Enterprise_Firewalls/Cisco_PIX_Firewall/Q_22967873.html It looks like this may have done it! thanks again!

Page: [1]