Discussion Locked

Exchange 5.5 to Exchange 5.5

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

OK all you Exchange experts, can you help?
I have 2 HP Netserver E-50 boxes running NT4.0SP6a and Exchange 5.5 (Sp4. One has been running for several months without missing a beat and is configured for 200 users. The other I configured yesterday for 7 users. Both are behind a FreeBSD firewall with Squid proxy and are delegated as 2 seperate internet doamins. Behind the firewall they are on the same subnet, but in 2 different NT domains.
2 way trusts have been setup between the domains.
The problem I have is that I cannot send e-mail from one web server to the other. ie if user1@domain1.com.au (we are in Australia here)tries to send an email to user2@domain2.com.au it simply sits in the output queue of the domain1 exchange server. The error says the connection to domain2 was refused.
I can, however send mail from domain2 to domain1 without problems.
At present I have got around this by creating the users of domain2 in domain1 and then forwarding to a forwarding e-mail outside ofthe organisation that then bounces back to the other domain2 (ie e-mail for domain2 goes from domain1 to ForwardingDomain then domain2. This works.
Pinging domain2 from domain1 (and vice versa) gives the correct IP addresses, likewise the servers can ping each other internally (ie behind the firewall). I can also telnet on port 25 to each sexchange server.
I have checked both server settings against each other and they are the same (except for domain names).
Each server can send and receivee-mail from outside of the organisation without any trouble.
What is causing the problem? Can anyone help?

2 replies

by [_rick_>

Check the IMS Connector for Domain 2. More specifically the Connections tab, proceed to specify by host. Are there any entries here?

Now proceed to Delivery Restrictions tab. Any restrictions set?

Now proceed to the Routing tab. Check all settings for any inadvertent ROUTING restrictions.

Good luck

by acattr

Your issue is that the exchange servers are using external dns servers resolving external addresses, confusing the firewall.

if both servers are on the same subnet, install DNS on one server. Create zones for both domains. Add the mx records foreach domain pointing to the internal addresses of thier corresponding server. Setup both exchange to use that dns server as thier PRimary DNS server.

This discussion is closed to new replies.