<div>
<div class="content wysiwyg-content">
We have a Windows 2003 server that runs a service listening on TCP port 3100. &nbsp;We want to lock this down so that only clients in a particular IP range can access them.<br />
<br />
Example:<br />
LAN is 172.16.0.0/16<br />
We want 172.16.7.x machines to be able to connect but not any others.<br />
<br />
Can we use IPSec policy under Windows 2003 to block all access to TCP port 3100 with the exception of 172.16.7.0/24?<br />
<br />
I don't want to VLAN the servers to achieve this or use firewall hardware.<br />
<br />
Can this be done under Windows 2003 at a software level?<br />
<br />
Thanks
</div>
</div>


We have a Windows 2003 server that runs a service listening on TCP port 3100.  We want to lock this down so that only clients in a particular IP range can access them.

Example:
LAN is 172.16.0.0/16
We want 172.16.7.x machines to be able to connect but not any others.

Can we use IPSec policy under Windows 2003 to block all access to TCP port 3100 with the exception of 172.16.7.0/24?

I don't want to VLAN the servers to achieve this or use firewall hardware.

Can this be done under Windows 2003 at a software level?

Thanks

Windows Server 2003 - Way To Packet Filter ?

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).