Re: How can I tell what protocols are enabled for the client?

From: peter (peter_at_discussions.microsoft.com)
Date: 06/22/04 

Date: Mon, 21 Jun 2004 22:42:01 -0700

Hi Mark,

I just want to make sure that we're talking about the same area. My question is on the Client Network Utility not on the Server Network Utility.

Based on your reply, even I have only enabled TCP/IP on the General tab of the Client Network Utility, I will still able to connect to an alias which is setup using Named Pipes on the Alias tab of the Client Network Utility.

"Mark Ferguson" wrote:

> If your application connects thru the alias, then the protocol for the
> alias is used. If the application connects thru the instance then the
> *enabled* protocols for the instance are used.
>
> See the following
> http://support.microsoft.com/default.aspx?kbid=814130 (How to help
> secure network connectivity for SQL Server 2000 local databases)
> and
> http://support.microsoft.com/default.aspx?scid=/support/servicepacks/SQL/2000/SP3aReadMe.asp
> (The Readme file for SP3)
> and
> The SQL Server Books Online (find on the microsoft.com, download and
> install)
>
> On Mon, 21 Jun 2004 14:34:02 -0700, "=?Utf-8?B?cGV0ZXI=?="
> <peter@discussions.microsoft.com> wrote:
>
> >If on the General tab of the Client Network Utility, TCP/IP is the only protocol enabled. Does it mean that other protocols are disabled and will not be used in communicating to SQL Servers on other machines?
> >In this case, should the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib only contains the Tcp entry?
> >If I have alias setup to use other protocol such as Named Pipes, does it mean the alias cannot be connected since Named Pipes is not enabled?
> >
>
>

Relevant Pages

  • Re: How can I tell what protocols are enabled for the client?
    ... The client and server use only the protocols enabled ... using the alias, only the protocls enabled for the alias are used. ... My question is on the Client Network Utility not on the Server Network Utility. ...
    (microsoft.public.sqlserver.connect)
  • Re: .NET Data Adapter not taking Alias added in ClientNetwork Utility
    ... I wasn't aware that .NET would even look at the client network utility. ... SQL Server / client network utility is not always going to be installed ... > I am in Administrators and hence was able to add the ALias. ...
    (microsoft.public.sqlserver.server)
  • Re: Client Network Utility
    ... You really do not need the alias... ... Go to the command prompt and try to ping the server ... I support the Professional Association of SQL Server and it's community of SQL Server professionals. ... > I have already created an alias using Client Network Utility - TCPIP. ...
    (microsoft.public.sqlserver.server)
  • Re: Remote Server Not Visible
    ... I tried adding the server through the client network utility with tcp/IP ... and then named pipes, but neither worked. ... > using the client network utility to create an alias to the other server ...
    (microsoft.public.sqlserver.replication)
  • Re: Cannot Connect to SQL Server 2000 using Windows XP Pro account login info
    ... Named pipes are not created, but rather enabled - with both the ... Client and Server Network Utilities. ... For the Client Network Utility, ...
    (microsoft.public.sqlserver.connect)