netbios and named pipes sql replication.

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
-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.co m...
> 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
|||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