OK since the Route command may not be the best way to block a couple of
specific IPs, can someone direct me toward a resource that can help
explain how to use IPSEC to do this without opening a major can of worms
of password authorizations and stuff.

Here's the basic setup. I administrate IIS and O'Reilly Webboard on a
remote computer running Win2K Pro (not Server). IIS handles http on port
80 and FTP on 119/120 and Webboard handles its http on 8080 and SMTP on
25. I do not have any custom user accounts setup on this machine -- just
the basic Administrator and Guest accounts plus normal groups. I login
as Administrator to do anything.

I want to be able to block two static IPs from being able to transact
anything with either IIS or WebBoard. I know I can do it internally on
IIS but WebBoard doesn't have any built-in IP filtering (that I'm aware
of). So I'd prefer to do both at once on a lower level.

So it sounds like IPSEC is the way to go. Help?

Tom

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]