September 22, 2008 at 12:38 pm
hi guys , i am trying to link a sql server from one of my servers but i keep receiving this error message:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (.Net SqlClient Data Provider)
the way i am doing it is by going to Management Studio, linked servers, add linked server and then choosing under security Be made using the login's current security context. This works perfectly using my local server.
can you help find what should i look for?
September 22, 2008 at 1:05 pm
When using "Be made using login's current security context", SS2005 will use your logged in userid and password. If this is working on your server, where is it failing?
by using this option "Be made using login's current security context", you are saying that who ever the user is trying to use the linked server, has been added to the other server as well with the same userid and password (very useful when using windows auth').
Kindest Regards,
Shivaram Challa
(http://challa.net - Home of the "Excel to CSV converter & Browsepad applications".)
Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 22, 2008 at 1:08 pm
that's is what i thought, then do you know why it works from my local server and not this specific server, i am using the same login. Like i said i can connect to this server just fine from my local server. I have sysadmin access to all these three servers.
September 22, 2008 at 1:19 pm
I've had better luck with the commands vs the gui.
EXECUTE sp_addlinkedserver @server='remoteserver', @srvproduct='SQL Server'
EXECUTE sp_addlinkedsrvlogin @rmtsrvname='remoteserver', @useself='false',
@rmtuser='username', @rmtpassword='password'
MCITP, Database Administrator
A hodgepodge of Information Technology and Life
LinkedIn Profile
My Twitter
September 22, 2008 at 1:25 pm
My hunch is that its an authentication issue.
You can test it in two says.
(1) Try using "Be made using this security context" and enter the remote Login and password. If it works here, it means that your current security context somehow has a disconnect with the the remote login (may be a missing domain name, etc). If it doesnt work, check you remote login.
(2) Try adding the remote login to the "Local server login to remote server login mappings". In the dropdown, you should be able to see you local Id and then enter the remote userid and password. Checking Impersonate checkbox would use the local userid and password on the remote server, so you dont want to do that since that is what we want to test.
Kindest Regards,
Shivaram Challa
(http://challa.net - Home of the "Excel to CSV converter & Browsepad applications".)
Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 22, 2008 at 1:26 pm
Before adding a linked server, can you verify that you can actually ping both fully qualified name and IP address of linked server?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply