Re: Opening Port doesn't seem to work
From: cjobes (cjobes_at_nova-tech.org)
Date: 06/04/04
- Next message: Chotie: "Why cant i get publishing of website to work?"
- Previous message: JEK: "W3proxy"
- In reply to: A Klimkin: "Re: Opening Port doesn't seem to work"
- Next in thread: Phillip Windell: "Re: Opening Port doesn't seem to work"
- Reply: Phillip Windell: "Re: Opening Port doesn't seem to work"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Jun 2004 09:16:37 -0400
Thanks Andrew,
That clarified it. I did a search in the help for "opening ports" etc but
didn't get anything that would help. I knew I was misunderstanding a basic
principle.
Thanks again for you help
Claus
"A Klimkin" <aklimkin at mail dot ru> wrote in message
news:OYlko%23fSEHA.2544@TK2MSFTNGP10.phx.gbl...
> IP packet filters are unable to allow clients internet access anyhow. They
> designed to control internet access from/to ISA server itself and DMZ
> segment in tri-homed configuration (this is not your case).
> To grant internal clients access to the external hosts over some custom
> protocol you have to create appropriate protocol definition (under Policy
> Elements / Protocol Definitions), then configure the allow protocol rule
> based on just created protocol definition.
> For details see ISA server help.
>
> Regards,
> Andrew
>
> "cjobes" <cjobes@nova-tech.org> wrote in message
> news:OL63vWdSEHA.3932@TK2MSFTNGP10.phx.gbl...
> > Hi all,
> >
> > We have a SBS2000 with ISA sitting behind a firewall. The public NIC is
> > plugged into the DMZ. All clients in the LAN connect through the ISA to
> the
> > Internet.
> >
> > We need to make port 4750 for TCP available for all clients to run a
> > specific web application from an outside source. We configured the
> firewall
> > to let TCP through port 4750 into the DMZ. We tested the application
from
> > the DMZ and it worked fine.
> >
> > We then created a custom filter on the ISA to allow TCP through port
4750
> in
> > both directions. When clients connect, the application fails with a
socket
> > error that according to the originator of the app indicates that the
port
> is
> > not open.
> >
> > Does anybody have any idea what is going on? What are we missing here?
> >
> > Any help would be very much appreciated.
> >
> > Claus
> >
> >
>
>
- Next message: Chotie: "Why cant i get publishing of website to work?"
- Previous message: JEK: "W3proxy"
- In reply to: A Klimkin: "Re: Opening Port doesn't seem to work"
- Next in thread: Phillip Windell: "Re: Opening Port doesn't seem to work"
- Reply: Phillip Windell: "Re: Opening Port doesn't seem to work"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|