Update SQL Bowser Service Article - by Mohit K. Gupta

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 774175 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 12/12/2012 4:20:58 PM
Access Restriction Public

Description

SQL Server Bowser service does not work against default instances.  I think the article should list that.  If you change the default port for a default instance, browser service does not reply back with correct port.  Because no attempt is made to get the port information, as listed in Connect article http://connect.microsoft.com/SQLServer/feedback/details/587855/sql-browser-service-needs-to-include-default-instance.

It can be tested to quickly with following steps...

- Start SQL Server Browser service from Command Prompt with -c option.  This will cause the Browser Service to report all incoming/outgoing requests.
- Change the default port on default instance from 1433 to different port, lets say 51000.
- Disable all protocols expect TCP/IP.
- Restart SQL Server Instance.
- Open up SQL Server management studio and try to connect to SQL Server now.

It will fail to connect.  With following error messages ..

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

or

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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061).

Verified with NetMon and ProcessMon.  It does scan the register for all the information, however never responds to UDP 1434 or because it never receives request.  As in the other connect article, it states the DbNetlib doesn't even try to make a call to SQL Browser service if it is default instance.
Sign in to post a comment.
Posted by Microsoft on 4/24/2013 at 10:07 AM
Sorry. But to the best of my knowledge this is not being enhanced at this time.
Posted by Mohit K. Gupta on 4/17/2013 at 9:57 AM
Thank-you :). Do you know if there are any plans to add that functionality in, as I am finding many customers are changing their default port information for default instances also.
Posted by Microsoft on 4/17/2013 at 9:26 AM
I have added the text "The SQL Server Browser does not return port information for the default instance." To the Books Online topic. This will appear as each version of Books Online is refreshed.
Thank you for reporting this.
Posted by Microsoft on 12/31/2012 at 12:58 PM
Thanks for your feedback. Our developer is taking a look.