RE: Changing IP of Exchange 2003

  • From: <ChongJa@xxxxxxxxxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 21 Dec 2005 16:01:06 -0500

I've seen an issue once, when I changed IP. I built an Exchange server
to be frontend in a lab. Then I deployed it, changed production IP and
an Exchange service did not start. The IP was changed to a different
subnet and an Exchange service did not start, something about it
changing sites. There was an event in the log that lead me to a KB
article for the fix. (not a hotfix)  Maybe this has been corrected with
updates. 

________________________________

From: MAHADEVAN Subramanyan [mailto:SMahadevan@xxxxxxxxxxxx] 
Sent: Wednesday, December 21, 2005 7:55 AM
To: [ExchangeList]
Subject: [exchangelist] Changing IP of Exchange 2003


http://www.MSExchange.org/


We have a requirement for changing the IP address of the Exchange 2003
server. Will that create any adverse effect?

Thanks

Mahadevan

Confidentiality Statement:

This message is intended only for the individual or entity to which it
is addressed. It may contain privileged, confidential information which
is exempt from disclosure under applicable laws. If you are not the
intended recipient, please note that you are strictly prohibited from
disseminating or distributing this information (other than to the
intended recipient) or copying this information. If you have received
this communication in error, please notify us immediately by return
email.
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp 
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
chongja@xxxxxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx 

Other related posts: