Publish Second website-Driving me crazy
- From: "FrodoBaggins" <email@xxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 14:29:59 -0700
ISA2000 on Win2kSP4. This box sits between internal network and DMZ in a
back to back config with a linux based firewall.
I have OWA2003 published and working fine already. But getting a second
website to work is driving me crazy! Here is what I have:
This box has two physical nics, internal and dmz side. The primary ip
address on the dmz nic is 192.168.0.6. I have also bound 192.168.0.8 to it
as well.
Incoming Web Requests. I have two listeners setup, one for .6 and one for
..8. The listener for .6 is for OWA, so I configured a listener for the
second website on the .8 ip address, no authentication selected or anything
like that. Listeners are set to listen on port 8888.
I created a destination set based on the fqdn that users would use to access
the web page. I created a web publishing rule using this destination set
and set it to forward any requests to an internal web server, also named by
fqdn. ISA has full DNS visibility to this web server.
When I try to connect I get an IE error of DNS error or website not found.
I am making sure to specify port 8888 in my IE request as follows,
http://server.domain.com:8888. I don't get anything in the log files at
all, even if I turn on Log allow packets for the packet filters log.
So I tried going by IP address to see if I had any DNS issues. I changed
the destinaiton set from the fqdn to the ip address 192.168.0.8, and I
changed the internal server specified in the web publishing rule to use the
IP address instead of the fqdn as well. I connect from the client using
http://192.168.0.8:8888. This time I see an entry in the packet filter log
that shows an allowed connectin from the client side to ip address
192.168.0.8:8888. But I still don't get a website. Nothing shows up in the
web proxy log. It seems like the request is hitting the listener, being
accepted, but not making it to the web proxy service. Is there any way I
can map the progress of traffic so that I can pinpoint where it is stopping?
Anyone have any suggestions? In the past when I was trying to get the OWA
working I tried using a different IP address bound to the dmz nic and ended
up with the same results. I just ended up using the default ip address on
the dmz nic becasue OWA was the only web publishing need I had. I feel like
this should be easy, but I can't get it to work!
Thanks
Jeff
.
- Prev by Date: Re: FTP Connecting but no files visible
- Next by Date: Use telnet to access an internal switch from the Internet
- Previous by thread: isa2004 pubish exchange2003 can't use outlook
- Next by thread: Use telnet to access an internal switch from the Internet
- Index(es):
Relevant Pages
|
