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.
ThanksHere is the other article I meant to paste in:
http://www.winnetmag.com/SQLServer/Article/ArticleID/23670/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.
> Thanks|||I 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/default.aspx?scid=kb;en-us;238477&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
Showing posts with label current. Show all posts
Showing posts with label current. Show all posts
Wednesday, March 21, 2012
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.
Thanks
I 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/default...77&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
|||I 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/default...77&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/A...670/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.
> Thanks
|||Here is the other article I meant to paste in:
http://www.winnetmag.com/SQLServer/A...670/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.
> Thanks
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
I 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/default...77&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
|||I 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/default...77&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/A...670/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.
> Thanks
|||Here is the other article I meant to paste in:
http://www.winnetmag.com/SQLServer/A...670/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.
> Thanks
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
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
Friday, March 9, 2012
server...Help!
I've searched the forum for a suitable solution for our current issue here.
Unfortunately, I'm yet to find a situation exactly matching ours.
I'm testing the linked server for SQL Server 2K to DB2/AS400. I've created the DSN and the linked server but I got the following message:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Microsoft][ODBC Driver
Manager] Driver's SQLSetConnectAttr failed]
[OLE/DB provider returned message: [IBM][Client Access ODBC Driver
(32-bit)][DB2/400 SQL]Communication link failure. COMM RC=0x3]
We're using Client Access V3R1M2 and I'm testing on a Windows 2K Pro PC. I also tried at a Windows 2K Server. Our AS400 is V3R7. We can't buy additional tools nor upgrade the Client Access for now.
Please help.What this error is saying is basicly you haven't set up your odbc driver yet. You need to set it up before you can set up you linked server. I hope this helps.;)|||I don't think it's possible for me to create a DSN without having a driver installed. I configured a Client Access DSN which points to the AS400 Server.
Or are you talking about a different driver which I should install on the SQL Server box?
:confused:|||I ran into the same problem, until we installed the latest version of Client Access Express and its service pack. Once that was done and the DSN was configured, it worked like a charm.|||CA-Express is not available for our current version. We need millions in order to get the upgrade. We can't do that for the moment.
Unfortunately, I'm yet to find a situation exactly matching ours.
I'm testing the linked server for SQL Server 2K to DB2/AS400. I've created the DSN and the linked server but I got the following message:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Microsoft][ODBC Driver
Manager] Driver's SQLSetConnectAttr failed]
[OLE/DB provider returned message: [IBM][Client Access ODBC Driver
(32-bit)][DB2/400 SQL]Communication link failure. COMM RC=0x3]
We're using Client Access V3R1M2 and I'm testing on a Windows 2K Pro PC. I also tried at a Windows 2K Server. Our AS400 is V3R7. We can't buy additional tools nor upgrade the Client Access for now.
Please help.What this error is saying is basicly you haven't set up your odbc driver yet. You need to set it up before you can set up you linked server. I hope this helps.;)|||I don't think it's possible for me to create a DSN without having a driver installed. I configured a Client Access DSN which points to the AS400 Server.
Or are you talking about a different driver which I should install on the SQL Server box?
:confused:|||I ran into the same problem, until we installed the latest version of Client Access Express and its service pack. Once that was done and the DSN was configured, it worked like a charm.|||CA-Express is not available for our current version. We need millions in order to get the upgrade. We can't do that for the moment.
Subscribe to:
Posts (Atom)