January 20, 2010 at 2:43 pm
I have a install of SQL Server 2008 SP1 on Windows 2003 Standard OS - default instance.
It is installed using a non-standard port, let's say 1234.
I manually registered my SPN, and it is showing up in AD just fine.
I have SQL Browser running.
I connect to the default instance using ONLY the name.
I see I've connected using Named Pipes and NTLM auth.
So...
I stop my browser.
I connect using my instance,portnumber.
Now, I see I connected using TCP/IP and Kerberos (this is what I want)
So...
I leave my browser off.
I create an alias for my connection.
I re-connect using my alias.
Now, my connection is Named Pipes, NTLM again... oh boy.
What can I do to allow my client to connect to a non-standard port WITHOUT having to specify the port number ans use TCP/IP and Kerberos?
Your feedback is much appreciated!!!
HawkeyeDBA
January 20, 2010 at 11:00 pm
Have you tried disabling Named Pipes?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 21, 2010 at 6:43 am
Funny, I had a sort of similar issue the other day. I disabled named pipes on client and server and now every connection is though tcp/ip.
Many years ago I actually had to remove the named pipes dll to stop it being used ( sql 2000 ) a somewhat complicated setup within a dmz running through two layers of translation - every so often it would insist on using named pipes despite only tcp/ip being set.
You can define tcp/ip in the alias btw.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
January 21, 2010 at 6:59 am
Yep, that was a disaster because anything that connected to the server as the server name rather than a fully qualified <servername>,<portnumber> failed 🙁
January 21, 2010 at 7:00 am
Yep, I was hoping for that too! I tried, believe me LOL
It's configured for tcp on the alias.
Did you have to make sure the apps were connecting with the port number specified? That DOES work, otherwise, maybe it's a network protocol issue?
January 21, 2010 at 7:03 am
I just re-read your post Grumpy...
You disabled named pipes on the client? That may be the issue... where do I check for that? I checked the client's network protocol thru control panel and it is using tcp/ip but is there something I'm missing maybe?
January 21, 2010 at 8:22 am
Ok,
I checked the client and the tcp protocol is first under the Client registry for MSSQLServer SN10.0.
So.. I changed the connection to the database to servername,portnumber in the registry for that app (it is SMS) and re-started the app services, and now it connects as tcp/ip.
Now that I have named pipes disabled I cannot connect to SQL Server through managament studio WITHOUT using the port number.
If anyone has more info on this please please let me know. I would like to avoid using the port number in my app connections if possible.
Thanks again!
February 3, 2010 at 10:40 am
Did anyone have any extended knowledge on why sql server will not use tcp/ip when an alias or sql browser is used to connect to sql server on a non-standard port without specifying a port number?
Just curious, I'd like to have all connections using tcp/ip without having to specify the port by using either the alias or the browser, but for now I have to settle for named pipes or have the app use the port number to connect 🙁
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply