I am connecting to an Access 97 db on a network drive, in which all tables are linked to a SQL Server 2000 db through a DSN. I can access the tables fine from a Windows 2000 machine, but I get this error when I try to access the tables on an NT4 machine: Login failed for user '(null)'. Reason: Not associated with a trusted SQL. I do not want to use trusted security and the DSN does have a valid SQL Server user name and password. Please help!!!When you created the linked tables within the Access database you specify which DSN to use. That DSN must be defined on all machines that will use the linked tables within the Access database. Does the NT 4.0 workstation have the DSN defined on it? If so does it have trusted connection defined or Login/Password?|||I do have the dsn set up on both machines, but in further digging, I found this:
FIX: SQL Server ODBC Driver Ignores Authentication Setting (Q279526)
------------------------
The information in this article applies to:
Microsoft ODBC Driver for SQL Server, version 3.6
Microsoft SQL Server 2000 (all editions)
Microsoft Data Access Components version 2.6
------------------------
SYMPTOMS
When you use the SQL Server ODBC driver version 2000.080.0194, which was released with SQL Server 2000 and Microsoft Data Access Components (MDAC) 2.6 RTM, the authentication settings for ODBC data source names (DSNs) are ignored. The driver attempts to log directly into SQL Server using NTLM authentication (integrated security) without prompting for a user ID and password.
This can cause authentication failures, messages that database objects are not available, or unintentional modification of the wrong objects when copies of objects are maintained in multiple databases.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, please see the following article in the Microsoft Knowledge Base:
Showing posts with label linked. Show all posts
Showing posts with label linked. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
login failed for user "null"
Hello,
I have problem with linked servers (MS SQL Server 2k)- when I try to execute
query(update, insert..) with linked servers, I have message Login failed for
user 'null'. This is very strange problem, some computers in AD (2k3 std)
don't have this error, when the other have this problem for few hours and
some have this error all the time. Network Protocols is TCP/IP.
Any idea ?Are the linked servers set up to "Be made using the login's current security
context"? If that's the case, then I'm guessing that you are having a
problem with delegation. Review the BOL topic "Security Account Delegation"
this will get you going in the right direction. You will need to have a
domain admin assist you with this if you do not have domain admin rights.
After running the setspn command, it may take a while for the change to take
effect. (at least it did in my environment)
"dobrzak" wrote:
> Hello,
> I have problem with linked servers (MS SQL Server 2k)- when I try to execu
te
> query(update, insert..) with linked servers, I have message Login failed f
or
> user 'null'. This is very strange problem, some computers in AD (2k3 std)
> don't have this error, when the other have this problem for few hours and
> some have this error all the time. Network Protocols is TCP/IP.
> Any idea ?
>
>sql
I have problem with linked servers (MS SQL Server 2k)- when I try to execute
query(update, insert..) with linked servers, I have message Login failed for
user 'null'. This is very strange problem, some computers in AD (2k3 std)
don't have this error, when the other have this problem for few hours and
some have this error all the time. Network Protocols is TCP/IP.
Any idea ?Are the linked servers set up to "Be made using the login's current security
context"? If that's the case, then I'm guessing that you are having a
problem with delegation. Review the BOL topic "Security Account Delegation"
this will get you going in the right direction. You will need to have a
domain admin assist you with this if you do not have domain admin rights.
After running the setspn command, it may take a while for the change to take
effect. (at least it did in my environment)
"dobrzak" wrote:
> Hello,
> I have problem with linked servers (MS SQL Server 2k)- when I try to execu
te
> query(update, insert..) with linked servers, I have message Login failed f
or
> user 'null'. This is very strange problem, some computers in AD (2k3 std)
> don't have this error, when the other have this problem for few hours and
> some have this error all the time. Network Protocols is TCP/IP.
> Any idea ?
>
>sql
Monday, March 19, 2012
Login Failed for Linked Server
In EM I am trying to create a link between two SQL SQL2K servers using NT
domain logins. It works using SQL Server logins, but not with NT logins.
The error message is "Error 18456: Login failed for user 'NT
AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
servers. I have checked the 'be made using the logins current security
context' box in the security tab. I can run querys against the second
server, but I need to run a linked query. We are trying to keep to NT logins
for everything, so I prefer not to use SQL logins.DaveK wrote:
> In EM I am trying to create a link between two SQL SQL2K servers using NT
> domain logins. It works using SQL Server logins, but not with NT logins.
> The error message is "Error 18456: Login failed for user 'NT
> AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
> servers. I have checked the 'be made using the logins current security
> context' box in the security tab. I can run querys against the second
> server, but I need to run a linked query. We are trying to keep to NT logins
> for everything, so I prefer not to use SQL logins.
Hi
Try to look up "delegation" in Books On Line. There are a few settings
in your domain that has to be in place in order to use NT login for
Linked servers.
Regards
Steen
domain logins. It works using SQL Server logins, but not with NT logins.
The error message is "Error 18456: Login failed for user 'NT
AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
servers. I have checked the 'be made using the logins current security
context' box in the security tab. I can run querys against the second
server, but I need to run a linked query. We are trying to keep to NT logins
for everything, so I prefer not to use SQL logins.DaveK wrote:
> In EM I am trying to create a link between two SQL SQL2K servers using NT
> domain logins. It works using SQL Server logins, but not with NT logins.
> The error message is "Error 18456: Login failed for user 'NT
> AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
> servers. I have checked the 'be made using the logins current security
> context' box in the security tab. I can run querys against the second
> server, but I need to run a linked query. We are trying to keep to NT logins
> for everything, so I prefer not to use SQL logins.
Hi
Try to look up "delegation" in Books On Line. There are a few settings
in your domain that has to be in place in order to use NT login for
Linked servers.
Regards
Steen
Login Failed for Linked Server
In EM I am trying to create a link between two SQL SQL2K servers using NT
domain logins. It works using SQL Server logins, but not with NT logins.
The error message is "Error 18456: Login failed for user 'NT
AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
servers. I have checked the 'be made using the logins current security
context' box in the security tab. I can run querys against the second
server, but I need to run a linked query. We are trying to keep to NT login
s
for everything, so I prefer not to use SQL logins.DaveK wrote:
> In EM I am trying to create a link between two SQL SQL2K servers using NT
> domain logins. It works using SQL Server logins, but not with NT logins.
> The error message is "Error 18456: Login failed for user 'NT
> AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
> servers. I have checked the 'be made using the logins current security
> context' box in the security tab. I can run querys against the second
> server, but I need to run a linked query. We are trying to keep to NT log
ins
> for everything, so I prefer not to use SQL logins.
Hi
Try to look up "delegation" in Books On Line. There are a few settings
in your domain that has to be in place in order to use NT login for
Linked servers.
Regards
Steen
domain logins. It works using SQL Server logins, but not with NT logins.
The error message is "Error 18456: Login failed for user 'NT
AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
servers. I have checked the 'be made using the logins current security
context' box in the security tab. I can run querys against the second
server, but I need to run a linked query. We are trying to keep to NT login
s
for everything, so I prefer not to use SQL logins.DaveK wrote:
> In EM I am trying to create a link between two SQL SQL2K servers using NT
> domain logins. It works using SQL Server logins, but not with NT logins.
> The error message is "Error 18456: Login failed for user 'NT
> AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
> servers. I have checked the 'be made using the logins current security
> context' box in the security tab. I can run querys against the second
> server, but I need to run a linked query. We are trying to keep to NT log
ins
> for everything, so I prefer not to use SQL logins.
Hi
Try to look up "delegation" in Books On Line. There are a few settings
in your domain that has to be in place in order to use NT login for
Linked servers.
Regards
Steen
Login Failed for Linked Server
In EM I am trying to create a link between two SQL SQL2K servers using NT
domain logins. It works using SQL Server logins, but not with NT logins.
The error message is "Error 18456: Login failed for user 'NT
AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
servers. I have checked the 'be made using the logins current security
context' box in the security tab. I can run querys against the second
server, but I need to run a linked query. We are trying to keep to NT logins
for everything, so I prefer not to use SQL logins.
DaveK wrote:
> In EM I am trying to create a link between two SQL SQL2K servers using NT
> domain logins. It works using SQL Server logins, but not with NT logins.
> The error message is "Error 18456: Login failed for user 'NT
> AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
> servers. I have checked the 'be made using the logins current security
> context' box in the security tab. I can run querys against the second
> server, but I need to run a linked query. We are trying to keep to NT logins
> for everything, so I prefer not to use SQL logins.
Hi
Try to look up "delegation" in Books On Line. There are a few settings
in your domain that has to be in place in order to use NT login for
Linked servers.
Regards
Steen
domain logins. It works using SQL Server logins, but not with NT logins.
The error message is "Error 18456: Login failed for user 'NT
AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
servers. I have checked the 'be made using the logins current security
context' box in the security tab. I can run querys against the second
server, but I need to run a linked query. We are trying to keep to NT logins
for everything, so I prefer not to use SQL logins.
DaveK wrote:
> In EM I am trying to create a link between two SQL SQL2K servers using NT
> domain logins. It works using SQL Server logins, but not with NT logins.
> The error message is "Error 18456: Login failed for user 'NT
> AUTHORITY\ANONOYMUS LOGIN'. What am I doing wrong? I am the DBA on both
> servers. I have checked the 'be made using the logins current security
> context' box in the security tab. I can run querys against the second
> server, but I need to run a linked query. We are trying to keep to NT logins
> for everything, so I prefer not to use SQL logins.
Hi
Try to look up "delegation" in Books On Line. There are a few settings
in your domain that has to be in place in order to use NT login for
Linked servers.
Regards
Steen
Subscribe to:
Posts (Atom)