FIX: SQL Server Browser doesn't respond through clustered IP address from a SQL Server 2019 Failover Clustered Instance (FCI)

Applies to: SQL Server 2019 on Windows


Assume that you run a named instance SQL Server 2019Failover Clustered Instance (FCI). You notice that the SQL Server Browserservice doesn't respond through the clustered IP address to client requests. However, SQL Server Browser service will respond through the local IP address. Additionally, the clientsmay be unable to fix TCP-IP port or named pipe specifics for the requestedinstance name. In this situation, the client connection may fail.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 


The fix for this issue is included in the following update for SQL Server:


To work around this issue, use one of the following methods:
  • Clients can specify TCP-IP port or named pipes address information to bypass SQL Server Browser service.
  • Use SQL alias entries on all client machines tospecify TCP-IP port or named pipes address information.


Learn about the terminology that Microsoft uses to describe software updates.