Is using the named pipes protocol more/less secure and/or
slower than using tcpip to connect to SQL server?
"Colleen Rossman" <anonymous@.discussions.microsoft.com> wrote in message
news:136401c4aba9$c7ef54b0$a601280a@.phx.gbl...
> Is using the named pipes protocol more/less secure and/or
> slower than using tcpip to connect to SQL server?
Named Pipes is equally secure (ie, vulerable to ethernet sniffing).
In two special cases Named Pipes is faster: on the same machine, and over
local-area networks using the NetBUI protocol. In other cases TCP/IP is
faster, since in those cases Named Pipes would be running _over_ TCP/IP.
Remember that all the client netlibs date from before TCP/IP took over the
world. Back then you would choose the netlib which matched your LAN's
network protocol. Well today every network runs on IP, so everyone uses the
TCP/IP netlib.
David
Showing posts with label protocol. Show all posts
Showing posts with label protocol. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
Named Pipes and Clusters
Can the Named Pipes protocol be removed from a SQL Cluster
(SQL2000/Win2003)? And it still function properly, of course...
-Arnie Rowland
Hi Arnie,
No it cannot, see KB article:
831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
http://support.microsoft.com/?id=831127
Dave Whitney
SQL Support
This posting is provided "AS IS" with no warranties, and confers no rights.
(SQL2000/Win2003)? And it still function properly, of course...
-Arnie Rowland
Hi Arnie,
No it cannot, see KB article:
831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
http://support.microsoft.com/?id=831127
Dave Whitney
SQL Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Named Pipes
I am using TCP/IP for my network protocol. Is there any
need to use Named Pipes? I would like to remove this
protocol in SQL Server Network Utility.
Thank you.There's really no reason to remove it. It gives you an alternate IPC to
connect to the server with if for example we're unable to bind to the TCP
port. MDAC 2.6 clients then also have alternate means to connect to your
server. If they attempt to connect via sockets and fail, the client
transparently will attempt making a Named Pipe connection. This is of
great benefit to users who are no interested in how SQL connects, just that
it connects.
If your SQL Server is behind a firewall, the firewall should be configured
to only allow the tcp traffic for SQL. There's no additional overhead on
the server to listen on both netlibs.
If you're using a SQL Cluster then you won't be able to remove Named Pipes
after applying sp3.
831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
http://support.microsoft.com/?id=831127
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||If the SQL instance runs in a cluster, Microsoft advises
you not to remove the support for named pipes. Otherwise,
bad things can happen (See KB article 831127).
Also check out KB 818806 -- Some Named Pipes Features Are
Not Disabled After You Disable the Named Pipes Protocol.
I hate to run into an unexpected dependency at a most
inconvenient time, and have chosen to keep both named
pipes and TCP sockets as a standard.
Do you have any specific reasons for preventing SQL Server
from listening on named pipes?
Linchi
What are the exactly conditions for this 'transparent
attempt of making a Named Pipe connection' to occur? What
are scenarios in which this transparent attempt will not
be 'attempted'? I'm thinking about the situation when you
use a server alias or prefix your server name with 'tcp:'.
Linchi
alternate IPC to
bind to the TCP
connect to your
the client
connection. This is of
connects, just that
should be configured
additional overhead on
remove Named Pipes
Server That Is
confers no rights.
need to use Named Pipes? I would like to remove this
protocol in SQL Server Network Utility.
Thank you.There's really no reason to remove it. It gives you an alternate IPC to
connect to the server with if for example we're unable to bind to the TCP
port. MDAC 2.6 clients then also have alternate means to connect to your
server. If they attempt to connect via sockets and fail, the client
transparently will attempt making a Named Pipe connection. This is of
great benefit to users who are no interested in how SQL connects, just that
it connects.
If your SQL Server is behind a firewall, the firewall should be configured
to only allow the tcp traffic for SQL. There's no additional overhead on
the server to listen on both netlibs.
If you're using a SQL Cluster then you won't be able to remove Named Pipes
after applying sp3.
831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
http://support.microsoft.com/?id=831127
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||If the SQL instance runs in a cluster, Microsoft advises
you not to remove the support for named pipes. Otherwise,
bad things can happen (See KB article 831127).
Also check out KB 818806 -- Some Named Pipes Features Are
Not Disabled After You Disable the Named Pipes Protocol.
I hate to run into an unexpected dependency at a most
inconvenient time, and have chosen to keep both named
pipes and TCP sockets as a standard.
Do you have any specific reasons for preventing SQL Server
from listening on named pipes?
Linchi
quote:|||Kevin;
>--Original Message--
>I am using TCP/IP for my network protocol. Is there any
>need to use Named Pipes? I would like to remove this
>protocol in SQL Server Network Utility.
>Thank you.
>.
>
quote:
> If they attempt to connect via sockets and fail,
> the client transparently will attempt making a
> Named Pipe connection. This is of
What are the exactly conditions for this 'transparent
attempt of making a Named Pipe connection' to occur? What
are scenarios in which this transparent attempt will not
be 'attempted'? I'm thinking about the situation when you
use a server alias or prefix your server name with 'tcp:'.
Linchi
quote:
>--Original Message--
>There's really no reason to remove it. It gives you an
alternate IPC to
quote:
>connect to the server with if for example we're unable to
bind to the TCP
quote:
>port. MDAC 2.6 clients then also have alternate means to
connect to your
quote:
>server. If they attempt to connect via sockets and fail,
the client
quote:
>transparently will attempt making a Named Pipe
connection. This is of
quote:
>great benefit to users who are no interested in how SQL
connects, just that
quote:
>it connects.
>If your SQL Server is behind a firewall, the firewall
should be configured
quote:
>to only allow the tcp traffic for SQL. There's no
additional overhead on
quote:
>the server to listen on both netlibs.
>If you're using a SQL Cluster then you won't be able to
remove Named Pipes
quote:
>after applying sp3.
>831127 Named Pipes Support Cannot Be Removed on a Virtual
Server That Is
quote:
>http://support.microsoft.com/?id=831127
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
quote:
>
>.
>
Friday, March 23, 2012
name pipe VS tcpip
I found that I can only use name pipe to connect to the sql server.
When I use tcpip, it fails to connect.
I am sure I have enabled the TCP/IP protocol in SQL server
What causes it?
sql is using port no.1433 and I have try using dynamically determine port
and force it to 1433 in ODBC setting.
thank you very much
"!" <!@.!.!> wrote in message news:%236FqHb0qEHA.3416@.TK2MSFTNGP15.phx.gbl...
> I found that I can only use name pipe to connect to the sql server.
> When I use tcpip, it fails to connect.
> I am sure I have enabled the TCP/IP protocol in SQL server
> What causes it?
> sql is using port no.1433 and I have try using dynamically determine port
> and force it to 1433 in ODBC setting.
There are a lot of reasons that this can fail, application type being one of
them. Reference the following as a troubleshooting guide:
http://support.microsoft.com/default...b;en-us;827422
Steve
When I use tcpip, it fails to connect.
I am sure I have enabled the TCP/IP protocol in SQL server
What causes it?
sql is using port no.1433 and I have try using dynamically determine port
and force it to 1433 in ODBC setting.
thank you very much
"!" <!@.!.!> wrote in message news:%236FqHb0qEHA.3416@.TK2MSFTNGP15.phx.gbl...
> I found that I can only use name pipe to connect to the sql server.
> When I use tcpip, it fails to connect.
> I am sure I have enabled the TCP/IP protocol in SQL server
> What causes it?
> sql is using port no.1433 and I have try using dynamically determine port
> and force it to 1433 in ODBC setting.
There are a lot of reasons that this can fail, application type being one of
them. Reference the following as a troubleshooting guide:
http://support.microsoft.com/default...b;en-us;827422
Steve
Subscribe to:
Posts (Atom)