If I understand your question correctly I think you are running into
double-hop issue? Are you using Windows Authentication? If yes you may have
to turn on delagation at the AD level. the other alternate is to use SQL
Server accounts on all the servers to avoid double-hop issue. Check if this
is what you are experiencing:
http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx --
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide Microsoft SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
Register (Free):
http://www.sqlcommunity.com/RegistrationLoginPage/tabid/68/Default.aspx?returnurl=%2fHome%2ftabid%2f36%2fDefault.aspx
[quoted text, click to view] "Randy Galliano" wrote:
> Hello,
>
> I a fairly complicated situation to explain in a newsgroup, but I am going
> to give it a try:
>
> 1. I have an SQL 2005 server (call it Server A) with a database. In the
> database is a view pointing that queries a table pointing to a linked
> server, Server B (#2 below). The permissions are set up properly and I can
> query the view from this server.
> 2. SQL 2005 server (Server B) with a
> database that is linked to from server A.
> 3. Using SQL Management studio from another SQL2005 server (Server C), or
> an Access database running the view Server A.
>
> The scenario:
>
> 1. When I go to run the a query from SQL Management studio on Server C, I
> get an error message saying no valid login for NT Authority\Annnomous
> Logon.
> 2. If I go to server A and run the query, then I can come back to Server C
> and the query run just fine. It will stay connected and run for a period
> of time, then I get the login error again.
>
> It almost appears as if the server where the query and linked server are
> defined, is passing through the proper permissions and creating a
> connection to the linked server, only if it initiates the connection.
> Then it appears the connection stays open for a period of time, then it
> closes.
>
> Does this make any sense? I can replicate it every time, but still cannot
> figure out why we get the login failure.