1. If you have multiple subnets then you can use ACLs on the LAN router
between them and the SQL's subnet.
2. If on the same subnet, and any thirdparty stuff aside, you be able to use
Packet Filters on the NIC in the Advanced Network Settings of the NCI,...but
I suspect it could become cumbersome because those arent' very flexable.
3. The another option might be if SQL Server itself has the ability to do
this within itself,...I don't know, SQL Server is not my "area".
4. IPSec could be another option.
My choice would be none of them, and I would control access by user account
and not worry about what IP# they are using. SQL Server can use either
Windows Accounts, Domain Accounts, or its own native user accounts that you
create within SQL Server,...or even a combination of all three.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Simo Sentissi" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello there
>
> I am running win2000 advanced server for my sql databases
> and I need to control the access to the server by IP adresses (something
> like only people to initiate traffic with the server are 10.200.52.X....)
> anybody know of anyway to do that ?
> it will be great to know if there is a native solution or some cheap 3rd
> party ?
Linear Mode
