Re: Delegation through Linked Server Stops working

yes, when we restat the nodes the kerberos delegation starts to work for few
minutes and then stops with the 'login failed reason (null)' error....

"Sue Hoegemeier" wrote:

Are you having a completely different issue?
This post was about delegation working and then suddenly
failing until a reboot. Is this your issue?

-Sue

On Sun, 27 Aug 2006 12:23:01 -0700, DallasBlue
<DallasBlue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Is there a solution for this issue.

delegation on linked server fails in our network when we use
nt-authenticated logins. we have a sql server 2000 nodes (n1,n2) on win 2003
cluster.

Any thots,hints,links,pointers appreciated

thanks,
GA

"Sue Hoegemeier" wrote:

A few others have reported similar issues - with no
solutions. I worked at a place where we had delegation
sporadically failing and then working after reboots. A
ticket was opened with Microsoft but the issue was never
resolved. I would guess it's a Kerberos issue, not a SQL
issue. Make sure AD is clean and you don't have duplicate or
bad SPNs for all machines involved. Make sure all machines
involved have times sync working correctly, using the same
time server.
I'd suggest getting the Kerberos Delegation troubleshooting
doc available at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=99b0f94f-e28a-4726-bffe-2f64ae2f59a2&DisplayLang=en
We also installed a tool that would do verbose logging for
Kerberos errors - I just looked and couldn't find the tool.
Maybe if someone else knows they will jump in and provide a
link for that tool.
It can be a difficult issue to troubleshoot and you may want
to consider opening up a support ticket with Microsoft
Product Support.

-Sue

On Wed, 16 Aug 2006 12:43:01 -0700, Sheriff
<Sheriff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I have a Linked Server from SQL 2005 to a SQL 2000 server. I have it
configured to use delegation. This will work fine for a while and then
suddenly stop working. Sometimes it works for an hour, sometimes for a day.
I have to restart the SQL 2005 server and it will begin to work again. The
error is:

TCP Provider: An existing connection was forcibly closed by the remote host.
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.

Any ideas?




.

Relevant Pages

  • Re: Propagating caller identity across applications from a bare ASMX Service method to a WSE3 Servic
    ... Directory Domain as the server computer and the server App Pool run-as ... Windows 2003 Server mode -- they may be in Windows 2000 mixed mode. ... to be configured so as to use kerberos delegation. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: File Server delegation
    ... Identity) using a custom domain account required for Delegation? ... you're going to use kerberos delegation to make the ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Impersonation on Remote UNC
    ... It sounds like you need to implement Kerberos delegation. ... you to impersonate the authenticated browser user and let the web app ... to be able to authenticate. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Kerberos Delegation
    ... Yes, kerberos delegation is possible. ... Server S will FORWARD this to server T ... > about Delegation but ALL described Only one hop scenario. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Constrained delegation question!
    ... remote server running the services in terms of the security audits on the ... AUTHORITY\ANONYMOUS LOGON event. ... you won't be able to get Kerb delegation to ...
    (microsoft.public.dotnet.framework.aspnet.security)