Welcome to ISAserver.org

The Kai Wilke publishing method with X owa

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Exchange Publishing >> The Kai Wilke publishing method with X owa

Page: [1]

Message

<< Older Topic Newer Topic >>

The Kai Wilke publishing method with X owa - 11.Jun.2004 8:26:00 AM

fesnouf@hotmail.com

Posts: 64
Joined: 14.Jan.2002
From: Paris
Status: offline

Guys,

I try to implement the Kai Wilke to publish owa+the authentication filter.
This is described on ISASERVER.org

My contect is a bis special. One ISA 2004 RC Refresh locate on the
headquarter site. This company has 12 remote site with 1 exchange per site.

The the idea is to installe a certificate on the external nic with name
*.company.com. Then, each site will have DNS name such as
OWASite1.company.com, OWASite2.company.com ...etc

So my question is : according to this method, we do a double bridging (
External ->Localhost->ExchangeServer).

Q1 : with this context, can I use this method.

On ISA 2000, when we want to make a bridging with 2 HTTPS tunnels, we must
keep the same name on both sides (that is why we had the name in the HOSTS
file with the IP of the exchange).
Q2 : with Linux machine we don't have this constraint (we can do the 2nd
part of the bridging with the IP of the Exchange server for example), does
ISA 2004 a little bit more 'tolerant'

Q3 : Which certificate do I have to install on the LocalHost listener. I
imagine *.company.com (otherwise I will only be able to publish 1
name -OWAsite1.company.com)...
Q3.1 : do you confirm
Q3.2 : do I have to install 2 '*.company.com', 1 for the external
and one for the localhost .. or can I use the same.

If you can advise me that would be great.

Thanks a lot.

Fred

Post #: 1

Featured Links*

RE: The Kai Wilke publishing method with X owa - 11.Jun.2004 3:24:00 PM

tshinder

Posts: 47659
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi Fred,

Inline...

Q1 : with this context, can I use this method.

On ISA 2000, when we want to make a bridging with 2 HTTPS tunnels, we must
keep the same name on both sides (that is why we had the name in the HOSTS
file with the IP of the exchange).
Q2 : with Linux machine we don't have this constraint (we can do the 2nd
part of the bridging with the IP of the Exchange server for example), does
ISA 2004 a little bit more 'tolerant'

Q3 : Which certificate do I have to install on the LocalHost listener. I
imagine *.company.com (otherwise I will only be able to publish 1
name -OWAsite1.company.com)...
==>The certificate on the Local Host network only requires that you have a common name on it that matches the redirect you use in the redirect from the external interface Web listener. That is the only requirement, so you have a lot of options.

Q3.1 : do you confirm
==>Confirm what?

Q3.2 : do I have to install 2 '*.company.com', 1 for the external
and one for the localhost .. or can I use the same.
==>wildcard cert on the external interface Web listener. Specific common names on the Local host Web listener and the internal Web site's Web site.

HTH,
Tom

(in reply to fesnouf@hotmail.com)

Post #: 2