Named Pipe and Clustering
From: Alex (alim_at_rogers.com)
Date: 12/11/03
- Previous message: Roland: "Secure Sockets Layer"
- Next in thread: Kevin McDonnell [MSFT]: "RE: Named Pipe and Clustering"
- Reply: Kevin McDonnell [MSFT]: "RE: Named Pipe and Clustering"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 11 Dec 2003 12:03:10 -0500
Hi,
I need to disable named pipes in a SQL Cluster environment (Windows 2000 and
SQL 2000 latest SP). Here is the scenario:
Our security policy requires me to secure my production SQL Server (Virtual
SQL Cluster name=SQL01) by disabling any access to SQL Server except access
from application server. I implemented this security in UAT (Non clustered )
by creating an IPSEC filter and disabling Named Pipes on SQL Server. In one
IPSEC filter, All IP Traffic to port 1433 is blocked. In another filter,
traffic from application server IP Address is permitted. This configuration
worked fine in UAT.
When I promoted the same IPSEC policy to production (both nodes
active-passive), I noticed that I can't disable Named Pipes in cluster
environment. Is there any work around this?
Can I change default pipe for Named Pipe in order to block SQL connections
coming from default pipe?
Do you have any better suggestion to secure SQL Server?
Thanks
- Previous message: Roland: "Secure Sockets Layer"
- Next in thread: Kevin McDonnell [MSFT]: "RE: Named Pipe and Clustering"
- Reply: Kevin McDonnell [MSFT]: "RE: Named Pipe and Clustering"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|