Skip to content

network-protocols-and-network-libraries.md

Latest commit

 

History

History
89 lines (62 loc) · 6.35 KB

network-protocols-and-network-libraries.md

File metadata and controls

89 lines (62 loc) · 6.35 KB
title Network Protocols and Network Libraries | Microsoft Docs
description A server can be configured to monitor multiple network protocols. You can change the configuration using the SQL Server Configuration Manager.
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.reviewer
ms.technology install
ms.topic conceptual
helpviewer_keywords
protocols [SQL Server]
configuration options [SQL Server], protocols
network libraries [SQL Server]
protocols [SQL Server], about network protocols
pipes [SQL Server]
network protocols [SQL Server]
default SQL Server configurations
library [SQL Server]
network protocols [SQL Server], about network protocols
configuration options [SQL Server], libraries
ms.assetid 8cd437f6-9af1-44ce-9cb0-4d10c83da9ce
author rwestMSFT
ms.author randolphwest

Network Protocols and Network Libraries

[!INCLUDE SQL Server -Windows Only]

A server can listen on, or monitor, multiple network protocols at one time. However, each protocol must be configured. If a particular protocol is not configured, the server cannot listen on that protocol. After installation, you can change the protocol configurations using the [!INCLUDEssNoVersion] Configuration Manager.

Default SQL Server Network Configuration

A default instance of [!INCLUDEssNoVersion] is configured for TCP/IP port 1433, and named pipe \\.\pipe\sql\query. [!INCLUDEssNoVersion] named instances are configured for TCP dynamic ports, with a port number assigned by the operating system.

If you cannot use dynamic port addresses (for example, when [!INCLUDEssNoVersion] connections must pass through a firewall server configured to pass through specific port addresses). Select an unassigned port number. Port number assignments are managed by the Internet Assigned Numbers Authority and are listed at https://www.iana.org.

To enhance security, network connectivity is not fully enabled when [!INCLUDEssNoVersion] is installed. To enable, disable, and configure network protocols after Setup is complete, use the [!INCLUDEssNoVersion] Network Configuration area of the [!INCLUDEssNoVersion] Configuration Manager.

Server Message Block Protocol

Servers in the perimeter network should have all unnecessary protocols disabled, including server message block (SMB). Web servers and Domain Name System (DNS) servers do not require SMB. This protocol should be disabled to counter the threat of user enumeration.

Warning

Disabling Server Message Block will block the [!INCLUDEssNoVersion] or Windows Cluster service from accessing the remote file share. Do not disable SMB if you do or plan to do one of the following:

  • Use Windows Cluster Node and File Share Majority Quorum mode
  • Specify an SMB file share as the data directory during [!INCLUDEssNoVersion] installation
  • Create a database file on an SMB file share

To disable SMB

  1. On the Start menu, point to Settings, and then click Network and Dial-up Connections.

    Right-click the Internet-facing connection, and then click Properties.

  2. Select the Client for Microsoft Networks check box, and then click Uninstall.

  3. Follow the uninstall steps.

  4. Select File and Printer Sharing for Microsoft Networks, and then click Uninstall.

  5. Follow the uninstall steps.

To disable SMB on servers accessible from the Internet

  • In the Local Area Connection properties, use the Transmission Control Protocol/Internet Protocol (TCP/IP) properties dialog box to remove File and Printer Sharing for Microsoft Networks and Client for Microsoft Networks.

Endpoints

[!INCLUDEssNoVersion] introduces a new concept for [!INCLUDEssNoVersion] connections; the connection is represented on the server end by a [!INCLUDEtsql]endpoint. Permissions can be granted, revoked, and denied for [!INCLUDEtsql] endpoints. By default, all users have permissions to access an endpoint unless the permissions are denied or revoked by a member of the sysadmin group or by the endpoint owner. The GRANT, REVOKE, and DENY ENDPOINT syntax uses an endpoint ID that the administrator must get from the endpoint's catalog view.

[!INCLUDEssNoVersion] Setup creates [!INCLUDEtsql] endpoints for all supported network protocols, as well as for the dedicated administrator connection.

[!INCLUDEtsql] endpoints created by [!INCLUDEssNoVersion] Setup are as follows:

  • [!INCLUDEtsql] local machine

  • [!INCLUDEtsql] named pipes

  • [!INCLUDEtsql] default TCP

For more information about endpoints, see Configure the Database Engine to Listen on Multiple TCP Ports and Endpoints Catalog Views (Transact-SQL).

For more information about [!INCLUDEssNoVersion] network configurations, see the following articles in [!INCLUDEssNoVersion] Books Online:

See Also

Surface Area Configuration
Security Considerations for a SQL Server Installation
Planning a SQL Server Installation