Exchange 2000 is running proerly now (sigh of relief). So I know the secureNAT is operating properly.

Currently:
My ISP translates www.domain.com to my firewall x.x.x.42. This firewall is just a linux box forwarding ports. x.x.x.42/80 ---> 10.10.10.2/80 (ip of web server). I have connected ISA (x.x.x.44)on the same hub as linux which in turn is connected to my router. If the web publishing was set up correctly, I should be able to get to my site via http://x.x.x.44/80, right?

This is what I've done so far:
Destination set: www.domain.com-->10.10.10.2
Do I need a path?
Published Server: x.x.x.44 --> 10.10.10.2 HTTPS Server (I know this isn't right)
Web publishing rules: ?

Could someone help me out here.
Thanks Chris

First, you should consider making the ISA Server your firewall, since that's what its made to do

You should have "www.domain.com" resolve to the external IP address of the ISA Server. By default, the external listener (Inbound Web Requests Listener)will default to port 80, but you can change that if you like.

Next, create a destination set for "www.domain.com". That is exactly what you should enter when you create the destination set. Click the option button for "destination" and in the text box type "www.domain.com".

When you publish the web site, use this destination set.

HTH,
Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

Thanks Tom,
Chris

Let us know how it worked out!

Thanks

Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

ISA Ext address: x.x.x.42
ISA Int address: i.i.i.1
Web Srv sddress: i.i.i.2

ISP's DNS resolves www.domain.com to x.x.x.42

Created Destination set: www.domain.com to destination www.domain.com
(also tried dest = i.i.i.2)

Created web publishing rule:
to got to destination www.domain.com

I checked my internal DNS. Clients can resolve www.domain.com to the local web server. But only when they auto detect settings in IE, not when configured as SecureNAT clients.

SecureNAT gets the following error on internal client:
10061 - Connection refused
Internet Security and Acceleration Server
*Background:
The server you are trying to access has refused the connection with the gateway. This usually results from trying to a service that is inactive on the server.

I was optomistic on this attempt, because this seems so easy to set up. But I still can't get anywhere.

Any Ideas?
Chris

Another thing I was concerned with was the web access for Exchange 2000. When users log on, they use their browsers to go to www.domain.com/exchange. This web access is a folder within the default web site on IIS. Wondering if any one had to use any special settings?

[This message has been edited by clynn (edited 26 February 2001).]

[This message has been edited by clynn (edited 26 February 2001).]

Nevermind, listener was not configure. I knew it was something stupid. For anyone reading this with a similar problem, the listener can be configured by right clicking the server in ISA Manager. Go to properties, click the tab, "incoming web requests"

[This message has been edited by clynn (edited 26 February 2001).]

Ha! Good to see you got it figured out. BTW, I wrote an article about some of the things you should do prior to publishing a web site. Check it out at:
www.isaserver.org/shinder

It might be helpful in making sure all the "pre flight" is done before doing the actual publishing.

HTH,
Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/