Missing Client Protocols in SQL Server Configuration Manager

Serrato, Mario 0 Reputation points

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.

👁 User's image

👁 User's image

  1. Viorel 127K Reputation points

    Why is it necessary?

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

    Hi @Serrato, Mario ,

    This behavior is expected in SQL Server 2025.

    The Client Protocols node in SQL Server Configuration Manager is a legacy feature and is no longer used by modern SQL client drivers (ODBC 18+, Microsoft.Data.SqlClient, newer OLE DB). That’s why it appears empty nothing is missing or broken.

    Only server-side protocols (TCP/IP under SQL Server Network Configuration), firewall rules, and proper connection strings matter now.

    The PowerShell/registry workaround only applies to very old SQL Native Client–based applications and is not required for normal SQL Server 2025 usage.
    No further action is needed unless you’re supporting legacy clients.

    Thanks,
    Akhil.

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

    Hi @Serrato, Mario ,

    Just checking back to see if the explanation above helped clarify why Client Protocols appear empty in SQL Server 2025.

    Could you please confirm whether this resolved your concern, or let us know if you’re still facing any issues? We’ll be happy to help further.

    Thanks,
    Akhil.

Sign in to comment

2 additional answers

  1. Erland Sommarskog 134.7K Reputation points • MVP • Volunteer Moderator

    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.

    0 comments No comments
    Sign in to comment
  2. Marcin Policht 92,630 Reputation points • MVP • Volunteer Moderator

    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

    0 comments No comments
    Sign in to comment
Sign in to answer

Your answer