WinAuth slower than SQLAuth (SSMS)

  • WinAuth is much slower than SQLAuth in my SSMS.

    I am talking about Authentication.

    With WinAuth it takes 10 seconds - showing Databases (expanding..)

    How to troubleshoot this ?

  • RVO (10/4/2016)


    WinAuth is much slower than SQLAuth in my SSMS.

    I am talking about Authentication.

    With WinAuth it takes 10 seconds - showing Databases (expanding..)

    How to troubleshoot this ?

    A few things you may want to check -

    I'd start by checking DNS settings - ipconfig /all and check the DNS server entry.

    When connected, check the auth_scheme in sys.dm_exec_connections to see if you are connecting via NTLM or Kerberos - that can also indicate what you need to troubleshoot. If NTLM is slow, check the servers connectivity to the Domain Controllers. If Kerberos is slow, check your own (client side) connectivity to the Domain Controllers.

    Sue

  • Where do I need to run

    ipconfig /all

    ?

    On SQL Server physical box?

    I don't have physical access to the box.

    ------------------------------------------------------------

    ------------- More details: ------------------------------

    ------------------------------------------------------------

    i am on BLL domain.

    SQL Server is on BLL-SG domain

    nslookup results:

    -------------------

    C:\>nslookup

    Default Server: bnddc05.bbl.local

    Address: 10.150.104.3

  • When I run

    select * from sys.dm_exec_connections

    In auth_scheme

    I see:

    SQL - majority of records

    NTLM - maybe 10%

    (Unknown) - 1%

  • But keep in mind.....

    When I connect using SQL Authentication

    it is fast.

    So probably it's not DNS issue.

    Could it be connection to ActiveDirectory issue?

  • Ping works fine:

    ping BNDARGSQLP51.bbl-sg.local

    Pinging BNDARGSQLP51.bbl-sg.local [10.146.173.51] with 32 bytes of data:

    Reply from 10.146.173.51: bytes=32 time=1ms TTL=126

    Reply from 10.146.173.51: bytes=32 time=2ms TTL=126

    Reply from 10.146.173.51: bytes=32 time=2ms TTL=126

    Reply from 10.146.173.51: bytes=32 time=2ms TTL=126

  • Can you ping by IP? I would guess you have network admins and these issues should be presented to them as well.

    If you can ping by IP but not by name, the server name isn't resolving which is a function of DNS.

    You could try adding the server to your host file as a temporary fix until the issues are resolved.

    Sue

  • Sorry.

    PING is ok.

    I wasn't using full name correctly.

Viewing 8 posts - 1 through 7 (of 7 total)

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