nejla
 |
| 07/17/2002 1:16 AM |
 Quote
 Reply
 Alert
|
| I want to restrict some machines to connect to the SQL Server except for
the machines that absolutely require connectivity.How can I do it
|
|
|
|
|
Chip Andrews
|
| 07/17/2002 12:23 PM |
Quote
Reply
Alert
|
| Here's a few places to start:
1. Place a firewall between the SQL Server and the rest of the network and only allow specific IP addresses. A device that allows specific rules or a personal firewall that does the same should do the trick (although I don't like software firewalls on critical servers.)
2. Use IPSec to restrict connectivity to other hosts. There are numerus tunnelling options you could try here as well.
3. Force protocol encryption on the server using a certificate only trusted by certain clients.
By far I like the firewall option best. Its simplist and doesn't require any specific Windows OS tinkering (like enabling IPSec or installing certificates). Your typical firewall appliance for $50 should do the job nicely - especially since many of them come with a built-in switch as well.
|
|
|
|
|
nejla
|
| 07/20/2002 2:22 AM |
Quote
Reply
Alert
|
| thanks chip for your advice.
I want something instead of firewall.
I tried working with sysproceses table in Master database.
I wrote a trigger for controlling then connections and their acts and kill processed which I don't want them with their spid.
but it's not working
thanks for your help
nejla |
|
|
|
|
Paresh
|
| 08/26/2002 2:47 PM |
Quote
Reply
Alert
|
| The trigger on sysprocesses does not work because system tables cannot have triggers on them...the servers/users in our domain are on DHCP, hence it is not possible to restrict them through IP address restrictions....
any help here might be great... |
|
|
|
|