Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Beat to Death by OWA

Posted on 2006-07-20
5
Medium Priority
?
413 Views
Last Modified: 2010-03-06
I am trying to publish Outlook Web Access ( OWA ) from behind a ISA 2004 Sever.

I am beat.  I have tried everything.  There seems to be tons of information on the Internet about setting OWA up, but little about any of the problems I am having…so, I guess it is something extremely easy, and I am just not seeing it.

I have an ISA 2004 Server running on Windows Server 2003.  This server has one external network card, and one internal network card.  The IP address of the internal card is 192.168.1.16.  The name of this machine is Earth.

The Exchange Server 2003 runs on Windows Server 2003.  This machine has one network card.  The IP address of this network card is 192.168.1.14 and 192.168.1.11.  The name of this machine is Venus2.

I have published the website running on IP address 192.168.1.11 through the ISA machine, and it seems to work fine.   People out on the Internet can type www.site.com and can see our website.

However, nothing I do, allows me to publish OWA through the ISA Server.

From a computer on the internal network, I can type “venus2\exchange” and go directly to OWA, or I can type “192.168.1.14\exchange”, enter my password and go to OWA, but as I have said from outside the ISA Server, there is nothing I can do to get to it.  

As for what have I tried so far, the answer is “Everything”.  I have followed every set of instructions on the Internet, I have tried every possible fix on the Internet, and I have randomly tried anything and everything just hoping to luck into some solution…all for nothing.

My hope is that I can get to a point where the users on the Internet would type “http:\\www.site.com” to get to our website, and “https:\\www.site.com\exchange” to get to our OWA.

Does anyone have any ideas on where I would start?  I have been at this for 4 days, and I am getting a little punch drunk.


0
Comment
Question by:jfnewell1965
  • 2
4 Comments
 
LVL 5

Expert Comment

by:rikke_vp
ID: 17150225
Hi,

did you open all the correct ports? 443

Rikke
0
 
LVL 5

Expert Comment

by:rikke_vp
ID: 17150246
0
 

Author Comment

by:jfnewell1965
ID: 17176264
The answer turned out to be that the listener on the ISA server was setup for both port 80 and 443.

I took 443 off of the listener, and created a seperate listener just for OWA on 443.

Seems to work now.
0
 

Accepted Solution

by:
ee_ai_construct earned 0 total points
ID: 17399064
PAQ / Refund
ee ai construct, community support moderator
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

876 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question