Microsoft SQL Server 2022 - no TCP/IP connection in client protocols in SQLServer Configuration Manager

Question

Microsoft SQL Server 2022 - no TCP/IP connection in client protocols in SQLServer Configuration Manager

Lackner, Mario 0

Hello,

since SQL Server 2022 Standard edition I miss in "SQL Server Configuration Manager" under "client protocols" all protocols e.g. "TCP/IP", to enable client connection to the Database.

Also I can not create manually a protocol in "client protocols".

No listening on port 1433.

thanks in advance for your help!

BR Mario

User's image

0 comments

3 answers

Your answer

Answer 1

Senthil kumar 685

Hi @Lackner, Mario

as per the error message you have to add your link your client ip to server by command attached the page link for your reference.
https://www.sqlshack.com/how-to-create-and-configure-a-linked-server-in-sql-server-management-studio/
please follow the procedures.

Thanks.

Lackner, Mario 0 Reputation points

2026-05-27T11:10:13.5066667+00:00

Hello,

the Server was already linked but the connection bring similar failure. connection from MSSQL 2019 - MSSQL 2022.

I think the destination SQL Server is not listening for connections?

BR Mario

===================================

The test connection to the linked server failed.

===================================

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Program Location:

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry)

at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(String cmd, Boolean retry)

at Microsoft.SqlServer.Management.Smo.LinkedServer.TestConnection()

at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LinkedServerConnectionTest.Invoke()

===================================

Named Pipes Provider: Could not open a connection to SQL Server [2].

OLE DB provider "MSOLEDBSQL" for linked server "SW01PAC702" returned message "Login timeout expired".

OLE DB provider "MSOLEDBSQL" for linked server "SW01PAC702" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". (.Net SqlClient Data Provider)

------------------------------

For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-2-database-engine-error

------------------------------

Server Name: SW01PAC01

Error Number: 2

Severity: 16

State: 1

------------------------------

Program Location:

at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry)
Senthil kumar 685 Reputation points

2026-05-27T12:40:35.8033333+00:00
Ok,

So, first install. "Microsoft OLE DB Driver for SQL Server” (MSOLEDBSQL 19.x or later)"

After installation Open SQL Server Configuration Manager

Go to SQL Server Network Configuration → Client Protocols

You should now see TCP/IP, Named Pipes, and Shared Memory

Right‑click each → Enable

Then restart SQL Server (MSSQLSERVER) & SQL Server Agent.

then execute server linked command again
EXEC master.dbo.sp_addlinkedserver @server = N'MyLink2022_TCP', @srvproduct = N'', @provider = N'MSOLEDBSQL', @datasrc =N'tcp:servername,1433';
Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator

2026-05-27T20:47:39.1733333+00:00

Senthil, Mario obviously already have MSSQLOLEDB installed, since the provider name appears in the error message. But there will not be anything in Client protocols with less than he installs the old SQL Server Native Client. (Which he should not do, and it would not change things.)
Senthil kumar 685 Reputation points

2026-05-27T22:11:40.14+00:00

Ok, understand @Erland Sommarskog .
In this case please try to change the application connection string provider based on your method odbc or oledb. may be helpful to fix this issue.

Thanks.

Answer 2

Erland Sommarskog 134.7K MVP Volunteer Moderator

As the AI says, this node relates to the old SQL Native Client drivers which are not shipped with SQL Server. Instead you use the ODBC and OLE DB drivers which you install separately.

It was long ago I had any reason to work with this node in SSCM anyway. What exactly do you expect to use this node for?

Lackner, Mario 0

Hello, 
I need to grant a client read access to a dedicated table. `@sqlCmd='update #pslTempStudiesProd set IsInUID=1 where ser_ins_uid in (select SERINSTANCEUID from '+@server0x+'.Patient.dbo.SERIES)'` where `server0x` is the remote server with MS SQL 2022.

When I try to apply the AI solution, port 1433 doesn't open. What steps are needed for this in cliconfg.exe?
Thx in Advance, Mario Lackner

Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator

2026-05-26T20:30:43.4733333+00:00

What error message do you get?
Lackner, Mario 0 Reputation points

2026-05-27T07:49:16.4133333+00:00

if I try to connect by using following command I get this error message:

select SERINSTANCEUID from sw01pac0x1.Patient.dbo.SERIES

OLE DB provider "MSOLEDBSQL" for linked server "sw01pac0x1" returned message "Login timeout expired".

OLE DB provider "MSOLEDBSQL" for linked server "sw01pac0x1" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".

Msg 2, Level 16, State 1, Line 0

Named Pipes Provider: Could not open a connection to SQL Server [2].

btw. if SQLServer2016 is installed on the querydestination this query works.
Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator

2026-05-27T20:45:05.5033333+00:00
So that is a plain standard connection error, meaning that the SQL Server instance you are trying to connect to was not found. This has nothing to do with the missing node Client protocols. This is the same error message you get from SSMS if you mis-type a server name. The only difference is that instead of connecting from SSMS, you are connecting from an SQL Server instance. But the means of troubleshooting is the same.

Is the server name correctly spelled? Note that the name used for the connection is not necessarily SW01PAC0x1, because that is just the name of the linked-server object itself. Check the data_source column in sys.servers.

Is the remote instance a default instance, or are you missing the instance name? Again, check sys.servers.

Is the remote instance, configured to accept remote connections. This you check in SQL Server Configuration Manager on the remote machine, under SQL Server Network Configuration.

Are there any firewall rules in the way? This could potentially be an outgoing firewall on the local SQL Server machine.
Lackner, Mario 0 Reputation points

2026-06-01T13:48:59.35+00:00

hello,

point 1 and 2 are ok. servername ist resolveable and it doesn't matter if i use the hostname or the default instance.point 3: where can i check if the remote instance is configured to accept remote connections ind SQL Server Configuraiton Manager?

point 4: windows firewall is for testing complete switched off

any other ideas?

attached the output from "SELECT * FROM [master].[sys].[servers]"

maybe this helps?

BR Mario
Senthil kumar 685 Reputation points

2026-06-01T17:25:59.79+00:00
Below query to get all linked servers list.

SELECT * FROM sys.servers WHERE is_linked = 1;
Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator

2026-06-01T21:06:52.3233333+00:00

The output from sys.servers is not congruent with your error messages. The error message talks about a linked server by the name of sw01pac0x1, but you only have one linked server in that output, and that is the Windows AD, not an SQL Server instance.

The output includes sw01pac0x1\MSSQLSERVER_SYDS, but that's server_id 0, which is the local instance.

So either you did not share the full output from sys.servers, or this is the output from a different SQL Server instance than the one you got the error message on.

Please be mindful that I only the details about your environment that you share with me. So it is important that the information I get is exact and accurate.
Lackner, Mario 0 Reputation points

2026-06-02T07:13:34.9966667+00:00
The output was from the SQL Instance I'm try to connect . I thought this will be interesting because there should be a difference between SQL 2016 and SQL 2022. Sorry for that!

Now attached the output from the SQL I'm trying to connect from (SQL2019):

in green, the connection to sw01pac711,712,713, are working fine to sql 2016 instances.

the red ones are not working to SQL2022.

Is there anything that should be additional configured on the not connectable Servers?
Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator

2026-06-02T19:28:01.98+00:00
Yet different server names from the name in the original post.

Can you run this query:

SELECT * FROM SW01PAC701.master.sys.databases

and share the output in a single screenshot? Please add line breaks in the error message so that all text is visible.

Can you connect to SW01PAC701 from SSMS on a different machine than SW01PAC701 itself without errors?

When connecting to an SQL Server instance, the version of the instance has very little importance. Rather difference in behaviour are due to differences in configuration.
Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-06-08T06:21:06.8433333+00:00

Hi @Lackner, Mario ,

Just following up to see whether you were able to run the requested checks and gather the additional information.

If the issue is still occurring, an update on the database query results, the full error message, and the outcome of testing the connection from another machine would be very helpful. Those details may help determine whether the problem is related to connectivity, instance configuration, or something specific to the server environment.

When you have a chance, please let us know how things are progressing.

Thanks,
Akhil.
Lackner, Mario 0 Reputation points

2026-06-08T12:02:43.4133333+00:00

Hello,

following the screenshot of the query

And no, there are also no other connection possible to the sw01pac701 server from SSMS.

Thanks and BR Mario
Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator

2026-06-08T20:54:51.9266667+00:00
So this suggests one of:

There is no SQL Server instance on SW01PAC701.

Or there is one, but it is a named instance, and not a default instance.

Or there is a default instance, but it is not running.

Or it is running, but it is not configured to accept remote connections.

There are firewalls or network configuration preventing traffic to get through.

For the first four points, you should check SQL Server Configuration Manager on SW01PAC701.

For the last point, you need to talk to your networking people.
Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-06-10T06:39:34.5433333+00:00

Hi @Lackner, Mario ,

Thank you for the update and for sharing the screenshot.

Based on the results provided, the guidance from Erland is consistent with the symptoms observed. The inability to connect from other machines as well as the linked server timeout indicates that the issue is likely outside the query itself and related to the SQL Server instance availability, configuration, or network connectivity.

Please review the suggested checks on SW01PAC701 and let us know what you find. If you discover any additional errors in SQL Server Configuration Manager, the SQL Server error log, or during connectivity testing, feel free to share them and we'll be happy to continue investigating.

Thanks for the update.

Thanks,
Akhil.
Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator

2026-06-18T05:58:52.0933333+00:00

Hi @Lackner, Mario ,

Just checking in to see whether you had an opportunity to investigate the connectivity issue further.

Were you able to review the SQL Server error logs, SQL Server Configuration Manager settings, or perform any additional network connectivity tests on SW01PAC701?

If you found any new error messages or observations during your investigation, please share them here and we'll be glad to continue assisting.

Thanks,
Akhil.

Answer 3

In SQL Server 2022 and later, the traditional “SQL Server Native Client” (sqlncli) is deprecated and no longer installed as part of SQL Server. Because of this, the Client Protocols node for “SQL Native Client 11.0” in SQL Server Configuration Manager can appear empty and cannot be populated from there.

Client connectivity now relies on newer client providers (for example, the Microsoft ODBC Driver for SQL Server or the Microsoft JDBC Driver), and the server‑side network stack is configured only under SQL Server Network Configuration → Protocols for <instance>. That is where TCP/IP, Named Pipes, and their ports (such as 1433) are enabled and configured.

To ensure TCP/IP connectivity for clients in this setup:

Open SQL Server Configuration Manager.
Go to SQL Server Network Configuration → Protocols for <your SQL 2022 instance>.
Enable TCP/IP and, if needed, Named Pipes.
In TCP/IP → Properties → IPAll, set a static TCP Port (for example, 1433) if a fixed port is required.
Restart the SQL Server service so the instance starts listening on the configured port.

If a legacy client or tool still depends on the old Native Client “Client Protocols” view, use the SQL Server Client Network Utility (cliconfg.exe) to enable TCP/IP and Named Pipes for those clients, as described in the referenced Q&A. This utility replaces the missing client‑protocol entries for older Native Client–based applications.

References:

Share via

Microsoft SQL Server 2022 - no TCP/IP connection in client protocols in SQLServer Configuration Manager

3 answers

Your answer