[isapros] Re: Firewall client publishing

  • From: "Steve Moffat" <steve@xxxxxxxxxx>
  • To: <isapros@xxxxxxxxxxxxx>
  • Date: Fri, 19 May 2006 14:26:53 -0300

Don't be deliberately stoopid....:), I meant, whether it was or was not
supported. Probably my grammar at fault there.

-----Original Message-----
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Jim Harrison
Sent: Friday, May 19, 2006 2:16 PM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: Firewall client publishing

Actually, I haven't tried it and no, it's not supported (stated in my
first response, yanut)... 


-------------------------------------------------------
   Jim Harrison
   MCP(NT4, W2K), A+, Network+, PCG
   http://isaserver.org/Jim_Harrison/
   http://isatools.org
   Read the help / books / articles!
-------------------------------------------------------
 

-----Original Message-----
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Steve Moffat
Sent: Friday, May 19, 2006 09:47
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: Firewall client publishing

Well then, does it work, or does it not work.....unsupported or not? And
don't say you haven't tried it...:)

-----Original Message-----
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Jim Harrison
Sent: Friday, May 19, 2006 1:32 PM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: Firewall client publishing

There were rumors to that effect, but I squashed them pretty quickly. 

You're absolutely correct; installation of the FWC (or wsp client in P2
terms) with judicious application of wspcfg.ini was the method of choice
for P2 and was functional (and supported) in ISA 2000.
Unfortunately, this methodology was not tested for ISA 2004 (time
limitations) and therefore fell of the "supportability' wagon...

-------------------------------------------------------
   Jim Harrison
   MCP(NT4, W2K), A+, Network+, PCG
   http://isaserver.org/Jim_Harrison/
   http://isatools.org
   Read the help / books / articles!
-------------------------------------------------------
 

-----Original Message-----
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx]
On Behalf Of Thor (Hammer of God)
Sent: Friday, May 19, 2006 08:37
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: Firewall client publishing

Wasn't it called "reverse proxy" or "reverse publishing" back then?  You
had to install the client (like Jason said) and tag an entry in the
WSPCLNT.INI or something where you specified the port/service to
remotely bind the port to the external interface of the Proxy 2.0 box.
I used that all the time it seems... 

Jim, you should fire it up... Rumor has it that you have an original
boxed set of Proxy 2.0 lying around.  Could that be true?

t


On 5/19/06 6:46 AM, "Jim Harrison" <Jim@xxxxxxxxxxxx> spoketh to all:

> Perzactamundo.
> 
> Technically it *may* still function, but if it blows up or acts oddly,

> CSS will tell you to undo it.
> 
> 
> -----Original Message-----
> From: isapros-bounce@xxxxxxxxxxxxx
> [mailto:isapros-bounce@xxxxxxxxxxxxx]
> On Behalf Of Jason Jones
> Sent: Friday, May 19, 2006 5:28 AM
> To: isapros@xxxxxxxxxxxxx
> Subject: [isapros] Re: Firewall client publishing
> 
> I remember doing this in the old proxy 2.0 days by installing the WSP 
> on Exchange servers and then configuring local bind ports...haven't 
> had the need to do it in ages - what you specifically trying to do
Tom?
>  
> 
> Jason Jones | Silversands Limited | T: 01202 360489 | M: 07971 500312
> |
> F: 01202 360900 | E: jason.jones@xxxxxxxxxxxxxxxxx 
> <mailto:jason.jones@xxxxxxxxxxxxxxxxx>
> 
>  
> 
> ________________________________
> 
> From: isapros-bounce@xxxxxxxxxxxxx
> [mailto:isapros-bounce@xxxxxxxxxxxxx]
> On Behalf Of Thomas W Shinder
> Sent: 19 May 2006 12:39
> To: isapros@xxxxxxxxxxxxx
> Subject: [isapros] Re: Firewall client publishing
> 
> 
> NO, that's not it. Its a method you can use to publish servers by 
> installing the Firewall client on the published server and then 
> manipulating the Firewall client configuration files so that you 
> remote and local bind the appropropriate IP addresses and ports on the

> external interface of the ISA firewall.
>  
> Tom
>  
> Thomas W Shinder, M.D.
> Site: www.isaserver.org <http://www.isaserver.org/>
> Blog: http://blogs.isaserver.org/shinder/
> Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> MVP -- ISA 
> Firewalls
> 
>  
> 
> 
> ________________________________
> 
> From: isapros-bounce@xxxxxxxxxxxxx
> [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Mulholland
> Sent: Friday, May 19, 2006 2:25 AM
> To: isapros@xxxxxxxxxxxxx
> Subject: [isapros] Re: Firewall client publishing
> 
> 
> publishing via gp i took it as.. no?
> 
> Greg Mulholland
> 'Security was not considered in the design of this protocol'
> 
> 
> ________________________________
> 
> From: isapros-bounce@xxxxxxxxxxxxx
> [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Moffat
> Sent: Friday, May 19, 2006 2:56 PM
> To: isapros@xxxxxxxxxxxxx
> Subject: [isapros] Re: Firewall client publishing
> 
> 
> 
> What do you mean FW Client publishing?
> 
> 
> 
> S
> 
> 
> 
> ________________________________
> 
> From: isapros-bounce@xxxxxxxxxxxxx
> [mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Thomas W Shinder
> Sent: Thursday, May 18, 2006 10:01 PM
> To: isapros@xxxxxxxxxxxxx
> Subject: [isapros] Firewall client publishing
> 
> 
> 
> Hey guys,
> 
> 
> 
> I recall hearing from one of the devs or maybe the UE team that 
> Firewall Client publishing isn't supported in ISA 2004+ but I don't 
> remember seeing anything on the ms.com site about this.
> 
> 
> 
> Anyone know if this is official or has anyone tried Firewall client 
> publishing?
> 
> 
> 
> Thanks!
> 
> Tom
> 
> 
> 
> Thomas W Shinder, M.D.
> Site: www.isaserver.org <http://www.isaserver.org/>
> Blog: http://blogs.isaserver.org/shinder/
> Book: http://tinyurl.com/3xqb7
> MVP -- ISA Firewalls
> 
> 
> 
> 
> All mail to and from this domain is GFI-scanned.
> 
> 
> 
> 




All mail to and from this domain is GFI-scanned.




All mail to and from this domain is GFI-scanned.



Other related posts: