SQL Server Home
SQL Server Management Studio unable to connect to anything but standard port in TCP
6/13/2006 7:27:44 PM
User(s) can reproduce this bug
While I understand many people use the standard 1433 port for SQL, we sometimes have the need to setup TCP listening on a different port.
There does not seem to be any way to have Management Studio connect to a TCP instance of SQL 2005 on anything but port 1433. No number of address combinations would work (i.e. SQL.SERVER.COM:1499).
Should there not be a field (at least under "options") where we can change the connection port so Management Studio usage is not restricted?
SQL Server 2005 Express Edition with Advanced Services - March 2006 CTP
Windows Server 2003
Operating System Language
Steps to Reproduce
Install SQL 2005 Exp Adv as per normal. In the configuration, turn on TCP (usually off by default) and set the listening port to 1499.
Try to connect using the Management GUI. Make sure TCP is set under "options". It will not connect to the SQL instance even if you specify "SQLSERVER.com:1499". If you switch the port back to 1433 it connects just fine.
There appears to be no way to tell Management Studio to use a different port other than the default.
Results in no connection.
w/o a field for port specifications, I kind of expected it to fail, but you should be able to specify any TCP port.
to post a comment.
Please enter a comment.
on 6/14/2006 at 6:50 AM
Thank you for you bug report. It turns out that you can use the SQL Server Configuration Manager to change the TCP/IP settings on the server and client.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft