Re: netbios and named pipes sql replication.

From: DC Stewart (donald.stewart2_at_alcoa.com)
Date: 09/07/04 

Date: Tue, 7 Sep 2004 13:50:13 -0400

-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

"Combfilter" <adsf@asdf.com> wrote in message
news:MPG.1ba7a7e4990ef73c9896a7@news.newsreader.com...
> A client that we replicate to is receiving some
> netbios request that are originating from our
> distribution server. I looked in the protocol
> section to see which protocol is on top. I
> assume the one on top is the order of which
> protocol it will try to use first. Both us and
> the subscriber have tcp/ip listed first.
> However, they are receiving netbios request from
> our machine. We have netbios over tcp/ip
> disabled. Therefore, i am guessing that the
> distributor is trying to use named pipes to
> communicate. Is this correct? Does named pipes
> even use netbios for discovery?
>
> tia..
> -comb

Relevant Pages

  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL Client protocol - not using tcp/ip
    ... my response here in case you didn't see it. ... How are you determining that the client is connecting using named pipes? ... the result of the last connection being cached. ...
    (microsoft.public.sqlserver.clients)
  • Re: What are these ports?
    ... >>properly it keeps the connection around long enough to make sure the close ... I do have MS NTP client turned off. ... > Since I am not using NetBios why does it seem that the ports are open? ... You will still be using NetBIOS locally even if you aren't using it over the ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cannot generate SSPI Context error
    ... changing to Named Pipes will connect. ... and the connection problem only lies in .NET code connections. ... And this connection string: ... > natively impersonate the client without calling the SSPI API. ...
    (microsoft.public.sqlserver.security)
  • Re: Samba connection fails
    ... Am trying to test the Samba configuration "offline" before connecting it to the network. ... The netbios name is the server's name your client pc's will see for those shares. ... Use a client computer and test the connection. ...
    (freebsd-questions)