Access SQL Server Using Named Pipes

I. Significance

After SQL Server is installed, the default configuration is to allow access by the client using the TCP/IP protocol. You only need to know the password of the SQL Server account, which is not safe, because many WEB programs directly write the connection information (database server, connection account, and connection password) in the program, attackers or hackers can directly view the source code to obtain the SQL Server account and password, and they can directly connect to the database Server using the TCP/IP protocol, modifies or even destroys data or configurations. When using a named pipeline, you must have the resources on the machine where SQL Server is located before you can access SQL Server. If you do not have the permission to access the resources, even if he knows the SQL Server account password, it cannot be connected.

II. Implementation

1. Server Configuration

Open the Server Network Utility of SQL Server: "START-> Program-> Microsoft SQL Server 7.0-> Server Network Utility". In the "General" column, delete unnecessary connection configurations, then press "Add... add a Named Pipes connection: Network librarys selects Named Pipes, and the Server name is the Server's machine name.

2. Client Configuration

Open the Client Network Utility of SQL Server: "START-> Program-> Microsoft SQL Server 7.0-> Client Network Utility". In the "General" column, delete unnecessary connection configurations, then press "Add... "Add a Named Pipes connection: Network librarys selects Named Pipes. The Server alias is the machine name (LAN) or IP address (WAN) of the Server where the SQL Server to be connected is located)

3. Connection Method

There are two scenarios:
A. The client has logged on to the domain where the Server is located. The client has the permission to access Server resources and can directly connect to the SQL Server.
B. The client does not log on to the server's domain. The client does not have the permission to access server resources. You can enter \ <server machine name or IP address> in "start-> Run, then, enter the NT account and password. After the verification is passed, the client has the permission to access Server resources. Then, the client can connect to SQL Server.

(