Desperate for help - doing IP Mapping
- From: "Michael Anderson" <mike@xxxxxxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Sat, 1 Jun 2002 15:58:25 -0500
Hello,
We have an internal web server that runs on a private 192 number. This
server must remain behind the firewall - so I need to use mapping (if
that is the proper term to use) to allow HTTP requests to come in
through our ISA server's external interface, and be forwarded on to our
internal 192 number.
I tried everything under the sun - with no success whatsoever.
First of all, I created an IP Packet Filter to allow Port 80 TCP
requests to be let in. First of all I should verify that it was set up
correctly. Here are the settings:
Name: Web Access
Mode: Allow
Filter Type: Custom Filter
Local Computer: Default external IP address
Remote Computer: Any
Protocol: TCP
Direction: Both
Local Port: 80
Remote Port: All ports
THEN, in order for the IP Mapping to work properly, I created the
following entry under the Web Publishing Rules (if that's even what I
want???):
Destinations: All internal destinations
Action: Redirect the request to this internal web server
(192.168.1.110)
Connect this port when bridging request at HTTP: 80
Connect this port when bridging request at SSL: 443
Connect this port when bridging request at FTP: 21
Redirect HTTP requests as : HTTP requests
Redirect SSL requests as : SSL requests
Applies to : Any request
Now I am just guessing on how to do this - and I could be way off course
here, with what I have tried thus far.
Could someone please tell me if I am on the right track here? And if
not, what I need to do, in order to make this work properly?
Thanks in advance for all your help,
Mike
Other related posts:
