RE: Microsoft Proxy 2.0 vs. ISA 2000

[Shawn H. Mesiatowsky]

Title: Microsoft Proxy 2.0 vs. ISA 2000

ISA does Proxy as well as NAT (network address translation). There are two separate methods for sharing an internet connection. NAT does not need any client software to be setup to use a proxy server. You just set the gateway settings in your IP config to point to the NAT server (in this case the ISA server). However, some applications do not work properly with NAT. In this case, the client software needs to be configured to access the Proxy, server, and the proxy settings must be configured properly. I am not sure if ISA supports both socks and Winsocks. With Socks, you only need to set up each client app to access the proxy server. With Winsocks, you need to install the winsocks client in order for everything to work. I read another post mentioning websense and Cisco Pix. Web sense is not required for a pix box, since the Pix box supports NAT. If you only need to access http, smtp, ftp, and some other common protocols, the NAT should be fine, and is much easier to administer. The best bet would be a PIX box in my opinion. $2000 for a simple Pix box, and well worth it! Pix also has the full set of the Cisco IOS commands J   Shawn H. Mesiatowsky   -----Original Message----- From: Goodman, Keith [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 06, 2001 11:40 AM To: NT System Admin Issues Subject: Microsoft Proxy 2.0 vs. ISA 2000   Ok, I asked this question before on another Sunbelt list but didn't get a chance to pay attention to the responses.  This time, I'm gonna ask here and I'll pay attention! :) We're currently using Microsoft Proxy 2.0 for our proxying needs.  However, for everything but HTTP requests and ftp requests through HTTP, Microsoft Proxy 2.0 requires all clients to have Winsock installed before proxying any other requests.  This is obviously undesirable.  My issues are these: 1.) We are looking for a proxy server that does proxying transparently based on only server settings (clients of course will still need to point all apps to the proxy server).  I know there are packages out there that do this, such as the linux version of Apache that our ISP was using when we had ISP functions outsourced.  Can anyone recommend an NT-based package that allows us to not have to install anything on the client side? 2.)  I started looking at Microsoft Internet Security & Acceleration Server 2000 (ISA 2000) as our Microsoft Proxy 2.0 replacement.  Does anyone know if this has the same limitations as Microsoft Proxy 2.0, in that each client has to have a component installed to proxy everything but http and ftp through http requests? Thanks for all responses! http://www.sunbelt-software.com/ntsysadmin_list_charter.htm http://www.sunbelt-software.com/ntsysadmin_list_charter.htm