servers and windows authentication

Hi,
Does anybody know if I can use linked server security
configuration with login's current security context for
windows authenticated sql server logins? I tested and it
doesn't work!!!
I have same windows nt sql server logins on both servers.
Linked server security is configured in a way that all
connections should be made using the login's current
security context (third option). It means that all windows
nt users should be able to refer database objects from the
linked server in their queries (using fully qualified
object name).
Well..., it is not true!
It works ONLY if windows nt user is connected locally to
the server where linked server is defined! However, if the
same windows nt user tries to do that from the client
computer, query fails with login incorrect message.
Did anybody try this? It's so stupid that I cannot believe
it's true.
ThanksI believe that problem is known as the "Double Hop" problem. There is some
information at the bottom of this page the explains:
http://support.microsoft.com/defaul...477&Product=sql
Also you might consider looking at this one:
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"OJ" <anonymous@.discussions.microsoft.com> wrote in message
news:228da01c45d51$a58a3990$a401280a@.phx
.gbl...
> Hi,
> Does anybody know if I can use linked server security
> configuration with login's current security context for
> windows authenticated sql server logins? I tested and it
> doesn't work!!!
> I have same windows nt sql server logins on both servers.
> Linked server security is configured in a way that all
> connections should be made using the login's current
> security context (third option). It means that all windows
> nt users should be able to refer database objects from the
> linked server in their queries (using fully qualified
> object name).
> Well..., it is not true!
> It works ONLY if windows nt user is connected locally to
> the server where linked server is defined! However, if the
> same windows nt user tries to do that from the client
> computer, query fails with login incorrect message.
> Did anybody try this? It's so stupid that I cannot believe
> it's true.
> Thanks|||Here is the other article I meant to paste in:
http://www.winnetmag.com/SQLServer/...3670/23670.html
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"OJ" <anonymous@.discussions.microsoft.com> wrote in message
news:228da01c45d51$a58a3990$a401280a@.phx
.gbl...
> Hi,
> Does anybody know if I can use linked server security
> configuration with login's current security context for
> windows authenticated sql server logins? I tested and it
> doesn't work!!!
> I have same windows nt sql server logins on both servers.
> Linked server security is configured in a way that all
> connections should be made using the login's current
> security context (third option). It means that all windows
> nt users should be able to refer database objects from the
> linked server in their queries (using fully qualified
> object name).
> Well..., it is not true!
> It works ONLY if windows nt user is connected locally to
> the server where linked server is defined! However, if the
> same windows nt user tries to do that from the client
> computer, query fails with login incorrect message.
> Did anybody try this? It's so stupid that I cannot believe
> it's true.
> Thankssql