Hi Thomas, So, by using the network templates this would be the "Back" template? How does this really differ then from the "Front" template? They both work with the back to back network setups. Thank you, Joseph -----Original Message----- From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] Sent: Sunday, September 19, 2004 11:50 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: Error Code: 502 Proxy Error http://www.ISAserver.org Hi Idan, I'd fix this network topology. Remember, you want your most secure firewall closest to the network assests -- so you need to move the Checkpoint server to the edge of the network and move the ISA firewall closest to the corporate assets. You can do this by using the back to back firewall config, where the Checkpoint Server is in front of the ISA firewall. In that way, the Checkpoint Server can perform the basic stateful filtering, and the ISA firewall on the back-end can provide both stateful filtering and stateful application layer inspection. HTH, Tom _____ From: Idan Plotnik [mailto:idan@xxxxxxxxxxxxxxx] Sent: Sunday, September 19, 2004 1:24 PM To: [ISAserver.org Discussion List] Subject: [isalist] Error Code: 502 Proxy Error http://www.ISAserver.org Hi all, I created a test environment for knowing all of ISA architectures and this is one of my infrastructures: Client -> CheckPoint -> ISA PROXY -> Internet The checkpoint and the ISA server are in the same segment (172.10.X.X) and the client is in other segment (10.0.0.X). I don't know if you familiar with the HTTP Mapping feather in CP but this allow me to redirect http traffic from one source to another destination and play with the source and the destination ports, when I am doing so I can see the packets come into the ISA Proxy server but I am getting this error at the browser client. Technical Information (for support personnel) * Error Code: 502 Proxy Error. The Uniform Resource Locator (URL) does not use a recognized protocol. Either the protocol is not supported or the request was not typed correctly. Confirm that a valid protocol is in use (for example, HTTP for a Web request). (12006) Any clue ? Thanks a lot. ------------------------------------------------------ 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 ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx ------------------------------------------------------ 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 ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: josephk@xxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx