Board index MS SQL Server

Client configuration (changing network protocol)

Client configuration (changing network protocol)

Post by Alexander Matevossia » Thu, 15 Apr 1999 04:00:00



Hi,

I tried to change the protocol to TCP/IP using SQL Server Client
configuration
utility, but I was unsuccessful.

Here is how I did it:

1. Started Sql client config util.
2. Went to Advanced tab.
3. Typed the server name in the "Server" edit box.
4. Selected TCP/IP Sockets in the DLL Name combo box
5. Pressed Add/Modify button.
6. Press Done button.

Then I ran ODBC applet in control panel and tried to configure the DSN.
After I pressed Next on the second step, I got the following error message:

Microsoft SQL Server Login:

Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft]ODBC SQL Server Driver][DBMSSOCN]General network error. Check
your network documentation.
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft]ODBC SQL Server Driver][DBMSSOCN]ConnectionOpen (connect()).

Once I changed the protocol back to named pipes, everything worked fine.  I
tried this with some variations (e.g., I entered server's IP address in the
connection string edit box, etc.) several times with the same result.

Thanks in advance for your help.

--
Regards,
Alex Matevossian.

 
 
 
Top

Client configuration (changing network protocol)

Post by Daniel Gar » Thu, 15 Apr 1999 04:00:00


Did you install TCP/IP when you installed SQL Server ? On 6.5 you have to
choose this as an option during install. If not run install and check the
"Change Network Support" option.

>Hi,

>I tried to change the protocol to TCP/IP using SQL Server Client
>configuration
>utility, but I was unsuccessful.

>Here is how I did it:

>1. Started Sql client config util.
>2. Went to Advanced tab.
>3. Typed the server name in the "Server" edit box.
>4. Selected TCP/IP Sockets in the DLL Name combo box
>5. Pressed Add/Modify button.
>6. Press Done button.

>Then I ran ODBC applet in control panel and tried to configure the DSN.
>After I pressed Next on the second step, I got the following error message:

>Microsoft SQL Server Login:

>Connection failed:
>SQLState: '08001'
>SQL Server Error: 11
>[Microsoft]ODBC SQL Server Driver][DBMSSOCN]General network error. Check
>your network documentation.
>Connection failed:
>SQLState: '01000'
>SQL Server Error: 10061
>[Microsoft]ODBC SQL Server Driver][DBMSSOCN]ConnectionOpen (connect()).

>Once I changed the protocol back to named pipes, everything worked fine.  I
>tried this with some variations (e.g., I entered server's IP address in the
>connection string edit box, etc.) several times with the same result.

>Thanks in advance for your help.

>--
>Regards,
>Alex Matevossian.


 
 
 
Top

1. Client Configuration (Network Library Configuration)

Hi all, I wrote a program using DTS in Delphi4.  The program works fine on
my development machine but not client machine.  I finally figured out that
if I install MSSQL7 on the client machine, when I create a ODBC label there
is a button, "Client Configuration" that allows me to enter Server Alias.
My question is do I have to install MsSQL7 on every single client machine?
I don't think so.  There should be an update to the ODBC or stuff like that
out there.

wooi.

2. Urgently need a Senior Sybase DBA.

3. Change Default Client Protocol or installing Client Utils

4. Where is DB*def...

5. Multi-Protocol SQL Server Client Configuration not working

6. DBI / DBD Informix -- Spaces in data

7. Network Protocol change

8. MDAC 2.5

9. Client Network protocol settings

10. Changing network protocol

11. Changing ADO network protocol - SQL Server OLEDB Provider

12. Changing Server's Network Protocol

13. Client network utility - Server alias configuration ?


All times are UTC
Board index