Networking Forums

Networking Forums > Computer Networking > Windows Networking > configuring IPsec...

Reply
Thread Tools Display Modes

configuring IPsec...

 
 
Drazen
Guest
Posts: n/a

 
      01-22-2004, 12:58 PM
Hello to the group,

Is it possible to configure IPsec on Windows 2003 Enterprise
Edition Server so that it accept TCP/IP connection to specified port
only from a list of IP addresses and block all others? For example I
would like to configure IPsec so that it only accepts connections to
port 3389 on the server from clients with IP addresses
192.168.0.100,192.168.0.124...etc.
Also is it possible to filter incoming connections by MAC address
using IPsec? If it is not possible using IPSec, is there another
system built-in way to accomplish that?

Thank you,
Drazen
 
Reply With Quote
 
 
 
 
Joseph Davies [MSFT]
Guest
Posts: n/a

 
      01-27-2004, 07:53 PM
To do what you need, you need to create a local IPSec policy on the server
computer with two rules:

1. Filter action: Permit, Filter List: List of filters for allowed traffic,
each filter is the source IP address of a client with destination TCP port
3389, mirrored
2. Filter action: Block, Filter List: Create a filter list for all traffic,
mirrored

You cannot control access based on MAC addresses using IPSec, which relies
on Internet layer and above protocols to define traffic.

There is no other capability of Windows Server 2003 that allows you to do
MAC-level address filtering.


"Drazen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Hello to the group,
>
> Is it possible to configure IPsec on Windows 2003 Enterprise
> Edition Server so that it accept TCP/IP connection to specified port
> only from a list of IP addresses and block all others? For example I
> would like to configure IPsec so that it only accepts connections to
> port 3389 on the server from clients with IP addresses
> 192.168.0.100,192.168.0.124...etc.
> Also is it possible to filter incoming connections by MAC address
> using IPsec? If it is not possible using IPSec, is there another
> system built-in way to accomplish that?
>
> Thank you,
> Drazen



 
Reply With Quote
 
Assaf Sheep
Guest
Posts: n/a

 
      02-24-2004, 01:21 PM
"Joseph Davies [MSFT]" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> To do what you need, you need to create a local IPSec policy on the server
> computer with two rules:
>
> 1. Filter action: Permit, Filter List: List of filters for allowed traffic,
> each filter is the source IP address of a client with destination TCP port
> 3389, mirrored
> 2. Filter action: Block, Filter List: Create a filter list for all traffic,
> mirrored
>
> You cannot control access based on MAC addresses using IPSec, which relies
> on Internet layer and above protocols to define traffic.
>
> There is no other capability of Windows Server 2003 that allows you to do
> MAC-level address filtering.
>


Hello,

I also have the same problem. what do I need to configure in the
second filter (source and destination) because with the default
configuration all the traffic to the server is blocked !

I'll appricate any help.

Assaf
 
Reply With Quote
 
Mark Swift [MSFT]
Guest
Posts: n/a

 
      03-01-2004, 06:40 PM
The second filter is a "BLOCK all traffic" filter so it is intended to block
all your traffic. The first filter is the filter that is exempted from the
block so that all traffic matching the first filter will be permitted to go
to the server. So configure your first filter (or multiple filters in the
filter list) to specify all traffic that you want to go to the server. We
recommend using the most restrictive filters (down to the protocol and
port). The Help system that came with Windows Server 2003 can walk you
through creating IPSec policy.

--
Mark Swift
--------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Assaf Sheep" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> "Joseph Davies [MSFT]" <(E-Mail Removed)> wrote in message
> news:<(E-Mail Removed)>...
>> To do what you need, you need to create a local IPSec policy on the
>> server
>> computer with two rules:
>>
>> 1. Filter action: Permit, Filter List: List of filters for allowed
>> traffic,
>> each filter is the source IP address of a client with destination TCP
>> port
>> 3389, mirrored
>> 2. Filter action: Block, Filter List: Create a filter list for all
>> traffic,
>> mirrored
>>
>> You cannot control access based on MAC addresses using IPSec, which
>> relies
>> on Internet layer and above protocols to define traffic.
>>
>> There is no other capability of Windows Server 2003 that allows you to do
>> MAC-level address filtering.
>>

>
> Hello,
>
> I also have the same problem. what do I need to configure in the
> second filter (source and destination) because with the default
> configuration all the traffic to the server is blocked !
>
> I'll appricate any help.
>
> Assaf



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Ipsec tunnel mode vs ip in ip with ipsec transport Reji Linux Networking 1 09-20-2011 04:29 PM
IPv6 + IPsec + ipsec-tools 0.6.[4567] + scope:link = no SA established phil-news-nospam@ipal.net Linux Networking 0 07-25-2007 09:01 PM
IPsec configuring karthicks Linux Networking 0 05-05-2006 10:33 AM
IPSEC configuring error :cud anyone help out...? karthicks Linux Networking 1 04-24-2006 02:46 PM
IPSec transport mode or IPSec tunnel mode? Spin Windows Networking 1 07-01-2004 06:32 AM



1 2 3 4 5 6 7 8 9 10 11