Using the SQLCMD in SQL 2005 Server - On using SQLCMD from the command line
(Page 2 of 5 )
One of the requirements for running the SQLCMD from the command line (in a DOS screen) is that the client and the server should be listening on/to the same TCP Port. If they are not, then the command line usage of SQLCMD results in an error as shown. While you do get an error message it is not very helpful. The only clue you get is the two words "TCP provider," if you can correctly guess. I wonder why they did not add another paragraph to this message.
C:Program FilesMicrosoft SQL Server90Shared>sqlcmd
HResult 0x274D, Level 16, State 1
TCP Provider: No connection could be made because the target machine
actively refused it.
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establishing a connection to the server. When connecting to SQL Server
2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
How do we correct the above condition?
Open the SQL Configuration Manager by going through All Programs -> MS SQL Server 2005 -> Configuration Tools -> SQL Server Configuration Manager and click as shown.

Next: SQL Server Network Connections >>
More MS SQL Server Articles
More By Jayaram Krishnaswamy