OWA publishing problem

[johnar]

I am having problems publishing an Exchange server behind ISA - I have followed several MS docs and everything should be set up OK but when I try to access OWA using "w.y.y.z/exchange" (where w.x.y.z is the external IP address of the ISA) from an external client I simply get 'page cannot be displayed' or 'server not found' errors.

If I use w.y.y.z/exchange on the ISA server itself then it works OK which, to me, suggests that publishing is working up to a point.

I can ping the external address of the ISA and can also connect through Terminal Services and can telnet into ports 110, 25

Any suggestions welcome.

Thanks

 

[lck092580]

I remember seeing an article with a step by step tutorial on how to do it.. i think i saw it here:

http://www.msexchange.org

have a look.

Hope this helps.

Good Luck

T

 

[theboys]

I have the sam problem and also seem to get the same results even setting it up in the lab

any ideas

 

[lck092580]

Sorry I meant to put another link.

Try this:

http://www.isaserver.org

T

 

[JDooley]

Also make sure you are using the URL:

http://w.y.y.z/exchange/

Making sure to put the trailing slash on the address.

This is silly, and you may have tried it that way already, but it bit me the first time I published OWA.

JD

 

[noeleon]

Try checking server publishing rules-destination set of ISA

noeleon

 

[pgalore]

I CAME ACROSS THESE POSTS, THEY MAY HELP! -S

HANDLE: KPI
POSTED ON: Sep 26, 2002

REPLY:
I 'solved' my problem today. But in order for my users to have continuous access to their web based mail, I had to turn off the 'authenticate unknown users' feature in the incoming web request properties of ISA. Now I am not as secure, but my users are not screaming at me. It turns out that ISA was blocking their requests after 60 seconds, even though I had the TTL set to 240 seconds. So I have to now find a way to get the authentication working. The quest continues.
-------------------------------------------------------------------

HANDLE: HowardL
POSTED ON: Sep 30, 2002

REPLY:

I managed to solve my problem on Friday. I added a packet filter to ISA allowing all HTTP traffic through port 80. Users have to enter in ID, password & domain, and this allows Web Outlook to open. I was amazed how quick it is!

I also changes the default IP address under IIS to the external network card, as it was set to "all unassigned"

The only problem I can see is that most attackers would scan port 80 by default, so my next step is to only open up 1 port (random) and change this in IIS. Users could then access by typing the port in the URL. Phew!

 

[Knutern]

When you pubish OWA from behind an ISA server, it is important that you create a WEB-Server publishing rule which knows with whom to communicate. Also, VERY important is that you have created a destination set containing following entries:
/exchange*
/exchweb*
/public*

The destination set is to be used with your web-publishing rule. Remove /public* if you do not intent to publish your public folders.

Hope this helps. If not please let me know either way.