![sql native client 10 dsn not connecting sql native client 10 dsn not connecting](http://vcloud-lab.com/files/resized/507894/931;540;bee52cbf9b5f4c65a98eba1ba26944a1b8958f11.png)
The instance named MSSQLSERVER isĪ default (unnamed) instance. In the right-pane confirm that the instance of the Database Engine is present and running.
![sql native client 10 dsn not connecting sql native client 10 dsn not connecting](https://filedb.experts-exchange.com/incoming/2015/08_w32/927032/ODBC---SQL-2014.png)
#Sql native client 10 dsn not connecting how to
For SSPI errors, see How to troubleshoot the "Cannot generate SSPI context" error message
![sql native client 10 dsn not connecting sql native client 10 dsn not connecting](https://www.ibm.com/support/pages/system/files/inline-images/image-20191218093811-2.png)
The server was not found or was not accessible.
#Sql native client 10 dsn not connecting windows
With a client running Windows 7, however the steps generally apply to other versions of SQL Server and other operating systems with only slight modifications. These steps are written for SQL Server 2008 R2 These steps assume that you are connecting to SQL Server from another computer by using the TCP/IP protocol, which is the most common situation. These stepsĪre in order of the most basic problems to more complex problems. These steps are not in the order of the most likely problems which you probably already tried. This is an exhaustive list of troubleshooting techniques to use when you cannot connect to the SQL Server Database Engine. We ran this same environment under 2008R2 with no issues.This topic was updated and moved into SQL Server Books Online in June. I really have no idea how to track this down. The 3 machines accessing SQL server are running as Terminal Servers. Since all machines are Guest VM on the same host, it should not be a network related issue. All machines in the equation are Windows server 2012 guest VM's hosted on Windows Server 2012 Hyper-V. After rebooting the machine the error goes away forĪwhile only to show up later at some other random time. When trying to connect I get the unable to connect via named pipes error when using Access DSN's or SQL Server Management studio. 2 servers never haveĪ problem, but one develops a connection problem in an almost random manner. In my environment I have 3 windows 2012 server that connect to SQL 2008 R2 using Native client 10 driver. I am having a connectivity issue which I believe is more related to the machine trying to connect than the SQL server itself.