RE: Quick Question on OWA setup...DSL
- From: "Steve Moffat" <steve@xxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 19 Oct 2004 15:29:03 -0300
Are you trying to access the https site from behind ISA?? What's the
domain name and I'll try from here?
S
-----Original Message-----
From: Marvin Cummings [mailto:MarvinC@xxxxxxxxx]
Sent: Tuesday, October 19, 2004 2:01 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Quick Question on OWA setup...DSL
http://www.ISAserver.org
Being that you do cover such a wide range of scenarios on the site and
in your books I think it would be greatly appreciated by those of us
that use this setup to have an aritcle or two dedicated to this setup.
What you'd be doing is expanding on the TZO packet filters article that
you have listed on the site and preceeding the articles you have on
publishing the OWA. So if you have the time by all means, hook us up.
:-)
You wrote:
> If you're using DDNS (TZO etc) the public address on the DSL NAT
> device will accept the incoming requests for the OWA site and will
> forward them to the ISA firewall's Incoming Web Requests Listener. So,
> the Web Publishing Rule just needs to be configured to accept incoming
> connection requests for the FQDN the remote users use to access the
> site
I went and deleted the listener I had for the internal IP and configured
the web server listener as follows:
1. Checked "Use a server certificate to authenticate to web clients"
box and selected the FQDN the users will use to connect to the OWA site.
2. Checked the "Bsic with this domain" box and selected my domain.
3. Made sure the "Enable SSL listeners" box was checked.
4. Published ports 25 & 80 on the linksys router/NAT device.
I can access the OWA site internally but not externally. What steps am I
missing?
TIA
On Tue, 19 Oct 2004 10:36:58 -0500, Thomas W Shinder
<tshinder@xxxxxxxxxxx> wrote:
> http://www.ISAserver.org
>
> Hi Marvin,
>
> If you're using DDNS (TZO etc) the public address on the DSL NAT
> device will accept the incoming requests for the OWA site and will
> forward them to the ISA firewall's Incoming Web Requests Listener. So,
> the Web Publishing Rule just needs to be configured to accept incoming
> connection requests for the FQDN the remote users use to access the
> site.
>
> Do you think we need an article on ISAserver.org or in the book on how
> to do this? Is this a common scenario? (I guess I answered my own
> question, since both you and I use this type of setup :-))
>
> Thanks!
>
>
>
> Tom
> www.isaserver.org/shinder
> Tom and Deb Shinder's Configuring ISA Server 2004
> http://tinyurl.com/3xqb7
> MVP -- ISA Firewalls
>
> -----Original Message-----
> From: Marvin Cummings [mailto:MarvinC@xxxxxxxxx]
> Sent: Tuesday, October 19, 2004 10:03 AM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: Quick Question on OWA setup...DSL
>
> http://www.ISAserver.org
>
> Let me restate the question and problems I'm having:
> Setup: DSL on ISA 2000 behind linksys router. The external interface
> is a private IP of 192.168.1.x.
> Question: how to publish OWA and multiple servers over a DSL
connection?
>
> Problem: web server is currently published as listener for external
> IP. This means ISA doesn't see any more external IP addresses. I can
> access web sites externally.
> Problem: ISA didn't see the external interface so I configured it to
> listen on the IP of the internal interface. I'm still unable to access
> the OWA externally.
> Problem: unable to publish mail server because ISA doesn't see any
> external IP addresses.
>
> #%@#!!!
>
> Qestion: What must I do to enable ISA to allow me to publish multiple
> servers on this external interface?
> Any responses are appreciated.
>
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
> ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
> ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> World of Windows Networking: http://www.windowsnetworking.com Leading
> Network Software Directory: http://www.serverfiles.com
> No.1 Exchange Server Resource Site: http://www.msexchange.org Windows
> Security Resource Site: http://www.windowsecurity.com/ Network
> Security Library: http://www.secinf.net/ Windows 2000/NT Fax
> Solutions: http://www.ntfaxfaq.com
> ------------------------------------------------------
> You are currently subscribed to this ISAserver.org Discussion List as:
> marvinc@xxxxxxxxx To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=isalist
> Report abuse to listadmin@xxxxxxxxxxxxx
>
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org Windows
Security Resource Site: http://www.windowsecurity.com/ Network Security
Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
steve@xxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx
This E-Mail is confidential. It is not intended to be read, copied, disclosed
or used by any person other than the recipient named above.
Unauthorised use, disclosure, or copying is strictly prohibited and may be
unlawful. Optimum IT Solutions Ltd disclaims any liability for any action taken
in connection of this E-Mail. The comments or statements expressed in this
E-Mail are not necessarily those of Optimum IT Solutions Ltd or its
subsidiaries or affiliates.
administrator@xxxxxxxxxx
Other related posts:
