This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 10%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
I installed SQL Server 2025, but when I try to enable TCP/IP from SQL Server Configuration Manager, the Client Protocols field is empty. I've tried everything: uninstalling, reinstalling, checking ports, using snap-ins—I'm at a loss. I have the correct version, permissions, etc., but nothing appears.
Why is it necessary?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Give the following a try
https://stackoverflow.com/questions/76096932/client-protocols-and-alias-missing-on-sql-native
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
This is expected. The Client Protocols node in SSCM is a holdover from older versions of SQL Server, and particularly older versions of the ODBC and OLE DB drivers that shipped with these versions of SQL Server.
Recent versions do not support being controlled through SSCM.
Is there any particular reasons you want to fiddle the the client-side protocol settings? Normally, you only modify the protocols for the server itself.