SQL Server Management Studio unable to connect to anything but standard port in TCP - by RedPhoenix HD

Status : 


Sign in
to vote
ID 133870 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 6/13/2006 7:27:44 PM
Access Restriction Public


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?
Sign in to post a comment.
Posted by Microsoft on 6/14/2006 at 6:50 AM
Hi Red,
    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.