Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol
Today I am going to discuss about Microsoft SQL Server Error 28 that most of the SQL Server users might have faced at least once in their career. It belongs to SQL Server connectivity issue SQL Network Interfaces Error 28.
Microsoft SQL Server Error 28
This is very common error that most of the people have gone through. Microsoft SQL Server Error 28 details are given below:
Sometime you might get same error as below description.
Generally, we get SQL Network Interfaces Error 28 while connecting to SQL Server instance either using SQL Server Management studio or using any other way. There might be several reasons behind generating Microsoft SQL Server Error 28. I have tried to capture all such reasons in below points..
- A specified SQL Server instance name is not valid. Wrong SQL Server Instance Name can lead to generate Microsoft SQL Server Error 28.
- Remote access is not enabled for your SQL Server instance.
- The firewall on the server has refused the connection because ports used by SQLBROWSER.EXE and SQLSERVR.EXE is still blocked.
- The SQL Server Browser service (sqlbrowser) is not started.
We need to check and validate multiple factors to fix Microsoft SQL Server error 28. Check all factors given in below step by step points to fix all possibilities for this SQL error 28.
- Validate whether server on which SQL Server is hosted is reachable from your client machine or not. Run ping and telnet to make sure server connectivity.
- Make sure SQL Server is running fine on your server. Check SQL Server services.
- Firewall ports 1433 for SQL Server and 1434 for SQL Server Browser services should be opened.
- Verify correct SQL Server Instance name. Check the spelling of the SQL Server instance name that is specified in the connection string.
- Make sure to enter full SQL Server Instance name in case you have named instance like SERVERNAME\SQL2017.
- Make sure that the SQL Server Browser service is started on the server.
- Enable Remote connection for your SQL Server Instance. Most of the people face Microsoft SQL Server error 28 because remote connection was disabled on the SQL Server Instance. Use the SQL Server Configuration Manager tool to enable SQL Server to accept remote connections over the TCP or named pipes protocols. Below steps you can follow to enable remote connections.
- Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and then click Protocols for InstanceName. If your server has default instance then it will look like “Protocols for MSSQLSERVER”
- You can see all three protocols in right side pane. Shared Memory, Named Pipes and TCP/IP.
- Make sure to enable Named Pipes and TCP/IP. Right-click at the protocol name and then click Enable. The icon for the protocol will change to show that the protocol is enabled.
- You need to restart the SQL Server services to bring the changes into effect so restart your SQL Server services.
- Fix SQL Server Error 40: A Network related or Instance specific Error Occurred while establishing a connection to SQL Server
- How to Fix SQL Server Error 53: Could Not Open a Connection on SQL Server?
- Fix Error 4064: Cannot open user default database
- SAP Connectivity Issue After AlwaysON Automatic failover
- Fix Error 976: Cannot connect to Secondary Replica of AOAG
Latest posts by Manvendra Deo Singh (see all)
- Understanding Hybrid Buffer Pool in SQL Server - December 30, 2018
- Fix:VIEW SERVER STATE permission was denied on object ‘server’, database ‘master’ - August 30, 2018
- SQL Server Error 5184: Cannot use file ‘I:\Path\Techyaz.mdf’ for clustered server - August 29, 2018