btomkins
asked on
smtp fails between two exchange 2003 servers on the same domain. (2003 server R2)
SMTP fails between two exchange 2003 SP2 servers on the same domain. (2003 server R2)
The first exchange 2003 server "mx1.abc.local" is hosting mailboxes for users at SITE A with email addresses @a.org
I have added a second exchange server for SITE B
exchange 2003 server mx2.abc.local is hosting mailboxes for users st SITE B with email addresses @b.org
I have define a SMTP "Connector" to forward all mail out via our isp a with an Address Space of *.
(same isp in both locations) with MX1 and MX2 selected as bridgehead servers on the conector.
I now have a queue of mail on MX1 for MX2 (emails to b.org) and a queue of mail on MX2 for MX1 (emails to a.org) . both queues are saing :
The remote server did not respond to a connection attempt.
We have a VPN between Site A and Site B and mx1and mx2 can ping each other.
Question 1
Do they need a connector/route or is it some problem with the SMTP virutal servers ?
Question 2
Client at connecting to mx2 are getting sycronise errors with the Offline Address Book. Do I need to do anything to get mx2 to sync the Offline Address Book?
Thanks
Brian
The first exchange 2003 server "mx1.abc.local" is hosting mailboxes for users at SITE A with email addresses @a.org
I have added a second exchange server for SITE B
exchange 2003 server mx2.abc.local is hosting mailboxes for users st SITE B with email addresses @b.org
I have define a SMTP "Connector" to forward all mail out via our isp a with an Address Space of *.
(same isp in both locations) with MX1 and MX2 selected as bridgehead servers on the conector.
I now have a queue of mail on MX1 for MX2 (emails to b.org) and a queue of mail on MX2 for MX1 (emails to a.org) . both queues are saing :
The remote server did not respond to a connection attempt.
We have a VPN between Site A and Site B and mx1and mx2 can ping each other.
Question 1
Do they need a connector/route or is it some problem with the SMTP virutal servers ?
Question 2
Client at connecting to mx2 are getting sycronise errors with the Offline Address Book. Do I need to do anything to get mx2 to sync the Offline Address Book?
Thanks
Brian
Last Comment
ASKER
Thanks for prompt reply.
Can you please give me a starting point for each solution. A link or anything.
Brian
Can you please give me a starting point for each solution. A link or anything.
Brian
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Athough I can ping across the vpn between mx1 and mx2.
I am unable to telnet to port 25 across the VPN.
When checking the SMTP virtual servers I clicked on the relay button on the access tab and added the ip of the other server. Is this correct?
I am unable to telnet to port 25 across the VPN.
When checking the SMTP virtual servers I clicked on the relay button on the access tab and added the ip of the other server. Is this correct?
You don't need to add anything to the relay settings, so remove that.
Furthermore the relay settings wouldn't stop the servers from being able to communicate. The fact that you cannot telnet to port 25 of the other server means that the port is being blocked by something. I identified the most blocks above.
Simon.
Furthermore the relay settings wouldn't stop the servers from being able to communicate. The fact that you cannot telnet to port 25 of the other server means that the port is being blocked by something. I identified the most blocks above.
Simon.
ASKER
You are a genius Simon.
It turned out to be a shorewall tcrule that was redirecting all port 25 traffic to the one isp (we have a couple) . I made the rule a tad more specific so the SMTP traffic could travel through the vpn.
I also created a routing group, moved MX2 to it and created a connector but was unsuccessful so I have reverted back to the First Routing Group and all is working.
1) Is a routing group required?
2) Do you have a link to fool proof instructions on doing this?
The OAB problem was fixed by adding MX2 to the replication servers list using the manage settings wizard on the "Default Offline Adress Book" Object.
3) Do I need a to do the same for any other objects?
Thanks
Brian
It turned out to be a shorewall tcrule that was redirecting all port 25 traffic to the one isp (we have a couple) . I made the rule a tad more specific so the SMTP traffic could travel through the vpn.
I also created a routing group, moved MX2 to it and created a connector but was unsuccessful so I have reverted back to the First Routing Group and all is working.
1) Is a routing group required?
2) Do you have a link to fool proof instructions on doing this?
The OAB problem was fixed by adding MX2 to the replication servers list using the manage settings wizard on the "Default Offline Adress Book" Object.
3) Do I need a to do the same for any other objects?
Thanks
Brian
You always have at least one routing group. However if the servers are on separate networks or sites then you can use routing groups to manage email flow - so internet email goes straight out rather than across the inter-site connection.
The common issue when splitting servers by routing groups is to caused by name resolution. It is fixed by changing the SMTP virtual server IP address setting from "All Unassigned" to the specific IP address. Then recreating the Routing Group connector.
For the system folders, specifically OAB and Free/Busy data, I usually recommend replicating them to all mailbox servers in the org.
Public Folders themselves also may need to be replicated to the other servers so that users can access everything.
Simon.
The common issue when splitting servers by routing groups is to caused by name resolution. It is fixed by changing the SMTP virtual server IP address setting from "All Unassigned" to the specific IP address. Then recreating the Routing Group connector.
For the system folders, specifically OAB and Free/Busy data, I usually recommend replicating them to all mailbox servers in the org.
Public Folders themselves also may need to be replicated to the other servers so that users can access everything.
Simon.
ASKER
Thanks again.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
What currently is happening (estimation) is that your exchange servers are both trying to send the email to the internet published IP adresses.
2) Define a copy of the OAB public folder on the MX2. (assuming that the public folder store on server MX2 is default PF store for the mailboxes.