3 Exchange Servers behind firewall - supporting different domains
Hello,
We have a small development environment where we have multiple set ups of the same solution repeated.
In each solution is an Exchange server providing the mail functionatily and each solution is set up as completely different public domains .i.e. (1) www.acb1.com (2) www.abc2.com (3) www.abc3.com.
All of these solutions are set up behind one firewall, with different public IP's mapped to each.
Email is workign fine from to and from other domains on the internet. However, we are having trouble working out a way for email to work between the 3 domains on the inside of the firewall.
Has anyone come accross a similar problem?
Does anyone know a way to achieve being able to email Public domains on the internet and internall too?
Thanks,
-Craig
We have a small development environment where we have multiple set ups of the same solution repeated.
In each solution is an Exchange server providing the mail functionatily and each solution is set up as completely different public domains .i.e. (1) www.acb1.com (2) www.abc2.com (3) www.abc3.com.
All of these solutions are set up behind one firewall, with different public IP's mapped to each.
Email is workign fine from to and from other domains on the internet. However, we are having trouble working out a way for email to work between the 3 domains on the inside of the firewall.
Has anyone come accross a similar problem?
Does anyone know a way to achieve being able to email Public domains on the internet and internall too?
Thanks,
-Craig
ASKER
Hi Simon,
If you could explain a little further that would be great. (points increased)
The systems are a mixture of Exchange 2003 and 2007.
Thanks,
-Craig
If you could explain a little further that would be great. (points increased)
The systems are a mixture of Exchange 2003 and 2007.
Thanks,
-Craig
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great - i have followed all that.
Should any services be restarted before the new routes are used?
Should any services be restarted before the new routes are used?
It's always worth restarting the smtp service when you make any changes to SMTP related things. Message tracking will help you work out if they are using the new connectors yet.
ASKER
Its working on the Exchange Server - thanks!
However ive just notice that the application server isnt using the exchange server for outbound mail -its sending it through a virtual SMTP service within IIS.
Do you know how to configure this in the same way?
(points increase to 500)
However ive just notice that the application server isnt using the exchange server for outbound mail -its sending it through a virtual SMTP service within IIS.
Do you know how to configure this in the same way?
(points increase to 500)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Excellent help! - much appreciated
Hope this helps, let me know if you need more info.