Post reply

SQL Server 2008 is supposed to support Kerberos over Named Pipes, but I cannot get it to work.

  • March 5, 2012 at 2:57 pm

    #256917

    Could anyone else test this as well? It's driving me crazy. I've been asked to test if Named Pipes can now be used for Linked Servers.

    http://technet.microsoft.com/en-us/library/ms191153.aspx

    So I can specify TCP:<MyRemoteServer>\<MyInstance>

    And running:

    select * from sys.dm_exec_connections where session_id=@@spid

    Would show auth_method as KERBEROS

    As soon as I connect via NP:<MyRemoteServer>\<MyInstance> it always defaults to NTLM.

    Keep in mind that I've created the SPNs correctly and according to the technet above. I also see no errors in the security events log. It seems to chose straight away NTLM and not really a failover situation.

    Can any DBA/Dev with 2 SQL 2008 boxes test as well?

  • March 7, 2012 at 9:40 am

    #1456102

    Bump, another link:

    http://technet.microsoft.com/en-us/library/cc280562.aspx

    Kerberos Authentication

    Beginning in SQL Server 2008, support for Kerberos authentication is expanded to include the named pipes and shared memory protocols. In addition, Kerberos can be used without requiring Windows Active Directory. For more information, see Kerberos Authentication and SQL Server.

  • March 27, 2012 at 9:23 am

    #1465063

    I just tested this with SQL 2012 (remote SQL 2012 mgmt studio to 2012 server). Same issue.... TCP connects using KERBEROS, named pipes keeps using NTLM only.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply