Accessing SQL Server using Named pipes

When you use a named pipe, you must have access to the resources of the machine where SQL Server resides before you can access SQL Server, and if the user does not have permission to access the resource, even if he knows that the SQL Server account is not connected.

One, meaning

After SQL Server installation, the default configuration is to allow clients to access the TCP/IP protocol, and users need only know the password of the SQL Server account to access, which is not safe, because many web programs are direct connection information (database server, Connection account, connection password) Written in the program, the attacker or hacker can in some ways to view the source code to obtain the SQL Server account and password, they can directly with the TCP/IP protocol to connect to the database server, the data or configuration to modify or even damage. When you use a named pipe, you must have access to the resources of the machine where SQL Server resides before you can access SQL Server, and if the user does not have permission to access the resource, even if he knows that the SQL Server account is not connected.

Second, realize

1, server Configuration

Open SQL Server's server network Utility: "Start-> program->microsoft SQL Server 7.0->server network Utility", in the General column, Remove the unnecessary connection configuration and press "Add ..." to add a Named Pipes connection: Network Librarys Select named Pipes,server name is the server's machine name.

2. Client Configuration

Open SQL Server's Client network Utility: Start-> program->microsoft SQL Server 7.0->client network Utility, in the General column, Remove the unnecessary connection configuration and press "Add ..." to add a Named Pipes connection: Network Librarys Select named Pipes,server alias is the machine name (local area network) or IP address of the server on which SQL Server is to be connected Wan

3. Connection method

Can be divided into two categories:
A, the client has logged on to the domain where the server resides, the client already has access to the server resources, and can directly connect to SQL Server
B, the client does not log on to the server's domain, the client does not have access to the server resources, you can enter the "Start-> run" in the \< server machine name or IP address, and then enter the NT account and password, verify that the client has access to the server resources after the permissions, The client can now connect to SQL Server.