configure-client-protocols.md

title	Configure Client Protocols | Microsoft Docs
ms.custom
ms.date	07/27/2016
ms.prod	sql-non-specified
ms.prod_service	database-engine
ms.service
ms.component	configure-windows
ms.reviewer
ms.suite	sql
ms.technology	database-engine
ms.tgt_pltfrm
ms.topic	article
helpviewer_keywords	default protocols network protocols [SQL Server], client configuration TCP/IP [SQL Server], client protocols disabling client protocols ordering protocols [SQL Server] protocols [SQL Server], order for client computers configure client protocols client protocols [SQL Server] protocols [SQL Server], client configuration default protocols, client
ms.assetid	3dfa2702-ba65-43b4-a777-6727846e133a
caps.latest.revision	35
author	MikeRayMSFT
ms.author	mikeray
manager	craigg
ms.workload	On Demand

Configure Client Protocols

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] This topic describes how to configure client protocols used by client applications in [!INCLUDEssCurrent] by using [!INCLUDEssNoVersion] Configuration Manager. Microsoft [!INCLUDEssNoVersion] supports client communication with the TCP/IP network protocol and the named pipes protocol. The shared memory protocol is also available if the client is connecting to an instance of the [!INCLUDEssDE] on the same computer. There are three common methods of selecting the protocol.

• Configure all client applications to use the same network protocol by setting the protocol order in [!INCLUDEssNoVersion] Configuration Manager.

• Configure a single client application to use a different network protocol by creating an alias. For more information, see Create or Delete a Server Alias for Use by a Client (SQL Server Configuration Manager).

• Some client applications, such as sqlcmd.exe, can specify the protocol as part of the connection string. For more information, see Connect to the Database Engine With sqlcmd.

Using SQL Server Configuration Manager

To enable or disable a client protocol

1. In [!INCLUDEssNoVersion] Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.

2. Click a protocol in the Disabled Protocols box, and then click Enable, to enable a protocol.

3. Click a protocol in the Enabled Protocols box, and then click Disable, to disable a protocol.

To change the default protocol or the protocol order for client computers

1. In [!INCLUDEssNoVersion] Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.

2. In the Enabled Protocols box, click Move Up or Move Down, to change the order in which protocols are tried, when attempting to connect to [!INCLUDEssNoVersion]. The top protocol in the Enabled Protocols box is the default protocol.

   [!IMPORTANT]
   [!INCLUDEssNoVersion] Configuration Manager creates registry entries for the server alias configurations and default client network library. However, the application does not install either the [!INCLUDEssNoVersion] client network libraries or the network protocols. The [!INCLUDEssNoVersion] client network libraries are installed during [!INCLUDEssNoVersion] Setup; the network protocols are installed as part of Microsoft Windows Setup (or through Networks in Control Panel). A particular network protocol may not be available as part of Windows Setup. For more information about installing these network protocols, see the vendor documentation.

To configure a client to use TCP/IP

1. In [!INCLUDEssNoVersion] Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.

2. In the Enabled Protocols box, click the up and down arrows to change the order in which protocols are tried, when attempting to connect to SQL Server. The top protocol in the Enabled Protocols box is the default protocol.

The shared memory protocol is enabled separately by checking the Enabled Shared Memory Protocol box.

See Also

Configure the remote login timeout Server Configuration Option