Re: Server Publishing
- From: "Jim Harrison" <jim@xxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Thu, 2 Aug 2001 10:12:39 -0700
Inline...
Jim Harrison
MCP(2K), A+, Network+, PCG
----- Original Message -----
From: <Thor@xxxxxxxxxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Sent: Thursday, August 02, 2001 09:45
Subject: [isalist] Server Publishing
http://www.ISAserver.org
Greets!
As I understand it, in order to collect the true IP address (as opposed to
the external interface of the ISA server) of a client when visiting a
published (internal) server, we need to use Server Publishing rather than
Web Publishing. (If there is another way, please let me know).
I have a couple of Q's about exactly how to implement this.
First, there is no HTTP protocol mapping in the Server Publishing rules
wizard, so I had to make my own -> TCP 80 Inbound. (There is an HTTP
outbound protocol definition, but this does not show up when doing Server
Publishing; besides, it is outbound.)
So, I then delete my Web Publishing rule, and do a Server Publishing rule to
take requests for the specific external IP address, and redirect it to the
internal IP address for that particular site, specifying the newly mapped
custom Web protocol.
I'm not sure what I am missing, but this does not work. The web site comes
up as "Cannot Be Displayed".
* You need to disable the incoming web listener for the IP that you're
publishing the web site on or else they'll conflict.
I seem to remember seeing an in-depth description of how to do this
specifically, but can't find it.
Any pointers would be appreciated.
---------------------------------
Attonbitus Deus
Thor@xxxxxxxxxxxxxxx
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
