Now I should be able to use the machine name instead of the IP address to connect to the SQL Server. In the below image I added IP address 74.200.243.253 with a machine name of SQLDBPool. To add the entry in the /host file type %SystemRoot%\system32\drivers\etc\ in the run window and open the host file using Notepad. If it resolves using an IP address, you can add the SQL Server machine into /etc/host file. If not, you can try to connect to the SQL Server using an IP Address (for default instance) or IP Address\Instance Namefor a named instance. Make sure you are able to ping the physical server where SQL Server is installed from the client machine. Follow the below steps to see if you can resolve the issue. There could be several reasons you get these error messages.
In this tip, we look at what may be causes to these errors and how to resolve. These errors could be for either Named Pipes connections or TCP/IP connections. (provider: TCP Provider, error: 0 – No such host is known.) (Microsoft SQL Server, Error: 11001) Verify that the instance name is correct and that SQL Server is configured to allow remote connections. The server was not found or was not accessible.
A network-related error or instance-specific error occurred while establishing a connection to SQL Server.
