|
Home > Archive > IIS Server Security > February 2005 > IpSec security
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Guoqi Zheng 2005-02-10, 7:51 am |
| There is an articles on www.microsoft.com/serviceproviders/
columns/using_ipsec.asp, explaining how to use IpSec to lock down a server.
I did what is said on that document. However, it seems to me that IpSec can
only filter traffic based on IP. If I do it based on port, it does not
work... I am using Windows 2003 standard edition.
Am I doing something wrong or IpSec can only wrok on a IP base?
| |
| Miha Pihler [MVP] 2005-02-10, 5:54 pm |
| It can filter based on IP, different protocols (TCP, UDP) and/or their port
numbers...
But I do admit that in most cases, it takes a bit to get the policy right
for it to work :-).
--
Mike
Microsoft MVP - Windows Security
"Guoqi Zheng" <no@sorry.com> wrote in message
news:O0cOv62DFHA.328@tk2msftngp13.phx.gbl...
> There is an articles on www.microsoft.com/serviceproviders/
> columns/using_ipsec.asp, explaining how to use IpSec to lock down a
> server.
> I did what is said on that document. However, it seems to me that IpSec
> can
> only filter traffic based on IP. If I do it based on port, it does not
> work... I am using Windows 2003 standard edition.
>
> Am I doing something wrong or IpSec can only wrok on a IP base?
>
>
|
|
|
|
|