-1

I am trying to create a SQL linked server between two SQL servers.

  1. Logged into SSMS as my domain account, created the linked server with another domain service account on both source and target servers.The created linked server was unable to connect
  2. Then I tried - created a 'Test' SQL login and database user with db_dataread on the remote server. With Server authentication changed to SQL and Windows authentication, on both source and target servers, I logged into the source server as the 'Test' account and tested the linked server connection unsuccessfully.

Error message I get is "...A network-related or instance-specific error has occured while establishing a connection to SQL Server. Server is not found or not accessible...

Please note tcp port 1433 is open between source and target servers bi-directional.

The Security option I chose is "Be made using this security context" and I supplied the username and password.

Would anyone know what I'm missing please? I've tried different security options.

Improve this question
8
  • 3
    "Server is not found or not accessible" means it can't find the server, this has nothing to do with authentication. Are you sure you are able to ping the target and telnet into port 1433? Are you sure the instance is actually listening on 1433? Commented Nov 18 at 13:14
  • 1
    Please post the T-SQL or a screenshot of the UI used to create the linked server. Commented Nov 18 at 16:59
  • 1
    The error is that it can't connect to the other instance. Since we have no data for it we're not going to be able to help you other than to tell you it can't connect. Shouldn't matter which driver. Commented Nov 19 at 0:15
  • 1
    You say "port 1433 is open", but it could be that local firewall software on either of the servers could be blocking. If you log in to the "source" server, can you run SSMS on that server and successfully connect to the other server (not creating a linked server, just making a Database Engine connection to the other server, whether authenticating via the domain account, or the "Test" SQL account that you created)? Commented Nov 19 at 0:50
  • 1
    Sounds like you were actually using a named instance on a non-default port, contrary to what you said. Only default instances use TCP port 1433 by default, named instances use SQL Browser on UDP 1434 to find the port. Commented Nov 20 at 1:12

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.