November 24, 2015 at 10:15 am
Hi guys,
Hope someone can help me out with this one; I'm having some trouble with a linked server.
The source server is SQL Server 2014, configured with an instance name and non-standard port, the SQL Browser service is DISABLED as part of our security configuration, connections from applications are done as follows:
Servername\Instance,PortNumber
Works great.
Destination server is SQL Server 2005, default instance and port.
If I log onto the console of the source server with RDP, I can set up the linked server as normal and it works fine. No issues.
If I try and connect to the source server from any other machine (ie, my desktop with SSMS) I get a login timeout expired when I try and access the linked server.
As part of my troubleshooting I disabled named pipes at the source server, and tried to access the linked server again. I am presented with the same error locally as I receive when trying to access it remotely.
I assume this is something to do with the protocols, but I've been spinning my wheels on this for a few hours now.
Any ideas?
Cheers.
November 24, 2015 at 6:49 pm
Do you have the linked server connections setup to "be made using the login's current security context"? If you do you likely are experiencing a double-hop authentication issue and you need to properly get Kerberos setup on both the SQL Servers. K. Brian Kelley has a good article on this site for Setting up Kerberos that can be found here.[/url]
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 25, 2015 at 9:06 am
Hi Jack,
Thanks for the reply. I wish it was that simple, I did think of that and changed the authentication method to a sql login. I probably should have mentioned that in the first post. Apologies.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply