• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 276
  • Last Modified:

Changing Exchange Server IP addressing

Because we are moving away from the existing old IP addressing scheme, we will be using new IP addressing on all of the server subnets, so I wonder what can I do to make sure that when I change the Server IP address, email flow is not affected ?

can anyone please share your thoughts and comments here.

Thanks
0
Senior IT System Engineer
Asked:
Senior IT System Engineer
4 Solutions
 
Marshal HubsEmail ConsultantCommented:
Hi,

Exchange doesn't care about the IP address. Therefore changing the IP address and rebooting the server will not be an issue.
Changing the name on the other hand would be a major problem, as that will break Exchange.

As a precaution though, you may want to disable the Exchange services, then reboot the server. The Services will not start. Verify that the server is seeing the domain correctly, registered in DNS etc, then change the services back to automatic and reboot again.
0
 
djStraTTosCommented:
Most probably you have a firewall that is using NAT to route traffic from you MX public IP address to your Exchange server's LAN IP address. Make sure that you amend this record accordingly. Of course you must take care so that your Exchange Server is able to contact your AD server after the IP changes. As Marshalhubs mentioned all changes should take place with the Exchange related services down. Emails that will be sent to your domain during the downtime will be resent automatically so there is a small posibility that you lose any of them (in case you don't have a backup email server).
Since you are not changing anything related to your MX record DNS entries then it's pretty straight forward.
0
 
SandeshdubeySenior Server EngineerCommented:
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Senior IT System EngineerIT ProfessionalAuthor Commented:
Hi All,

The Exchange Server is the small part of the picture, the whole Server and AD network will be changed as well, this includes the AD, DNS server and the user workstation IP address.

My assumption is that as long as the records in the DNS (MX and SRV) for autodiscover is changed accordingly, then it should all be working.

The Hub Transport Server is using Unicast NLB, this will be little bit tricky as I must configure the Cisco switch to update the MAC address mapping.

is that correct ?
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
so in this case as long as the server with the new IP address can successfully ping each other in the same VLAN, I assume that there is nothing that I need to change ?

My initial check will be on the Send & Receive connectors
0
 
djStraTTosCommented:
Exactly as long as you make sure that your firewall is routing incoming and outgoing SMTP traffic to and from your exchange server's new internal IP address.
0
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

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now