[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 179
  • Last Modified:

Change Exchange 2003 Standard Change IP for E-mail and OWA Usage?

Hi EE Kids,

We have a T1 circuit with two public IPs. One IP is for OWA and the other is incoming/outgoing e-mail. The T1 and our e-mail filter are being replaced. I need to migrate OWA and the filter off that T1 to a new circuit. We are using Exchange 2003 Standard.

166.55.16.52 is used for OWA. After NAT it goes directly to Exchange.

166.55.16.51 is our MX record for mail.mybiz.com. After NAT it goes to our e-mail filter then the e-mail filter forwards it to Exchange.

What would I need to change in Exchange System Manager to make the changes successful so OWA still works and incoming/outgoing e-mails send/receive from the new e-mail filter?  I know I need to talk to our ISP about changing the sub-domain IP for OWA and the MX e-mail record. Does the ISP need to do anything else? When I tell me ISP to make these changes does it really take 2-3 days?

All I see in ESM is Administrator Groups -> Routing Groups-> Connectors. With a Connector pointing to our e-mail filter.
0
First Last
Asked:
First Last
  • 2
3 Solutions
 
e_aravindCommented:
Atleast regarding the OWA access
166.55.16.52 is used for OWA. After NAT it goes directly to Exchange
should changed to
166.55.16.xx ---> After NAT it should directly reach to Exchange\IIS server

Testing:
Telnet <new-ip-address> 443 --> should listen on this port.
(no error message should be thrown)


The same should be happening for the mail-flow too
IMO, nothing needs to be performed @ the IIS server
0
 
Auric1983Commented:
danbrown1888

For the most part changing your external IP's just means updating your Firewall records & MX/DNS records for your domain.

Updating your MX records can take 2-3 days, it may be a lot quicker for some, but it may not be for others.   I always recomend to my clients to perform this change on a Friday so that the DNS changes have time to propogate over the weekend.
0
 
Auric1983Commented:
Another option is to add a second MX record to your domain prior to the switch over pointing to the NEW external IP.  call it mail2.domain.com for the sake of this example.

When you switch over to the new circuit, and change your inbound firewall rules, mail will be delivered to "mail2..."  This is not the best solution as you will still need to update your MX records at a later date.

0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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