SQL Server 2008 Link Server Connection Error

Question

Post reply

SQL Server 2008 Link Server Connection Error

tamil.selvanmca

Ten Centuries

Points: 1367
More actions
April 8, 2013 at 5:48 am

#270682

Sir,
I am working in Medical college campus.They have 5 server in our campus.
I have done a Port for SQL 1433 Both Server are activate an also Named Pipes Provider are Enable,TCP/IP is Enabled in Both Server.In Configuration Manager SQL Browser is running and SQL SERVER (MSSQLSERVER) also running.When connection Link server the following Error as occurred.
TITLE: Microsoft SQL Server Management Studio
------------------------------
The linked server has been created but failed a connection test. Do you want to keep the linked server?
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Named Pipes Provider: Could not open a connection to SQL Server [53].
OLE DB provider "SQLNCLI10" for linked server "172.17.15.100" returned message "Login timeout expired".
OLE DB provider "SQLNCLI10" for linked server "172.17.15.100" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". (Microsoft SQL Server, Error: 53)

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

arnipetursson SSCertifiable Points: 6557 More actions · Answer 1

Is the IP correct? can you ping it from the server originating the connection?

Could be firewall or you are not using the right port number.

Lowell SSC Guru Points: 323518 More actions · Answer 2

172.17.15.100 looks like a public IP address, and not something on a private LAN;

typically, external servers are locked down to ignore everything except port 80(http).

if these servers are not on a LAN, you'll most likely need to get with your network guys to resolve connectivity.

In my shop, for example, we would not open our ports, but instead set you up with a VPN to get you on the LAN, so you can connect via server name instead of the external IP.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

tamil.selvanmca Ten Centuries Points: 1367 More actions · Answer 3

IP is Ping Correctly and also SSMS are login to access database

timscronin SSCertifiable Points: 6851 More actions · Answer 4

forget the port issue, start simple

"Check if instance name is correct and if SQL Server is configured to allow remote connections"

Did you check this on the remot instances you are trying to connect to. Also you may run profiler for a second on the remote server and see if you see any activity from this server