Re: How to force usage on NTLM

From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 03/29/05

  • Next message: Kevin McDonnell [MSFT]: "RE: Applying MS05-003 broke something..." 
    Date: Mon, 28 Mar 2005 22:12:59 GMT

    Well, one thing you could try is to force the connection to use Named
    Pipes. I believe the last time I tested this, Named Pipes would always
    authenticate via NTLM. Whereas with TCP to make a Trusted Connection we
    rely on SSPI and always try Kerberos first. Named Pipes can impersonate
    the client natively, and don't need to go thru the SSPI api. Essentially,
    there should be less overhead with Trusted Connections using Pipes that
    Sockets in this regard.

    Hope this helps,

    Kevin McDonnell
    Microsoft Corporation

    This posting is provided AS IS with no warranties, and confers no rights.

  • Next message: Kevin McDonnell [MSFT]: "RE: Applying MS05-003 broke something..."

    Relevant Pages

    • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
      ... remote connection. ... should I just check named pipes only or both TCP/IP and ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ...
      (microsoft.public.sqlserver.connect)
    • Re: Cannot generate SSPI Context error
      ... changing to Named Pipes will connect. ... and the connection problem only lies in .NET code connections. ... And this connection string: ... > natively impersonate the client without calling the SSPI API. ...
      (microsoft.public.sqlserver.security)
    • Re: Performance really poor if calling data from sql clients
      ... cannot see even in the profiler. ... recommendation of using TCP instead of Named Pipes to get performance. ... what is the problem with TCP as connection type? ... profiler to see what is happening on the sql server end. ...
      (microsoft.public.sqlserver.clients)
    • Re: strange ODBC connection problems
      ... We're using TCP for our connection, not named pipes. ... > Do you have the netbios protocol installed on the SQL server? ... >> just beat ODBC into doing DNS resolution, ...
      (microsoft.public.sqlserver.odbc)
    • Re: SQL 2000, Named Pipes and Windows 2003 Standard
      ... to the SQL using named pipes i get a security audit log. ... fixed a SQL Connection timeout that happened every so often. ... seperated the Web server and SQL Server onto our new Dell Blade systems ... Windows 2003 is ...
      (microsoft.public.sqlserver.connect)