Microsoft SQL Server Native Client 10.0 Login timeout expired

47,089

Solution 1

I ran into the same problem. I used -S, instead of -s, and removed the "" before and after the servername\instance. Everything ran great after that.

Solution 2

Maybe a little late on the draw here but for future readers with the issue: Try running Command Prompt as Administrator.

Solution 3

In the named pipes properties just change the path to \\.\pipe\sql\query instead of default path

Solution 4

I had this same thing happen to me for a client trying to setup a new SQL-Server box.

Open your SQL-Server configuration manager on the machine where SQL is actually INSTALLED.

Look to the SQL Native Client 10.0 Configuration. Under that is Client Protocols. You probably have TCP/IP and Named Pipes DISABLED. You need to ENABLE them.

Sample here

Share:
47,089
Xian Garcia
Author by

Xian Garcia

Updated on July 12, 2022

Comments

  • Xian Garcia
    Xian Garcia almost 2 years

    I have a freshly installed SQL Server 2008 R2 Express. I'm trying to run SQLCMD locally (please do take note locally) but I am receiving the error:

    Named Pipes Provider: Could not open a connection to SQL Server [2]
    Sqlcmd: Error: Microsoft SQL Serve Native Client 10.0 : 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 informations see SQL Server Books Online..
    Sqlcmd: Error: Microsoft SQL Server Native Client 10.0: Login timeout expired.

    Why can't I make it work? I already tried everything.

  • Frank Bailey
    Frank Bailey almost 10 years
    Good advice. This should be higher.
  • Savage
    Savage about 4 years
    In my case I had to do this under the SQL Server Network Configuration tree rather, plus changing the path to \\.\pipe\sql\query as mentioned elsewhere