Avatar of bhaf
bhafFlag for United States of America

asked on 

OWA Not Working After Internal IP Address Changes

I just changed our internal (private) IP addresses to prepare for some network changes. Everything is working fine except Outlook Web Access (OWA). We have an extranet set up at https://extranet.companyname.com, and I can log on to this and access our extranet pages, but when I try to go to the OWA portion (https://extranet.companyname.com/exchange), I get a 404 page not found error. This happens whether accessing from internally or externally and whether using URL or using IP address directly.

We have a Windows 2000 Server AD domain, with one Exchange 2000 (SP3) server that contains our mailboxes and another Exchange 2000 SP3 server set up as a front-end just for OWA. The only thing that was changed was the internal IP addresses of the servers. I figure there is some other place where I need to change the IP address, but I've looked around Exchange System Manager and IIS admin console, but haven't found it.

Any ideas?

bhaf
Exchange

Avatar of undefined
Last Comment
bhaf
Avatar of timeshell
timeshell

Do you have a network address translation going on in your firewall that needs to be also updated to reflect the new internal IP address?  
Avatar of bhaf
bhaf
Flag of United States of America image

ASKER

I have a one-to-one NAT translation set up in our firewall so that the public IP address for the extranet (https://extranet.companyname.com) maps to the private IP on the front-end Exchange server. I know this is working because we can access our extranet home page there. It's just when we click our link to OWA (or enter it directly in the URL) that we have the problem.

bhaf
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of bhaf
bhaf
Flag of United States of America image

ASKER

The web site is set to "(All Unassigned)". I tried setting to the specific IP - that didn't work. Tried changing back to unassigned - that didn't work.

I also tried rebooting the machine (which I don't think I did last week when I changed the addresses), but that didn't work. Searched the registry for the old IP address and found nothing.

bhaf
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

You haven't got connection restrictions or anything like that on the server? I have changed IP addresses loads of times and it hasn't caused a problem.

Simon.
Avatar of bhaf
bhaf
Flag of United States of America image

ASKER

I figured it out, and it was just a dumb mistake! The IP address for the Default Web Site on the main Exchange server was still set to the old value. I had been doing all of my checking on the front-end server which was correct. Once I changed it to "All Unassigned", OWA worked again.

Thanks for pointing me in the right direction.

bhaf
Exchange
Exchange

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo