<AFoxmore@yahoo.com> wrote:

>Hi Everyone,
>
>I was doing some testing with client configuration and I'm seeing
>something I don't understand. Let me explain the setup.
>
>My setup involves a single machine running "SQL Server Express 2005".
>As you probably know, SSE includes the "SQL Server Native Client". I
>run the "SQL Server Configuration Manager" and under the "SQL Native
>Client Configuration" | "Client Protocols" node, I disable TCP/IP. My
>understanding is that this should prevent clients on this machine from
>using TCP/IP to connect to any SQL Server instance. Does this sound
>right so far?
>
>Well, when I run SQLCMD (specifying "tcp:" as the protocol) I am still
>able to connect to the instance on the local machine.
>
>In other words, I have TCP/IP disabled as a client protocol, yet I am
>still able to successfully connect to an instance using SQLCMD with a
>command line like this:
>
>SQLCMD -S tcp:.\TEST_01 -d AdventureWorks
>
>Now, it's my understanding that SQLCMD relies upon the "SQL Server
>Native Client". And since I've (supposedly) configured the "SQL Server
>Native Client" *NOT* to allow TCP/IP connections, the above SQLCMD
>connection should not work, yet it does.
>
>What am I missing here?