Re: Cannot generate SSPI Context error

From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 11/09/04 

Date: Tue, 09 Nov 2004 20:14:18 GMT

Hi Peter,
   Sorry, looking at your code won't solve the problem. The best tools to
troubleshoot this are:

1. Network traces.
2. Netdiag.exe

To impersonate the client over TCP, we have to establish an additional
session with the DC. This is where it is failing.
It has really nothing to do with SQL or your code per say. Netdiag can be
use to see if there are problems communicating with the DNS server
and/or the Domain Controller. This is where you need to focus.

Kevin McDonnell
Microsoft Corporation

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

Relevant Pages

  • RE: win2000 vs msde 7
    ... Login failed user means esentially we're unable to impersonate the ... client. ... This can happen if you're using TCP and having problems reaching ...
    (microsoft.public.sqlserver.security)
  • RE: Yet another SSPI Error
    ... The SSPI error indicates that we're unable to impersonate the client over ... TCP. ... If you don't have DNS name resolution working properly and/or can't ...
    (microsoft.public.sqlserver.security)
  • Re: SQL2K server connect via ado TCP/IP failing
    ... Is there anyway I can get this to work, for Client B to connect ... and not on the workgroup with serverA. ... One of these can connect via TCP but the other can not. ... > impersonate the client using the SSPI API. ...
    (microsoft.public.sqlserver.connect)
  • Re: Problem with writing fast UDP server
    ... it likely means you have reached your ethernet bandwidth ... frames) to achieve your desired results. ... Keep in mind TCP is stream based, not datagram based so you may need ... On your client, make the following changes. ...
    (comp.lang.python)
  • Re: Debugger not working in Vs.net 2003
    ... I check The "Impersonate a client after authentication" user right, aspnet ...
    (microsoft.public.vsnet.debugging)
Loading