Error while connecting to remote server

  • Hi,

    I am getting error when i tried to connect to remote server by using server name.

    Error:

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

    When I tried to connect using Ip address, i am able to connect to the server but cannot able to connect using server name. What may be the reason for this? Please suggest..

    Thanks.

  • If you can also connect using the FQDN then it's often a DNS issue.

    You could try doing a DNS flush on your end and see if that helps.

    Sue

  • I can't even connect using FQDN , it is giving the same error.

  • If pinging by server name fails but by IP succeeds, the problem is most likely with name resolution. You can still try flushing DNS on your PC with:

    ipconfig /flushdns

    You can do a tracert to the server by both name and IP and see if that helps identify an issue in the network.

    Make sure you are pointing to the correct DNS server - ipconfig /all

    Check the servers DNS entry as well.

    Verify that the correct records are registered in the DNS for the server.

    You can do an nslookup and see if you are getting errors finding the server (can't resolve name), a timeout which would indicate configuration issues in the environment, a No Response would mean the DNS servers can't be reached or are unavailable.

    If your on an older network or not using a DNS server, you could update your host file in Windows\System32\drivers\etc

    You can also do that if you don't want to go through all of this and don't have network support where you are. But if the IP changes for that server, it can backfire on you.

    Sue

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

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