OWA not working after installing and configuring new router w/ new outside ip address

I recently setup Exchange 2003 SP2 and it was working fine, including POP3, OWA and other services.  I had to install a new firewall / router and was required to change the outside ip address as well (gotta love comcast).  After I setup the new router I created the standard port forwardes for 25, 110, 80, 443 and others that we need.  I have port 80 & 443 (although we are not using a ssl yet) to forward to our exchange server.  
after i put in the new router with the new wan ip address, i am unable to access owa from the outside.  browser says it can't find the page htt://xxx.xxx.xxx.xxx/exchange.  it worked fine before installing the new router.
are there any settings in IIS or Exch 2003 that I need to change since I installed the new router.

I've checked the forwarding rules and they seem to working.
jvandewayAsked:
Who is Participating?
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.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Whenever you modify anything having to do with your WAN or LAN configuration on an SBS you need to run the Configure Email and Internet Connection Wizard (CEICW -- which is linked as Connect to the Internet in the Server Management Console > To-Do List)

A visual how-to is here:  http://sbsurl.com/ceicw and a full networking overview for SBS is at http://sbsurl.com/msicw

Jeff
TechSoEasy
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
jvandewayAuthor Commented:
thank you, i didn't know that, i'll try that in the morning... and get back to you.
0
SarahWHCommented:
Have you amended your domains MX records to reflect the change in external IP?  This would be a reason why you would not be able to connect using the fully qualified domain name - but you should be able to connect using the IP address?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

jvandewayAuthor Commented:
ive reran the setup suggested by TechSoEasy and restarted IIS and related services and MSE Information Store just in case.  OWA works internally and I've verified the rules on our router.  But when I type in the following http://xxx.xxx.xxx.xxx/exchange it bombs out.

All MSE and IIS Admin Service are running properly.

Any ideas?
0
LeeDerbyshireCommented:
Couple of things that might help to diagnose the problem.  Can you reach the Default Web Site at http://xxx.xxx.xxx.xxx (without the /exchange)?  Also, look at your IIS logs to see if the requests are actually reaching the server.  The IIS logs are in C:\Windows\System32\Logfiles\W3SVC1 .
0
jvandewayAuthor Commented:
Yes i can get to the default website, at http://xxx.xxx.xxx.xxx that is how I know that port 80 is forwarding properly.  I also have port 443 forwarding for when we do get a certificate.  I'll check the iis logs get repost.
0
jvandewayAuthor Commented:
what am i looking for in the logs mentioned
0
LeeDerbyshireCommented:
Look for the logged GET requests to /Exchange.  Your error message says that it "can't find the page".  This means one of two things - either the requests aren't even reaching the server; or the requests /are/ reaching the server, but the response isn't reaching the client.  If you can see GET requests to /Exchange (note that the times are in GMT), then you will at least know whether the client requests are reaching the server, or not.
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Please try using https://xxx.xxx.xxx.xxx/exchange (instead of just http).

If you disable port 80, in the CEICW, you would not have to specifically use https because the http would automatically fall over to port 443.  Generally I recommend that you don't have port 80 open on an SBS.

Jeff
TechSoEasy
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
Microsoft Legacy OS

From novice to tech pro — start learning today.

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.