Microsoft Proxy Server is not just a HTTP based proxy.
It has a rather unique piece of technology call Winsock proxy that
splits the winsock dll in two.
half runs on the clients, half on the server (OK so it's not strictly
accurate, but you get the idea),
the two halves are connect via a named pipe.
This means that if your running say only IPX internally you can have
your clients connect to the internet
(for ANY service) and still use only one IP address.
You can even set up servers behind the Proxy Server, so applications
like SMTP can operate on another machine.
It works VERY well and is well worth the cost, and for the most part the
small cost of proxy server is irrelevant
to organisations who are already running NT and have already invested in
client access licences for NT.
Linux or BSD currently don't have any technology that comes close.
We currently have the Proxy Server 2.0 <---> FW-1 combination running
where I work, if anyone would like to email me
directly at lmcintos @
au with any specific questions I would
be happy to try and answer them.
P.S Not I don't hold any Microsoft stock - I'm just impressed with the
On Wednesday, 28 January 1998 1:03, Peter da Silva
> > > >I have a client that wants to integrate Proxy Server 2.0 to mask
> > > >user IP address from the FW-1 Unit. This way he can save on the
> > > >user license. Has anyone run into issues with this type of
> > > >configuration.
> Talk about going to an awful lot of trouble for little gain.
> If you're going for an HTTP-proxy-only instead of a filter why not
> the firewall-1 completely and stick a squid on a nailed down FreeBSD
> Linux box between yourself and the Internet? You'd save even more