Named Pipes Value set from SQL Server Network Utility in SQL 2000

Question

Post reply

Named Pipes Value set from SQL Server Network Utility in SQL 2000

SQL_Hunt

SSC-Dedicated

Points: 33518
More actions
April 14, 2010 at 4:10 pm

#386708

In the SQL Server Network Utility in SQL 2000, what value should be set for Named Pipes? By default for Named Pipes comes as: \\.\pipe\sql\query.
Do I need to retain the default value or do I need to change the Named Pipes value? Pls suggest ..
Thanks.

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

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

SQL_Hunt SSC-Dedicated Points: 33518 More actions · Answer 1

I'm trying to deploy a database from one of the servers to the server:SQLXX999YYY12

Do I need to change anything in the protocols? Pls suggest...

Error connecting to SQLXX999YYY12 (OSQL RC=1). [SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53]. CommandOutput id -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- - ----------- ----------- [SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53]. 1 NULL [SQL Native Client]Login timeout expired 2 NULL [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. 3 NULL NULL 4 NULL .

Thanks.

chandrakant_gaurav Right there with Babe Points: 799 More actions · Answer 2

Please make sure that you have installed Service pack 4. I recently configured my server for remote access using 2000 +SP4.

hope it helps.

NJ-DBA SSChampion Points: 13834 More actions · Answer 3

The proper value for named pipes configuration is: \\.\pipe\sql\query

I always have TCP/IP enabled as it seems to be less problematic.

I have seen that error message when network connectivity is not available (most clients try TCP/IP first, then named pipes).

From the client, can you telnet to the server on port 1433?

(just go to command line and enter "telnet servername 1433" If it goes to a black screen you have connected, if you get a message indicating that it "could not connect", either there is a network connectivity problem (perhaps a firewall in the way?) or the server is not listening on the default port.

Can you connect to the database from the server itself?

NJ-DBA SSChampion Points: 13834 More actions · Answer 4

Also- is the server you are connecting to configured to allow remote connections? (if 2005 check SQL Server Surface Area Configuration)