Connecting SQL Server Management Studio to a non-standard TCP/IP Port

Avian Waves : Blog

Topic: All

Filter by topic: All, Tech, Music, Website, Birds, Politics, Misc, TV, Environment, Smart Car, Science, Sports, Anime

RSS 2.0 Feed

Search Blog

All Any Exact

Archives

• July, 2010 (1)
• June, 2010 (1)
• April, 2010 (2)
• March, 2010 (3)
• January, 2010 (3)
• December, 2009 (1)
• November, 2009 (6)
• October, 2009 (8)
• September, 2009 (2)
• August, 2009 (1)
• July, 2009 (6)
• June, 2009 (14)

[ Show Full Archive ]

Connecting SQL Server Management Studio to a non-standard TCP/IP Port

Posted By Timothy • Topic: Tech

Feb 12, 2007 4:23 PM EDT

I searched for an hour on live.com and google.com to try to figure out how on EARTH you specify a non-1433 port number when you want to establish a remote connection to MS SQL Server using Management Studio. It seemed like such a simple thing. So simple, I guess, that I'm the only person that doesn't know how to do it!

Well I finally found a page that has the answer. It's easy. You add a comma and the port number to the end of the server name.

So if you want to connect to MySqlServer.MyDomain.com on port 3821, you type...

MySqlServer.MyDomain.com,3821

That's it!

Hopefully this will help some other poor sap who didn't realize (like me) that you use the same nomenclature as any normal connection string to specify a port number. So simple. Sheesh.

Ah well. Such is life!

Digg! / del.icio.us / Furl

[ Comments (39) • Trackbacks (0) ] PermaLink

Trackbacks :

Send trackbacks to this URL:

http://www.avianwaves.com/Blog/track.aspx?id=25

In your blog post, you must link back to my post using this URL:

http://www.avianwaves.com/Blog/default.aspx?id=25

Comments :

This was very helpful to me. Thank you very much for the post.

Comment By Sam Lalani At 3/8/2007 7:15 PM EDT

PermaLink

THANKS!!!

Comment By Hank At 4/2/2007 4:17 PM EDT

PermaLink

Thanks! This was great info. I couldnt find it in the help anywhere, and I still can't believe that it doesn't use a colon to separate the server name and the TCP/IP port.

Comment By Adam At 4/4/2007 10:28 AM EDT

PermaLink

Thanx buddy !

Comment By moszi At 4/27/2007 6:01 PM EDT

PermaLink

I'm glad someone else faced the same problem!! granted this was a simple connection string, but really shouldnt it be documented somewhere!!
now i could connect this way to a certain port only when the default tsql tcp endpoint has permissions to public - was it the same in your case?

Comment By adita At 5/3/2007 9:44 AM EDT

PermaLink

Yes it did -- thanks very much!

Comment By Jan At 5/14/2007 4:25 AM EDT

PermaLink

Thanks, this helped me too. I kept using servername:port with no luck, looked for a port setting everywhere I could with no luck, looked through the help files with no info available that I could find, edited the hosts config to specify a port number there with no luck, then googled the problem, found this article, and I'm connected.
You saved my day.

Comment By Me At 6/7/2007 4:37 PM EDT

PermaLink

I second the above. What a life-saver, and I agree with Adam: why on Earth doesn't it use a colon?

Comment By Henri Hein At 10/7/2007 10:41 PM EDT

PermaLink

Thanks a lot, so helpful and I think if cant find this page, more that one hour may be wasted.

Comment By AFShin At 11/14/2007 7:23 AM EDT

PermaLink

Thanks to you and Google, i just had to waste 30 secs to get this answer. Thanks a lot!

Comment By Kristian At 12/7/2007 2:59 AM EDT

PermaLink

Thanks, short answer, great results.

Comment By Enrique Sansores At 2/26/2008 3:01 PM EDT

PermaLink

Thank you very much! It was exactly what I've searched! Thank you and thank Google! :)

Comment By dj shaman At 4/2/2008 4:14 AM EDT

PermaLink

One of those simple-hard-to-find things that no one at microsoft gave its importance. Thanks a lot buddy !!!!

Comment By George Waters At 8/29/2008 4:30 AM EDT

PermaLink

How gay, you have to put a comma, how hard is it to put the port in the connection options dialog?! Thanks mate now I can actually connect to the server, onto the actual work.

Comment By bollo At 10/5/2008 7:27 PM EDT

PermaLink

GREAT, Thanks!!

There have been many many people sweating blood due to this idiotic defect - you can define protocol, but not the port, in connection options.

Comment By Finn, just not Hucleberry At 10/8/2008 5:50 AM EDT

PermaLink

Thank you very very much, you just saved my day.

Comment By Antti Kukkonen At 10/24/2008 4:54 AM EDT

PermaLink

Thanks a lot. Ben looking for this for a long time.

Comment By Jonas At 11/13/2008 4:32 AM EDT

PermaLink

THANKS ALOTTTTTTTTTT.

Comment By sara At 12/1/2008 8:18 AM EDT

PermaLink

It seems as though you should be able to create an alias and connect to SSMS using the alias name only instead of alias ame, port.

Comment By Renee' At 1/12/2009 2:26 PM EDT

PermaLink

Thank you so much! Now if someone can just explain why MS coders didn't write it to accept the typical colon (and if they needed it as a comma in the underlying connection string, just swap it out after the user hits Connect on that Connect to SErver dialog).

:-)

Comment By Deron Dilger At 4/8/2009 7:14 PM EDT

PermaLink

Thanks, this was frustrating me for a while.

Comment By JC At 4/16/2009 12:28 PM EDT

PermaLink

OH MY GOD!! THANK YOU SO MUCH!!!!

Comment By jk At 5/4/2009 11:03 PM EDT

PermaLink

Just wanted to thank!!

Comment By Jimsy At 5/11/2009 12:31 PM EDT

PermaLink

Thanks for saving a lot of time.

Comment By Benny At 9/21/2009 8:15 AM EDT

PermaLink

Well I didn't find the answer here.

For some odd reason though on my computer when specifying a different port number a space is required.
for instance

192.168.0.100,1232/SQLEXPRESS

did not work. but

192.168.0.100,1232 /SQLEXPRESS

does.. it doesn't make sense cause from a connection string either method works.. I really dislike this tool, but there is no replacement for it out there.

Comment By earlz At 10/14/2009 7:51 PM EDT

PermaLink

Another Server:Port person. Thanks fo rtaking the time to post this.

Another poor sap!

Comment By Ken At 11/8/2009 8:09 AM EDT

PermaLink

Thanks for the post, more helpful than the Help file!

Comment By Jay At 12/9/2009 5:26 PM EDT

PermaLink

bo selecta

Comment By Pete At 12/18/2009 11:40 AM EDT

PermaLink

Thanks, worked! No one specified this small thing.

Comment By Ram Kumaran At 12/23/2009 8:22 AM EDT

PermaLink

I guess Bill Gates had other uses for his colon... :-P

Thanks for this post. You really helped me out! :-)

Comment By Evert Meulie At 1/8/2010 6:17 AM EDT

PermaLink

Thanx man. Help me a lot

Comment By NKappa At 1/11/2010 2:42 PM EDT

PermaLink

Thanks A Lot. Initially tried with colon and Gawked when it didn't work.

Thanks for you posting buddy. It Worked.

Comment By Sarav At 1/20/2010 11:07 AM EDT

PermaLink

Thank you very much

Comment By Parker At 2/3/2010 10:13 AM EDT

PermaLink

A BIG thanks for that. I would have incorrectly guessed colon.

Comment By George At 3/1/2010 1:37 PM EDT

PermaLink

I was one of those poor saps you helped...thanks!

Comment By Homer Lim At 3/11/2010 9:17 PM EDT

PermaLink

thanks a lot

Comment By vinsen At 4/23/2010 11:39 AM EDT

PermaLink

Wonderful. Thanks. Sometimes it is just the little things that count (and save us a lot of time!)

Comment By Eric At 5/4/2010 9:22 PM EDT

PermaLink

thanx it saved alot of time! 30 seconds.

Comment By wous At 6/21/2010 8:31 AM EDT

PermaLink

Thanks man! Saved me some time. I can also add that localhost isn't recognized but using 127.0.0.1 works fine, though. Why follow standards...? :)

Comment By colon blow At 7/15/2010 4:26 AM EDT

PermaLink

Add Comment :

Name :

Email :

URL (Optional) :
Remember Info?

Comments :

Allowed BBCode Tags : LINK (URL), BOLD, ITALIC, UNDERLINE, QUOTE

By posting a comment to this blog, I agree to the blog rules.

This Avian Waves blog is powered by a modified version of Presstopia Blog