February 1, 2013 at 10:39 am
We were having an issue where SSMS was unable to connect to a named instance of SQL Server 2008 R2. We had TCP 1433 and UDP 1434 open.
We allowed all traffic to see what else it was trying to use and found port TCP 56731. When we opened that port it worked... I have never seen this port related to SQL before.
Any clues?
February 1, 2013 at 11:29 am
Named instances use dynamically assigned ports. The browser service normally handles this behind the scenes but the port(s) used still need to be open.
February 1, 2013 at 11:48 am
Thanks for the info!
Is there a range that I can open or do I always need to check what is assigned?
*Note to other readers you can see the port used here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<InstanceName>\MSSQLServerSuperSocketNetLib\TCP\IPAll\
February 3, 2013 at 8:28 pm
By default, SQL Server uses dynamically assigned port numbers. You have the option to assign a specific port number to an instance of SQL Server.
You can do this using the "SQL Server Configuration Manager". Have a look in Books Online for the topic "How to: Configure a Server to Listen on a Specific TCP Port" - it gives you all the details you will need to do this
February 3, 2013 at 10:36 pm
The port number is also available in the SQL Server log - it is one of the messages logged when SQL Server starts.
February 4, 2013 at 10:30 am
Excellent. Thank you all for the information.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply