Relatively straightforward (at first... :-))
1. Install NT4
2. Install SP4
3. Install MSP2.0
4. Enable packet filtering.
Also, you might want to also install the new IIS GET fix, as this
could be used as part of a doS attack against an MSP2.0 server, if
you're using web publishing.
At this point the server should be quite secure against external
interference. However, you'll now need to work out what filters and
access restrictions are needed for the internal LAN users.
The following link might provide more information:
http://www.msproxy.com/
MSP also has quite helpful online documentation. If you're familiar
with NT and IIS, the MSP installation should be quite easy.
Oh, resist all attempts to run anything else on the box, like the
Option Pack (including IIS4). And don't make the MSP box a PDC or BDC
for the NT domain. If anything try placing it in its own domain, with
a one-way trust relationship for user authentication.
Finally, check the MS proxy news group for the latest and and greatest
stories about MSP 2.0. Scrolling back a few messages should give you
some pretty good ideas of what problems you may encounter.
Good luck!
Brian Steele
-----Original Message-----
From: Chris J. Magnuson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Sunday, December 27, 1998 9:34 PM
Subject: MS Proxy Server 2.0
>Yes it is true. A customer wants to use this. It's my job to set it
up
>the best I can.
>
>If anyone can point to any horror stories or helpful tips on this
that
>would be great.
>
>Regards,
>Chris
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
