Exchange settings for Gateway change

We have a Server running Exchange with a default gateway of 192.168.1.1 on a cisco 877 (iPrimus line). I would like to change gateways on the server  to a different router, cisco 851, gateway 192.168.1.254 (Telstra Line).

What do i need to consider in terms of Exchange, SMTP, DNS and MX settings to ensure that exchange will continue to work after I have done the switch?

 
LVL 1
danmax1979Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

danmax1979Author Commented:
Additional info: We are currntly using a smart host smtp.iprimus.com.au that i assume will also need to be changed to a telstra equivalent
0
BusbarSolutions ArchitectCommented:
if both are going from the same ISP then nothing.
if they use different ISP then you will need to update the MX record and PTR records as well as your web mail URL
0
Hypercat (Deb)Commented:
The internal IP address (192.168.1.1 changing to 192.168.1.254) is not the issue.  Is your EXTERNAL IP address changing?  The only reason you would need to make any changes would be if that external IP will be different. Other than that, you just replace one router with the other and make sure to configure all of your firewall and packet forwarding/filters the same as on the old router.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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.

Hypercat (Deb)Commented:
One other thing - you need to make sure that the internal default gateway on all of your servers/workstations is also changed from 192.168.1.1 to 192.168.1.254.
0
danmax1979Author Commented:
Thanks for that, external ip address IS also changing.
0
BusbarSolutions ArchitectCommented:
so you will need to change
mx records IP
PTR records IP
web mail A record  IP
0
Nathan-B2BCommented:
Ensure the 192.168.1.254 router/firewall is forwarding incoming smtp traffic to your server.
Will need to change your servers NIC Gateway to point to the .254 address, rather than the current .1 address.

If you forward email to a smart host, update that to your new ISP smart host.
If you forward unresolved recipients to a smart host, update that ot your new ISP smart host.
DNS on your server, if you have DNS forwarders manually assigned, update these to your new ISP DNS servers.

As mentioned previously, your MX record on the domain you email from will need to point to your new external staic IP address and the associated rDNS record will need updating to your new static IP address (your ISP does this, not you).
0
danmax1979Author Commented:
Hi Guys,

Just an update on the situation here, I have had our MX records modified and everything is now working, mail going in and out etc.

We ended up creating a new mx record mail2.ourdomain.com and also kept our old one mail.ourdomain.com as a backup incase we need to switch back at some time.

Recently (last few months) we have been having some issues with spam being sent to AND from our domain. Now that i have made this change there are a heap of recipients in the Queue getting "Delivery Status Failure" messages stuck in a "Retry" state. The thing is the majority of these recipients look like they are spam type addresses (see attached image).

This is probably a good thing but there are also the odd good address getting caught in this state. Is there something I may have forgotten or is it a case of some people perhaps not recognizing (or permitting) the new mail2.ourdomain.com address?

spam.JPG
0
danmax1979Author Commented:
Also just noticed that under the SMTP server properties, in the Advanced option on the Delivery tab, Masquerade Domain is set on mail.ourdomain.com

Should this be changed to mail2.ourdomain.com??
0
danmax1979Author Commented:
Ok I have implemented that, and i will monitor the performance over the coming days.

Thanks everyone for your help.
0
Shreedhar EtteCommented:
Where are the points for Assistance?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.