Exchange Server Forums

Edge Transport Internet Recieve Connector

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Message Routing >> Edge Transport Internet Recieve Connector

Page: [1]

Message

<< Older Topic Newer Topic >>

Edge Transport Internet Recieve Connector - 25.Jan.2008 10:52:29 PM

schekap

Posts: 1
Joined: 25.Jan.2008
Status: offline

HELP!!

I am having a major exchange issue and I am having the hardest time finding someone with a similar issue like this with their Receive connector.

We have an Exchange 2007 environment with two servers Server A. is a Hub, CAS, STORE, while Server B is our Edge server.

I Installed the Exchange 2007 into a fresh 2003 R2 environment back in September of 2007. There are no pre-existing legacy exchange servers.

Edge transport is setup to filter our spam and such, pretty much your typical setup with nothing special.

As of sometime this morning our internet receive connect on the Edge server is having some serious issues. Every 2 or so hours or randomly the Receive connector that handles ALL of our companies incoming email for mail.mycomany.com sort of locks up and throws out this message

"451 4.4.0 Primary Target IP address responded with: "." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to alternate host."

I am familiar with this message from my initial setup of our Edge server but that instance it was our SEND connect that was having connectivity issues with our HUB transport server. This was also the initial setup, not something that has been working for almost 5 months.

There were no updates applied, the server was wasnt rebooted in the last week and as far as I can tell there is nothing in the event log indicating why it's locking up on us. My only resolution is to manually restart the "Microsoft Exchange Transport� Service. That will immediately get inbound mail working again.

It's happening so much I had to run a script to automatically restart the service every 5 minutes.

Here are my troubleshooting steps

While the Receive connector is locked up
*I can send email externally through the same HUB Transport>Edge Server
* I can watch all incoming email pile up in the Recieve Connector Queue
*From the Edge Server I can ping the HUB Transport, and our domain controllers (DNS)
* I can telnet from the Edge server to the HUB server over port 25 in either direction
* I can ping by DNS name or IP address of either server from either server.
* I deleted and recreated our Internet Receive Connector and completely restarted the system
*Test-Edgesync works perfectly
*Start-Edgesync works perfectly

Restarting the HUB Transport server made no difference, only restarting the MS Exchange Transport service on the edge server solves the issue for a few hours.

HELP!!!! I've been looking all over the net for about 14 hours trying to find something similar.

-Matt

< Message edited by schekap -- 25.Jan.2008 10:54:36 PM >

Post #: 1

Featured Links*

RE: Edge Transport Internet Recieve Connector - 12.Feb.2008 10:58:27 AM

dssbreilly

Posts: 31
Joined: 12.Feb.2008
Status: offline

the follow urls have the info to help trouble shoot the queues/connectors

http://www.exchangeninjas.com/TroubleshootingExchange2007TransportQueuingProblems

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1115899&SiteID=17

Can you enable protocol logging for SMTP Send (which would tell you whether it tries to connect to the outside, and if that fails, the socket error code) and the connectivity log?

To enable the SMTP Send protocol log:
get-sendconnector | set-sendconnector -ProtocolLoggingLevel Verbose

PS let us know how u get on, and if you do get it working, make notes and post the steps here thanks

< Message edited by dssbreilly -- 12.Feb.2008 11:00:00 AM >

(in reply to schekap)

Post #: 2