FIX: The remote procedure call (RPC) client cannot connect to a server that is running SQL Server and is configured to use "Windows only" authentication (311111)

SYMPTOMS

Under the following conditions, a client application cannot connect to SQL Server:

The client uses the client components of SQL Server 7.0 (MDAC 2.1), or later.
The client wants to connect through Multiprotocol (Remote Procedure Call [RPC]).
The server is configured to use "Windows only" authentication.

If the preceding conditions are met, Odbcping.exe (found in the \x86\Binn folder of the SQL Server 2000 CD) produces this output:

COULD NOT CONNECT TO SQL SERVER

SQLState: 08001 Native Error: 11 Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.

SQLState: 01000 Native Error: 1775 Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake()).

The second error message that occurs may be different depending upon the client components that are installed and the SQL Server version of the target server. For example, this error message may occur:

ConnectionWrite(WrapperWrite()))

Client applications other than ODBCPING may only show this error message:

General network error. Check your network documentation.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later:

   Date          Time    Version    Size          File name
   -----------------------------------------------------------

   23-Oct-2001   01:43   8.00.460   29236 bytes   Dbmsrpcn.dll

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

WORKAROUND

To work around this problem either:

Change the authentication of the SQL Server to "SQL Server and Windows" (also known as "mixed mode").

-or-
Use a different network library.

NOTE: In SQL Server 2000, you can encrypt data "over the wire" by using all network libraries that use SSL encryption.

MORE INFORMATION

You can also use the fixed Dbmsrpcn.dll against SQL Server 7.0; however, the fix requires SQL Server 2000 Service Pack 1 as prerequisite.

NOTE: The file Dbmsrpcn.dll is a client-side component; you must install this fix on every affected client computer.