This is: 1 - impossible 2 - reflective of poor deployment planning There is no possibility of publishing FWC ports because they're dynamically assigned, much like RPC ------------------------------------------------------- Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/Jim_Harrison/ <http://isaserver.org/Jim_Harrison/> http://isatools.org <http://isatools.org/> Read the help / books / articles! ------------------------------------------------------- ________________________________ From: Derbyshev Igor [mailto:derbyshev@xxxxxxxx] Sent: Thursday, August 04, 2005 02:05 To: [ISAserver.org Discussion List] Subject: [isalist] Publishing FW Client ports http://www.ISAserver.org Hello! We have an ISA Server 2004 computer, which is used as a project server (not production) for application filter development. Its external interface looks into our internal network. It would be handy for us if people could connect to it directly through firewall client from our internal network (external for ISA), for testing purposes. I think this can be done by server publishing FW Client ports to ISA internal interface. What ports/protocols need to be published in this case? Is this possible at all? Thanks. Best regards, Igor Derbyshev E-Mail : derbyshev@xxxxxxxxxxxxxx <mailto:iderbyshev@xxxxxxxxxxxxxx> ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx All mail to and from this domain is GFI-scanned.