Comments on: cannot connect to PIX Firewall via ISA Proxy server using ASDM Launcher http://itknowledgeexchange.techtarget.com/itanswers/cannot-connect-to-pix-firewall-via-isa-proxy-server-using-asdm-launcher/ Fri, 27 Nov 2009 00:25:11 +0000 http://wordpress.org/?v=2.6.2 By: RonP http://itknowledgeexchange.techtarget.com/itanswers/cannot-connect-to-pix-firewall-via-isa-proxy-server-using-asdm-launcher/#comment-65403 RonP Sun, 12 Jul 2009 16:43:43 +0000 #comment-65403 Great..Thx..Another issue I discovered is the ISA Server is on a much lower security, and as such, static routes needed to be established to and back from the "inside interface"..Port Number Configuration info was bang on..!! Great..Thx..Another issue I discovered is the ISA Server is on a much lower security, and as such, static routes needed to be established to and back from the “inside interface”..Port Number Configuration info was bang on..!!

]]> By: RonP http://itknowledgeexchange.techtarget.com/itanswers/cannot-connect-to-pix-firewall-via-isa-proxy-server-using-asdm-launcher/#comment-65307 RonP Thu, 09 Jul 2009 15:29:08 +0000 #comment-65307 Yes, HTTP Server is enabled on the PIX. At this point, I believe the source of the problem may be with the port I'm using to start outbound HTTP sessions in my browser (I.E. 7). I just discovered all outbound browser connections are being established with the Proxy Server (ISA) on Port 8080. If I speciifically add the PIX Inside Interface (IP Address) to the list of "Exceptions" in my browser, thereby avoiding the ISA entirely, the Cisco ASDM Launcher [B]works[/B]. This tell me both the PIX and my workstation (i.e. Java components, etc) have been configured properly and no problems exist at the foundation level. So, in essence, my question really is how I can leverage the ISA Proxy Server to allow/process traffic both to the PIX interface and back to my workstation via Cisco's ASDM Interface using Port 8080? If this can't be done, then I'll continue to exclude the Proxy from these sessions in my browser. Was merely wondering if there was a workaround. Can the PIX "HTTP Server" option be configured to use a different Port once enabled on the interface??? Thx. Yes, HTTP Server is enabled on the PIX. At this point, I believe the source of the problem may be with the port I’m using to start outbound HTTP sessions in my browser (I.E. 7). I just discovered all outbound browser connections are being established with the Proxy Server (ISA) on Port 8080. If I speciifically add the PIX Inside Interface (IP Address) to the list of “Exceptions” in my browser, thereby avoiding the ISA entirely, the Cisco ASDM Launcher works. This tell me both the PIX and my workstation (i.e. Java components, etc) have been configured properly and no problems exist at the foundation level.

So, in essence, my question really is how I can leverage the ISA Proxy Server to allow/process traffic both to the PIX interface and back to my workstation via Cisco’s ASDM Interface using Port 8080? If this can’t be done, then I’ll continue to exclude the Proxy from these sessions in my browser. Was merely wondering if there was a workaround. Can the PIX “HTTP Server” option be configured to use a different Port once enabled on the interface??? Thx.

]]>