Linked Servers fail with Integrated Authentication

Linked Servers fail with Integrated Authentication

Secure Home | Search | About
 Microsoft Applications Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Linked Servers fail with Integrated Authentication jwgoerlich 10-12-2007
Posted by on October 12, 2007, 4:39 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Hello group,

I have two SQL database servers. The first is SQL 2000, default
instance, hosted on Windows 2000 Server. The second is SQL 2005, named
instance, hosted on Windows 2003 Enterprise Server.

The DBAs manage the SQL servers from their client computers. Clients
and servers are in one AD Domain. The DBAs use Windows integrated
authentication to connect.

On the SQL 2000 server, I have created a linked server entry to point
to the SQL 2005 server. I did this with the following commands:

EXEC sp_addlinkedserver @server='2005server\instance',
@srvproduct='',
@provider='SQLOLEDB',
@datasrc='2005server\instance',
@catalog = 'master',
@provstr="Integrated Security=SSPI;";
EXEC sp_addlinkedsrvlogin '2005server\instance', 'true';

This link works if a query is executed from the server console. When
Query Analyzer is run from the DBA's computers, however,
authentication fails. The same user account is used both on the server
console and on the client.

The error is:

Server: Msg 18456, Level 14, State 1, Line 1
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

What steps should I take to successfully link the two SQL servers and
use integrated authentication?

J Wolfgang Goerlich


Posted by S. Pidgorny on October 13, 2007, 12:46 am
If you were  Registered and logged in, you could reply and use other advanced thread options
I would check the SPNs for SQL server service account.

Also: are you using the same account on the workstations that works on the
server console?

--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-

* http://sl.mvps.org * http://msmvps.com/blogs/sp *


> Hello group,
>
> I have two SQL database servers. The first is SQL 2000, default
> instance, hosted on Windows 2000 Server. The second is SQL 2005, named
> instance, hosted on Windows 2003 Enterprise Server.
>
> The DBAs manage the SQL servers from their client computers. Clients
> and servers are in one AD Domain. The DBAs use Windows integrated
> authentication to connect.
>
> On the SQL 2000 server, I have created a linked server entry to point
> to the SQL 2005 server. I did this with the following commands:
>
> EXEC sp_addlinkedserver @server='2005server\instance',
> @srvproduct='',
> @provider='SQLOLEDB',
> @datasrc='2005server\instance',
> @catalog = 'master',
> @provstr="Integrated Security=SSPI;";
> EXEC sp_addlinkedsrvlogin '2005server\instance', 'true';
>
> This link works if a query is executed from the server console. When
> Query Analyzer is run from the DBA's computers, however,
> authentication fails. The same user account is used both on the server
> console and on the client.
>
> The error is:
>
> Server: Msg 18456, Level 14, State 1, Line 1
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>
> What steps should I take to successfully link the two SQL servers and
> use integrated authentication?
>
> J Wolfgang Goerlich
>



Posted by on October 13, 2007, 5:47 am
If you were  Registered and logged in, you could reply and use other advanced thread options
> I would check the SPNs for SQL server service account.

Good idea. Will do.


> Also: are you using the same account on the workstations that works on the
> server console?

Yes. Oddly enough, it sporadically works from the workstations. This
is maybe once in twenty times, however. I am leaning heavily towards
this being an authentication issue.

J Wolfgang Goerlich


>
>
>
>
> > Hello group,
>
> > I have two SQL database servers. The first is SQL 2000, default
> > instance, hosted on Windows 2000 Server. The second is SQL 2005, named
> > instance, hosted on Windows 2003 Enterprise Server.
>
> > The DBAs manage the SQL servers from their client computers. Clients
> > and servers are in one AD Domain. The DBAs use Windows integrated
> > authentication to connect.
>
> > On the SQL 2000 server, I have created a linked server entry to point
> > to the SQL 2005 server. I did this with the following commands:
>
> > EXEC sp_addlinkedserver @server='2005server\instance',
> > @srvproduct='',
> > @provider='SQLOLEDB',
> > @datasrc='2005server\instance',
> > @catalog = 'master',
> > @provstr="Integrated Security=SSPI;";
> > EXEC sp_addlinkedsrvlogin '2005server\instance', 'true';
>
> > This link works if a query is executed from the server console. When
> > Query Analyzer is run from the DBA's computers, however,
> > authentication fails. The same user account is used both on the server
> > console and on the client.
>
> > The error is:
>
> > Server: Msg 18456, Level 14, State 1, Line 1
> > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>
> > What steps should I take to successfully link the two SQL servers and
> > use integrated authentication?
>
> > J Wolfgang Goerlich- Hide quoted text -
>
> - Show quoted text -



Posted by S. Pidgorny on October 13, 2007, 7:18 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
As for the authentication setup - use http://support.microsoft.com/kb/319723
as a checklist. There are many other articles - just search for "Kerberos
SQL".

Use Kerberos tray/klist to list Kerberos tickets on the client mahine; make
sure the TGT is there. Look for anomalies.

Keep us posted about your investigation please.

--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-

* http://sl.mvps.org * http://msmvps.com/blogs/sp *


>> I would check the SPNs for SQL server service account.
>
> Good idea. Will do.
>
>
>> Also: are you using the same account on the workstations that works on
>> the
>> server console?
>
> Yes. Oddly enough, it sporadically works from the workstations. This
> is maybe once in twenty times, however. I am leaning heavily towards
> this being an authentication issue.
>
> J Wolfgang Goerlich
>
>
>>
>>
>>
>>
>> > Hello group,
>>
>> > I have two SQL database servers. The first is SQL 2000, default
>> > instance, hosted on Windows 2000 Server. The second is SQL 2005, named
>> > instance, hosted on Windows 2003 Enterprise Server.
>>
>> > The DBAs manage the SQL servers from their client computers. Clients
>> > and servers are in one AD Domain. The DBAs use Windows integrated
>> > authentication to connect.
>>
>> > On the SQL 2000 server, I have created a linked server entry to point
>> > to the SQL 2005 server. I did this with the following commands:
>>
>> > EXEC sp_addlinkedserver @server='2005server\instance',
>> > @srvproduct='',
>> > @provider='SQLOLEDB',
>> > @datasrc='2005server\instance',
>> > @catalog = 'master',
>> > @provstr="Integrated Security=SSPI;";
>> > EXEC sp_addlinkedsrvlogin '2005server\instance', 'true';
>>
>> > This link works if a query is executed from the server console. When
>> > Query Analyzer is run from the DBA's computers, however,
>> > authentication fails. The same user account is used both on the server
>> > console and on the client.
>>
>> > The error is:
>>
>> > Server: Msg 18456, Level 14, State 1, Line 1
>> > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>>
>> > What steps should I take to successfully link the two SQL servers and
>> > use integrated authentication?
>>
>> > J Wolfgang Goerlich- Hide quoted text -
>>
>> - Show quoted text -
>
>



Posted by on October 19, 2007, 7:02 am
If you were  Registered and logged in, you could reply and use other advanced thread options
Definitely a Kerberos ticket issue. I can see it fail and then switch
to anonymous login. I have the SPNs setup for the service accounts.
Still, there is no delegation tab under the service account properties
in Users and Computers. This is strange because the SPN is working (I
checked in ADSIEdit) and we are in native Windows 2003 AD mode. By
chance, do you know how I can enable this tab?

J Wolfgang Goerlich

> As for the authentication setup - usehttp://support.microsoft.com/kb/319723
> as a checklist. There are many other articles - just search for "Kerberos
> SQL".
>
> Use Kerberos tray/klist to list Kerberos tickets on the client mahine; make
> sure the TGT is there. Look for anomalies.
>
> Keep us posted about your investigation please.
>
> --
> Svyatoslav Pidgorny, MS MVP - Security, MCSE
> -= F1 is the key =-
>
> *http://sl.mvps.org*http://msmvps.com/blogs/sp*
>
>
>
>
>
> >> I would check the SPNs for SQL server service account.
>
> > Good idea. Will do.
>
> >> Also: are you using the same account on the workstations that works on
> >> the
> >> server console?
>
> > Yes. Oddly enough, it sporadically works from the workstations. This
> > is maybe once in twenty times, however. I am leaning heavily towards
> > this being an authentication issue.
>
> > J Wolfgang Goerlich
>
>
>
> >> > Hello group,
>
> >> > I have two SQL database servers. The first is SQL 2000, default
> >> > instance, hosted on Windows 2000 Server. The second is SQL 2005, named
> >> > instance, hosted on Windows 2003 Enterprise Server.
>
> >> > The DBAs manage the SQL servers from their client computers. Clients
> >> > and servers are in one AD Domain. The DBAs use Windows integrated
> >> > authentication to connect.
>
> >> > On the SQL 2000 server, I have created a linked server entry to point
> >> > to the SQL 2005 server. I did this with the following commands:
>
> >> > EXEC sp_addlinkedserver @server='2005server\instance',
> >> > @srvproduct='',
> >> > @provider='SQLOLEDB',
> >> > @datasrc='2005server\instance',
> >> > @catalog = 'master',
> >> > @provstr="Integrated Security=SSPI;";
> >> > EXEC sp_addlinkedsrvlogin '2005server\instance', 'true';
>
> >> > This link works if a query is executed from the server console. When
> >> > Query Analyzer is run from the DBA's computers, however,
> >> > authentication fails. The same user account is used both on the server
> >> > console and on the client.
>
> >> > The error is:
>
> >> > Server: Msg 18456, Level 14, State 1, Line 1
> >> > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>
> >> > What steps should I take to successfully link the two SQL servers and
> >> > use integrated authentication?
>
> >> > J Wolfgang Goerlich- Hide quoted text -
>
> >> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -



Similar ThreadsPosted
Integrated Windows Authentication w/Netscape 8? December 27, 2005, 1:39 pm
Windows Integrated Authentication vs IE session credentials December 18, 2006, 5:11 pm
WSUS 3.0 console fail May 25, 2007, 7:17 am
MS05-039 breaks when integrated into unattended installs January 15, 2006, 7:11 pm
integrated fingerprint reader windows login feature January 4, 2006, 2:02 pm
User creation date on fail domain April 11, 2006, 11:55 am
How do I know if my computer has been linked to be viewed by anoth January 10, 2006, 2:42 pm
DMO & ADO connections fail even with valid credentials when using LOGON32_LOGON_NEW_CREDENTIALS flag with 'LogonUser' April 17, 2006, 9:19 am
problem with "Restricted Groups" within a GPO linked to my domain. January 22, 2006, 1:03 am
AOL Servers Probing ??? July 30, 2005, 12:16 pm

The site map in XML format XML site map

Contact Us | Privacy Policy