Usually, the error ‘SQL Network Interfaces error 28’ occurs while trying to connect to SQL Server instance either using SQL Server Management Studio or using any other way.

Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and see how to fix it.

What causes ‘SQL Network Interfaces error 28’ error to occur

Before we get into the solution part, let’s first discuss the causes for this error to occur. Here are the different reasons for this error to occur.

• Invalid SQL Server instance name.
• Disabling of Remote access for your SQL Server instance name
• The ports used by SQLBROWSER.EXE and SQLSERVR.EXE is blocked. As a result, the firewall on the server refuses to connect.
• The SQL Server Browser service (sqlbrowser) is not started.

For instance, the error appears as below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol)

How we fix the error ‘SQL Network Interfaces error 28’

Here are the suggestions our Support Engineers provide to our customers to resolve this error.

Validate that the Server on which the SQL server is hosted is reachable by the client machine. For that, you can run ping and telnet to check the connectivity.

Ensure that the SQL server is running well on your server. For that, make sure to check SQL Server services.

The firewall ports like 1433 for SQL Server and 1434 for SQL Server Browser must be open.

Verify that the SQL Server Instance name is correct. Also, check the spelling of the SQL Server Instance name that is mentioned in the connection string.

In case you have named instance like SERVERNAME\SQL2017, then make sure to enter the full SQL Server Instance name.

Make sure to start the SQL Server Browser service on the server.

Enable Remote connection for your SQL Server Instance. You can enable SQL Server to accept remote connections over the TCP or named pipes protocols by using the SQL Server Configuration Manager tool. Here are the steps to enable remote connections.

• First, launch SQL Server Configuration Manager. Then from the left side pane expand SQL Server Network Configuration and then click Protocols for InstanceName. If your server has a default instance then it will look like “Protocols for MSSQLSERVER”
• Now, you must be able to see all three protocols in the right-side panel. They are Shared Memory, Named Pipes, and TCP/IP.
• Enable Named Pipes and TCP/IP. For that, right-click at the protocol name and then click Enable. Now, the icon for the protocol will change to show that the protocol is enabled.
• Finally, restart the SQL Server services to bring the changes into effect.

[Need any further assistance in fixing SQL errors? – We’re available 24*7]

Conclusion

In short, this error occurs while trying to connect to SQL Server instance either using SQL Server Management Studio or using any other way. Today, we saw how to fix this SQL error.