RE: ISA 2004 opening ports

  • From: "Geldrop, Paul van" <paul.van.geldrop@xxxxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Wed, 18 Jan 2006 21:55:19 +0100

I just wailed and gnashed somebody else's teeth.. quietly.
Zen is a wonderful thing!
 
 
(now let's see if we can get Tom to do the same when somebody asks about 
unihomed ISAs...)
________________________________

From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx]
Sent: Wed 18-1-2006 19:08
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: ISA 2004 opening ports



http://www.ISAserver.org

You're right! I'm remiss at getting infuriated!!!!

Looks like John has us covered here :)

Thomas W Shinder, M.D.
Site: www.isaserver.org
Blog: http://spaces.msn.com/members/drisa/
Book: http://tinyurl.com/3xqb7
MVP -- ISA Firewalls
**Who is John Galt?**



> -----Original Message-----
> From: Alexandre Gauthier [mailto:gauthiera@xxxxxxxxxxxxxxxxx]
> Sent: Wednesday, January 18, 2006 11:32 AM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: ISA 2004 opening ports
>
> http://www.ISAserver.org
>
> I'm really surprised nobody got infuriated by the terms
> "opening a port"
> yet. Or maybe you guys are just being subtle about it, but
> that would not
> match the behavioural pattern I have observed here so far ;P
>
> -----Message d'origine-----
> De : Jim Harrison [mailto:Jim@xxxxxxxxxxxx]
> Envoyé : 18 janvier 2006 11:49
> À : [ISAserver.org Discussion List]
> Objet : [isalist] RE: ISA 2004 opening ports
>
> http://www.ISAserver.org
>
> Yep - it was a bug in the FTP app filter.
> I *believe* we solved it in SP2, but I'm not using that bug
> database any
> more...
>
>
> -------------------------------------------------------
>    Jim Harrison
>    MCP(NT4, W2K), A+, Network+, PCG
>    http://isaserver.org/Jim_Harrison/
>    http://isatools.org
>    Read the help / books / articles!
> -------------------------------------------------------
> 
>
> -----Original Message-----
> From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx]
> Sent: Wednesday, January 18, 2006 08:44
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: ISA 2004 opening ports
>
> http://www.ISAserver.org
>
> Hey Jim,
>
> Yes, I recall that was a big problem for FTP publishing. For
> some reason,
> the secondary connection didn't "take" :)
>
> Thomas W Shinder, M.D.
> Site: www.isaserver.org
> Blog: http://spaces.msn.com/members/drisa/
> Book: http://tinyurl.com/3xqb7
> MVP -- ISA Firewalls
> **Who is John Galt?**
>
> 
>
> > -----Original Message-----
> > From: Jim Harrison [mailto:Jim@xxxxxxxxxxxx]
> > Sent: Wednesday, January 18, 2006 10:28 AM
> > To: [ISAserver.org Discussion List]
> > Subject: [isalist] RE: ISA 2004 opening ports
> >
> > http://www.ISAserver.org
> >
> > Actually, there was an issue with ISA 2000 where server publishing
> > didn't work if you didn't have a corresponding outbound rule.
> > Freakishly difficult to repro, but reported by more than a few
> > customers...
> >
> > -------------------------------------------------------
> >    Jim Harrison
> >    MCP(NT4, W2K), A+, Network+, PCG
> >    http://isaserver.org/Jim_Harrison/
> >    http://isatools.org
> >    Read the help / books / articles!
> > -------------------------------------------------------
> > 
> >
> > -----Original Message-----
> > From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx]
> > Sent: Wednesday, January 18, 2006 07:48
> > To: [ISAserver.org Discussion List]
> > Subject: [isalist] ISA 2004 opening ports
> >
> > http://www.ISAserver.org
> >
> >
> > Hey guys,
> >
> > I hope I wasn't too harsh with this:
> >
> > ISA 2004 opening ports:
> > http://forums.isaserver.org/m_2002003879/mpage_1/key_/tm.htm#2
> > 002003992
> >
> > Thomas W Shinder, M.D.
> > Site: www.isaserver.org <http://www.isaserver.org/>
> > Blog: http://spaces.msn.com/members/drisa/
> > Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> MVP
> > -- ISA Firewalls **Who is John Galt?**
>



This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

Other related posts: