(e-mail address removed)
This would best be answered under database support .Although please find a
workaround as below:
WORKAROUND
By default, SQL Server will listen for incoming connections made by Named
Pipes clients. Named Pipes is the default IPC mechanism for clients to
connect to a SQL Server version 4.2, 6.0, and 6.5 server. The Named Pipes
DLL is Dbnmpntw.dll, and it should be located in the Windows\System or
Winnt\System32 directory. The TCP/IP sockets netlib DLL is Dbmssocn.dll,
and also should be in the Windows\System or Winnt\System32 directory.The
most common resolution to this problem is to configure the client computer
to connect using Named Pipes.
Configuring Named Pipes
If the Microsoft Data Access Components (MDAC) ODBC drivers have been
installed on the computer, you can make this change in the second step of
the Create New Data Source wizard.
NOTE: You can download MDAC drivers from:
http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid
=28001860
To configure the client, start the Create New Data Source wizard, click the
Client Configuration button, and perform the following steps, based on the
version of the SQL Server ODBC driver you are using:
For SQL Server ODBC Driver version 3.50
Click the Net Library tab and use the drop down list box to set the default
network (Net Library) to Named Pipes.
On the Advanced tab, remove any advanced entries that reference the server
you are connecting to.
Click Done.
For SQL Server ODBC Driver version 3.70
In the Network Libraries section of the Edit Network Library Configuration
dialog box, select Named Pipes.
Click OK.
If you do not have the MDAC ODBC drivers installed, you can use the SQL
Server Client Configuration Utility tool to set the default Net-Library to
Named Pipes. You can install the client utilities from the SQL Server CD
from the i386 directory.
Configuring TCP/IP Sockets
Server configuration:
In order for a client to connect to the SQL Server over TCP/IP sockets, the
server needs to be listening on the server side sockets library. To add
TCP/IP sockets support run SQL Setup.
Press Continue.
Press Continue again.
Select Change Network Support
Select TCP/IP Sockets
Press Continue to accept the default Pipe Name and TCP/IP socket port 1433.
Stop and restart the MSSQLServer service.
In order for you to confirm that your SQL Server is listening for incoming
sockets connections, the following line should be in the current SQL Server
error log found in \mssql\log. ods Using 'SSMSSO60.DLL' version
'6.5.0.0' to listen on '1433'.
Client configuration:
To configure the client, start the Create New Data Source wizard, click
Client Configuration, and perform the following steps, based on the version
of the SQL Server ODBC driver you are using:
For SQL Server ODBC Driver version 3.50:
Click the Net Library tab and use the drop down list box to set the default
network (Net Library) to TCP/IP Sockets.
OR
Leave the default Net Library set to Named Pipes and on the Advanced tab,
add a new entry where: Server := SQL Server Name
Network:= TCP/IP Sockets
Connection String: = IP Address,1433
(There are no spaces between the IP Address, the comma, and the port
1433)
Click Add/Modify.
Click Done.
For SQL Server ODBC Driver version 3.70:
In the Network Libraries section of the Edit Network Library Configuration
dialog box, select TCP/IP.
Enter the name of the SQL Server into the Server alias textbox
Change the Computer name to the actual IP address of the SQL Server.
Type 1433 in the port number textbox
Click OK.
LINKS:
=====
http://support.microsoft.com/default.aspx?scid=kb;en-us;195566
hth
This posting is provided "AS IS" with no warranties, and confers no rights.
