Nt Authority Anonymous Logon Linked Server Error
Contents |
user …” ★★★★★★★★★★★★★★★ SQL Server ConnectivityAugust 10, 200678 Share 0 0 SQL Server 2005: “Login nt authority anonymous logon sql server 2012 failed for user ‘NT AUTHORITYANONYMOUS LOGON'”.
Login Failed For User 'nt Authority Anonymous Logon' Windows Authentication
= "urn:schemas-microsoft-com:office:office" />
SQL Server 2000: "Login failed for user "(null)". Reason: Not associated with what is nt authority anonymous logon a trusted SQL Server connection". The errors listed above is very typical when deploy linked server with delegation. They actually are thrown by the linkedMsg 18456, Level 14, State 1, Line 1 Login Failed For User 'nt Authority\anonymous Logon'.
server and pass by middle server to the client application. In this post, I will discuss how to properly configure SQL instances and Windows environment in most common scenario and try to make configuration steps as explicit as possible.
By using delegation in distributed query, such as linked server query, login failed for user nt authority anonymous logon asp net the SQL instance obtains impersonated token of the user logon credential to gain access to resources of another SQL instance, the linked server. In delegation setting, the client connection and linked server object are configured to use integrated authentication in SQL Server’s term as opposed to SQL login. Some time integrated authentication also referred as trusted connection or Windows authentication. Linked server login can also use SQL login, but it is not discussed here. To simplify the discussion, let’s assume two SQL Server instances are installed on machine A and B respectively. Also, let’s assume A is the middle server that has a linked server object configured which points to a SQL instance on machine B. If the client is on machine C different from A, we call it double-hop setting; if the client is collocated with middle server machine A, we call it single-hop setting. In single-hop setting, it ishere 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
Linked Server Windows Authentication
developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask
Linked Server Login Failed For User
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 login failed for user nt authority anonymous logon ssis them; it only takes a minute: Sign up SQL Server returns error “Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.” in Windows application up vote 28 down vote favorite 4 An application that has been working without problem (and has https://blogs.msdn.microsoft.com/sql_protocols/2006/08/10/sql-linked-server-query-failed-with-login-failed-for-user/ not had any active development done on it in about 6 months or so) recently began failing to connect to database. Operations admins cant say what might have changed that would cause the problem. The client application uses a hardcoded connection string with Integrated Security=True, but when the applications attempts to create a connection to the database, it throws an SQLException saying "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON". I can log on to the database through Management Studio http://stackoverflow.com/questions/12462674/sql-server-returns-error-login-failed-for-user-nt-authority-anonymous-logon on this account without problem. All of the things that I have seen for this issue are for ASP.NET projects and it is apparently the "Double Hop Problem" which being a client application darned well better not be a problem. Any help would be greatly appreciated. Edit The client machine and server machine as well as user accounts are on the same domain. This occurs when Windows Firewall is off. Leading theory is: Server was restarted about a week or so ago, and failed to register Service Principal Name (SPN). Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. sql-server security sqlconnection share|improve this question edited Sep 17 '12 at 16:57 asked Sep 17 '12 at 15:41 CodeWarrior 4,51732966 29 If you are going to downvote me, please give me a reason why you are doing it. This will do two things, it will give me constructive criticism which will allow me to better frame questions in the future, and it will give me the peace of mind that you are NOT serial downvoting me due to some perceived wrong. –CodeWarrior Dec 5 '12 at 14:50 2 Concur. Down votes should require a comment/reason –Breakskater Feb 7 at 0:13 add a comment| 4 Answers 4 active oldest votes up vote 13 down vote accepted If your issue is with linked servers, you need to look
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server http://www.sqlservercentral.com/Forums/Topic1206923-1526-1.aspx 2008 » Security (SS2K8) » Linked Server Error: Login failed for user... Linked Server Error: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Rate Topic Display Mode Topic Options Author Message winston http://serverfault.com/questions/88962/sql-server-to-sql-server-linked-server-setup Smithwinston Smith Posted Wednesday, November 16, 2011 9:47 AM SSC Eights! Group: General Forum Members Last Login: Tuesday, September 27, 2016 1:58 AM Points: 927, Visits: 2,033 I am setting nt authority up a linked server between two servers on my domain.I am using impersonate, so that its my own account that is used on the linked server.I set up both servers to use kerberos and confirmed its working (both servers running under domain accounts).im logged into my desktop pc, via my domain account.Now, when i try to query tables via the linked nt authority anonymous server i get the error:Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.I set up kerberos initially to get over this yet its still an issue. anyone able to help here?Thanks. Post #1206923 DevDev Posted Wednesday, November 16, 2011 10:02 AM SSCommitted Group: General Forum Members Last Login: Saturday, August 8, 2015 4:20 AM Points: 1,932, Visits: 1,598 It was a BUG in SS2K5 and MS claims it to be fixed. Time to re-open the defect I guess http://support.microsoft.com/kb/925001 Dev*** Open Network for Database Professionals ***http://www.linkedin.com/in/devendrashirbad Post #1206941 winston Smithwinston Smith Posted Wednesday, November 16, 2011 1:31 PM SSC Eights! Group: General Forum Members Last Login: Tuesday, September 27, 2016 1:58 AM Points: 927, Visits: 2,033 Would a bug of this scale ( its pretty big IMO that you cannot use linked servers with Windows Logins over Kerberos) go unfixed since sql server2000? Im using sql server 2008 R2 enterprise. Post #1207094 K. Brian KelleyK. Brian Kelley Posted Wednesday, November 16, 2011 1:48 PM Keeper of the Duck Group: Moderators Last Login: Friday, September 16, 2016 11:44 AM Points: 6,639, Visits: 1,905 Kerberos authenti
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 this site About Us Learn more about Stack Overflow 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 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 (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 54441123 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 security issues that make this harder than it should be. The words "Kerberos Authentication" will become the bain of most sys-admins/DBA's lives. It effectively is used for pass-through authentication. Here are the basics of what you need. 1) The servers (A and B) need to be set-up in Active Directory(AD) with delegation for Kerberos enabled. (this is set through your active directory admin panel) 2) The service account that your SQL Servers run under need to have delegation enabled also (this is also set through your active directory admin panel). - if they are not running under a service account, you need to create one. 3) The Servers need to have SPN's defined for the instance and the HOST and the machine name. (Using a tool called SetSPN in the windows support tools) Support Tools (SetSPN is in thi