February 18, 2011 at 7:34 am
Good afternoon,
I have the following issue that i can't seem to "fix":
I have 2 instances: Instance A (primary 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 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,
SuperJB 😎
February 18, 2011 at 8:54 am
when you create a linked server you have several option regarding how to deal with connection authentication to the linked server. You will need to configure the method of authentication to remote server correctly. Right click on the linked server (in SSMC) , select properties and go to security tab.
The probability of survival is inversely proportional to the angle of arrival.
February 18, 2011 at 9:00 am
Check your security options in your linked servers. Anonymous means just that: as far as SQL is concerned you're not passing credentials.
Carlton.
February 18, 2011 at 9:04 am
As a test, have you tried creating a sql account on server B and using that for the linked server authentication ?
February 18, 2011 at 10:05 am
First off, thank you all for the replies.
My security options are IDENTICAL in machine A and B and IDENTICAL in Instance A and B. I have the same exact Logins and users in each instance.
And i can access access Instance A from Linked Server in Instance B but not the other way around.
I would understand the issue if the instances had different security properties, but they don't 🙁
Quick question, does anyone know if it's possible that SQL Server doesn't allow this 2way communication (from A to B and from B to A)?
SuperJB 😎
February 18, 2011 at 10:19 am
The fact that the linked servers security context are configured exactly the same on both instances doesn't mean a thing.
To illustrate my point, lets say instance A is installed under an administrative domain account, the other instance B, is installed under a local or system account. Even though both linked server security setups were set to allow the connection with no context, the one from A to B would work and the one from B to A would fail. Another example, you log in as on B with context set to "use the login context" and can access the A server. Then login as a non-sysadmin to Server A and try to do the same thing over to B and it fails.
Therefore you need to configure the linked server security appropriately according to how the linked server connection is going to be used and by whom.
The probability of survival is inversely proportional to the angle of arrival.
February 21, 2011 at 4:31 am
Thanks for the feedback sturner. That just may be the problem. As soon as i have some time, im gonna check that out.
SuperJB 😎
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply