Mssql Linked Server Error 18456
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From linked server windows authentication My Forums Answered by: Linked Server error: Login Failed for linked server error 18456 login failed for user user 'NT AUTHORITY\ANONYMOUS LOGON' SQL Server > SQL Server Database Engine Question 0 Sign spn registered in to vote Good afternoon, I have the following issue that i can't seem to "fix": I have 2 instances: Instance A (primary linked server login failed databases for my application) and Instance B (relational databases for Reporting Services). Each instance is installed on a separate machine and both are included in the same domain. I can access Instance A from Machine B and i can access Instance B from Machine A (with both SQLServer
Login Failed For User Nt Authority Anonymous Logon Sql Server 2008 Linked Servers
Authentication and Windows Authentication)... no problem here. I've created a Linked Server connection from Instance B to Instance A without a problem. I can access all my databases from instance A in this linked server. The problem is creating Linked Server from Instance A to Instance B. I get no error creating it, but i can't access any databases from Instance B. I get the following error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' (Microsoft SQL Server, Error: 18456). I've been reading about this in some forums but no solutions seem to help... Any help please? Thanks in advance for any help, SuperJBJB Friday, February 18, 2011 2:57 PM Reply | Quote Answers 0 Sign in to vote This is most likely caused by the SPN onInstanceB not being set. Please see: http://blogs.msdn.com/b/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx Proposed as answer by WeiLin QiaoModerator
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of
Nt Authority Anonymous Logon Sql Server 2012
this site About Us Learn more about Stack Overflow the company Business Learn msg 18456 level 14 state 1 line 1 login failed for user more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ msg 18456, level 14, state 1, line 1 login failed for user 'nt authority\anonymous logon'. Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes https://social.msdn.microsoft.com/Forums/sqlserver/en-US/7e75b7d7-641f-4519-b5ea-9567985a2cce/linked-server-error-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldatabaseengine a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How can I get my linked server working using Windows authentication? up vote 8 down vote favorite I'm trying to get a linked server to ServerA created on another server, ServerB using "Be made using the login's http://dba.stackexchange.com/questions/44795/how-can-i-get-my-linked-server-working-using-windows-authentication current security context" in a domain environment. I read that I'd need to have SPNs created for the service accounts that run SQL Server on each of the servers in order to enable Kerberos. I've done that and both now show the authentication scheme to be Kerberos, however, I'm still facing the error: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'". In Active Directory, I can see that the service account for ServerB is trusted for delegation to MSSQLSvc, but I noticed that the service account for ServerA does not yet have "trust this user for delegation" enabled. Does the target server also need to have that option enabled? Is anything else necessary to be able to use the current Windows login to use a linked server? sql-server sql-server-2008 linked-server authentication kerberos share|improve this question asked Jun 18 '13 at 21:29 Christopher Garcia 2593510 add a comment| 1 Answer 1 active oldest votes up vote 9 down vote Every machine in the chain from your desktop to the server you are calling has to be Kerberos enabled for the trust to advance past the first hop. So, yes the server needs
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://serverfault.com/questions/88962/sql-server-to-sql-server-linked-server-setup and policies of this site About Us Learn more about Stack Overflow http://stackoverflow.com/questions/20923015/microsoft-sql-server-error-18456 the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it linked server works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SQL Server to sql server linked server setup up vote 24 down vote favorite 3 Please explain what is required to set up a SQL Server linked server. Server A is SQL 2005 windows logins only Server B is the same login failed for (SQL 2005 windows logins only) Server A runs windows XP Server B runs Windows Server 2003 Both SQL Server services are running under the same domain account. I am logged into my workstation with a domain account that has administrative rights on both SQL Servers. Note these are both SQL Server 2005 SP2 - I've had old hotfixes pointed out to me, but those are already applied. The issue I am having is this error: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Microsoft SQL Server, Error: 18456)" sql-server share|improve this question edited Nov 4 '12 at 3:44 MDMarra 87k23149292 asked Aug 28 '08 at 19:13 ScottStonehouse 53941123 migrated from stackoverflow.com Nov 28 '09 at 4:15 This question came from our site for professional and enthusiast programmers. add a comment| 9 Answers 9 active oldest votes up vote 18 down vote From My understanding of this issue it's a "HOP" issue. i.e. you are trying to use server A to relay your login details (with SSPI) to Server B. In SQL Server 2005 they have added a whole load of sec
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Microsoft SQL Server Error: 18456 up vote 50 down vote favorite 9 I am getting this error while trying to connect to the sql server. Microsoft SQL Server Error: 18456 Can anybody tell me what the error code means? sql-server connection error-code share|improve this question edited Jun 29 '15 at 13:28 ughai 8,37031238 asked Jan 4 '14 at 15:43 merazuu 4173716 5 A cursory search seems to indicate that the error code is a login failure, and is generally accompanied by more detailed information. –David Jan 4 '14 at 16:03 And that more detailed info should be in the sql server error log. The number itself deliberately doesn't tell you much, so crackers can't use it for clues on where their attempts are going wrong. –Tony Hopkinson Jan 4 '14 at 16:10 8 @David if you see a duplicate question in SO, then mark this as such. Just because the answer is easy to come by, doesn't mean it doesn't belong on SO. This is the first hit on Google after all :). –Josh Noe Feb 24 '14 at 19:52 add a comment| 7 Answers 7 active oldest votes up vote 112 down vote accepted if you're trying to connect using "SQL Server Authentication" then you may want to modify your server authentication ; Right click server and click properties go to security page under Server authentication, choose the SQL