Re: netbios and named pipes sql replication.

From: Combfilter (adsf_at_asdf.com)
Date: 09/08/04


Date: Wed, 8 Sep 2004 09:38:32 -0500

In article <10jrt6rrko7fc4e@news.supernews.com>,
donald.stewart2@alcoa.com says...
> -comb
>
> yes Named Pipes uses netbios.
>
> we had a situation after apply a MS patch to the SQL server which disabled
> netbios connections (security hole).
>
> Clients (ODBC) which had been setup to use TCP/IP would switch to named
> pipes if the TCP/IP connection could not be made or was dropped sometine in
> the life of the ODBC. Once the client switched to named pipes, it never
> switches back to TC/IP. It remains at the last protocol it made a good
> connection with.
>
> When we took named pipes support off the SQL server with the MS patch, those
> clients could not connect.
>
> We had to manually walk thru the ODBC setup and configure the CLIENT
> CONFIGURATION to use the TCP/IP library.
>
> Even if the client was using a native or 3rd party connector the client uses
> the last good connection library to make all subsequent connections to that
> SQL server.
> It is actually stored in the registry, but the easiest way to change it is
> thru an ODBC configuration.
>
> You may have a similar issue with the distributor server acting as the
> client in this case.
>
> DS
>
>

Thanks DS..

I believe this is exactally what is happening.

It's interesting to know that it defaults to the
last known good protocol. I figured it would
always try to connect with the first protocol in
the list.

I appreciate the info.

-comb



Relevant Pages

  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
    ... remote connection. ... should I just check named pipes only or both TCP/IP and ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ...
    (microsoft.public.sqlserver.connect)
  • Re: Connection Error: ADO.Net and SQL Server 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... I can connect to the server through an ODBC connection ... It is very puzzling because this client doesn't seem to have anything ...
    (microsoft.public.sqlserver.connect)
  • RE: Error 17835 - When encryption and Shared Memory are enabled
    ... Did you encounter this error when you connected to your SQL Server ... Did your SQL Server instance use a certificate explicitly specified by ... you configure your client connection settings "Force Protocol Encryption" ...
    (microsoft.public.sqlserver.connect)
  • Re: Losing connections with SQL 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server automatically detects if the client falls into the sea or gets ... Does the Connection pooling mechanism do this on its ... Upgrading our app is a really big task, ...
    (microsoft.public.sqlserver.connect)
  • Re: Problem connection to SQL Server with ODBC
    ... What protocols are being used by the client and what is the ... Are you using an alias for the connection? ... SQL Server Clients May Change Protocols When They Try ...
    (microsoft.public.sqlserver.connect)