Locking Down Services

Why don't you start with the "Security Operations Guide for Windows 2000 Server" manual. It is 7 chapters long, with several appendicies, and some scenarios. You can download it here:

http://www.microsoft.com/downloads/release.asp?releaseid=37123
(please remove any spaces)

hope this helps

I can tell you how to do it but I need to know...

Exactly what should they and should they not be able to access?

Agree with the counterquestions about more detail. Just an addition: ISA, or any other firewall, is _not_ the kind of tool which helps in this directly. It can filter or block certain TCP/IP actions, but it cannot filter on the basis what people do once they have (legally!) made a connection with your W2K box for certain rightful purposes as long as they stay inside the same IP port. So locking down inside the W2K box is a better way to go, based on the counterquestions and the MS guidelines you should be able to find a good path in this.

Hope thiz helpz,

- The Netherlandz

Additional info: The person should be able to perform as an account op or server op. They should not be able to discover any other network resources; they should not be able to map to any other devices; they should not be able to perform any function outside of the server they attach to.

Answer 1 web site has move it is now
http://www.microsoft.com/technet/treeview/default.aspurl=/technet/security/prodtech/windows/windows2000/staysecure/secops01.asp

This question was closed by the author