Improve company productivity with a Business Account.Sign Up

x
?
Solved

Messages remaining in routing group connector

Posted on 2007-12-04
4
Medium Priority
?
1,532 Views
Last Modified: 2012-08-13
I have this incredibly strange problem with exchange between 4 sites.

I have 4 sites. Each was configured in its own administrative group.
Our main office has a routing group connector for each of the 3 servers in the other offices.

Yesterday I changed the exchange organisation to native mode and since then the offices have had lots of problems sending mail within the organisation.

If I send a blank test message from one of the sites the message will arrive but there are messages in the queue that will not come through.
In the event logs I've seen this event logged once in a while.

Message delivery to the host 'x.x.x.x' failed while delivering to the remote domain  '_693a5a4ec6af5d4081f63b043f920e7a_D' for the following reason: The semaphore timeout period has expired.

I also see this log

Message delivery to the host '192.168.0.4' failed while delivering to the remote domain  '_693a5a4ec6af5d4081f63b043f920e7a_D' for the following reason: The connection was dropped by the remote host.

I don't see any other logs that would indicate a problem.

When I look at the main servers smtp connector I see sessions from the remote servers, you can see the sessions have been connected for over 300 seconds. Its like the connection is made and then it just stays open.

When sending from the head office server to any of the others it works fine but the other way its very tempremental.

I've run the exchange trouble shooting tool and it reports no problems.
I've using symantec enterprise, I've verified I'm not using internet email scanning plugin.

The server are connected via cisco ipsec tunnels, all ports are good.

I'm really puzzled on this. Like I said it worked fine until I went into native mode and of course. Theres no going back.
0
Comment
Question by:dj_relentless
  • 2
  • 2
4 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 20402519
The first thing I would suggest is to verify that the SMTP virtual servers are set to a specific IP address and not all unassigned. If they are set to all unassigned, change them to the specific IP address of the server, then recreate the routing group connectors.

Simon.
0
 
LVL 4

Author Comment

by:dj_relentless
ID: 20402591
I double checked this and set all the other offices to their specific ips and recreated the connectors. No difference.
I forgot to mention that I've run winroute and verified everything looks happy. All routing connectors say they have connections.
0
 
LVL 104

Accepted Solution

by:
Sembee earned 1000 total points
ID: 20402619
It can take 15 - 20 minutes for the RGC recreation to take effect. You can speed thing up a little by restarting the Exchange routing engine service.

The errors you have posted are connectivity errors - usual cause is something blocking or scanning the SMTP traffic. Firewalls with SMTP scanning functionality can cause similar issues.

Simon.
0
 
LVL 4

Author Comment

by:dj_relentless
ID: 20402821
Your a legend. I had sat there staring at the anti virus software, routing connectors and event logs until my eyes were sore (which was from 2pm until 9:30pm last night). Nothing is worse than working late and going home knowing you didn't achieve anything.

I checked the cisco firewall responsible for the vpn and low behold it was set to inspect smtp traffic.  Disabled and the connector kicked into life and cleared the queue. I'm checking our other sites now and it looks like they all have the same inspection set on the firewalls.
0

Featured Post

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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

In migration, Powershell can be a very crucial tool to achieve success and finalize projects within deadline or even fix issues. X500 or Legacy Exchange DN Attribute can cause lots of issue during the migration
Fix RPC Server is unavailable Error in Exchange 2013, 2010, 2007, and 2003 Server. Different reason can such as network connectivity issue, name resolution issue, firewall, registry corruption that lead to RPC Server Unavailable error.
This video discusses moving either the default database or any database to a new volume.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…

579 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question