Re: ?? Turning Off TCP/IP Client Has No Effect ??



Alan Foxmore (AFoxmore@xxxxxxxxx) writes:
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?

Not really. Client protocols only controls which protocol that client
programs use by default. I gueds you override that when you specify
tcp: on the command line. (I have not verified this.)

If you want to protect the server, you should confgure the server
protocols so that TCP is disabled.


--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.



Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Select command with multiple tables
    ... Oops, the client did handle ... There is also a cost for expanding the ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ... Books Online for SQL Server 2005 at ...
    (comp.databases.ms-sqlserver)
  • Re: Problem connection to SQL Server with ODBC
    ... What protocols are being used by the client and what is the ... Are you using an alias for the connection? ... SQL Server Clients May Change Protocols When They Try ...
    (microsoft.public.sqlserver.connect)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.adonet)