TCP/IP and security

From: Drizzt (drizzt.du_at_libero.it)
Date: 11/24/03 

Date: Mon, 24 Nov 2003 12:19:53 GMT

I've got an application that ships with MSDE as DBMS instead of the old .mdb
file. Everything work right, only I have problems with security stuff. I've
searched around with Deja, but found no solutions to those two...

1) I need to change the protocols settings during installation or, after
installation, with Visual Basic code. This because the software is
autoinstalled, distributed on a CD, user friendly, and I don't want to ruin
it forcing the user to change the protocols manually.
Specifically, I need to be sure that protocols used by the server are TCP\IP
and Named Pipes, and that port XXXXX is selected as the default port instead
of 1433. Is there a stored procedure to do this? Or can this be done with
DMO?

2) I've installed the SQL Security package on a couple of machine to see
what happens and how it solve the nasty problem with the various worms
attacking port 1433 and 1434. But I was expecting a different solution,
honestly, than disabling the TCP\IP protocol for SQL Server!
After the installation of the patch, we found that
 - whatever port I say to SQL Server to use, it's always closed. netstat -a
do not list it, grc.com says it is closed, accessing the server with EM from
other PC via Internet result in "server doesn't exist".
 - If I remove the TCP protocol from the used ones, obviously SQL Server do
not use it (errorlog after service start lists the protocols used).
 - If I add the TCP protocol to the ones to use, guess what, SQL Server
STILL do not use it!(errorlog after service start lists the protocols used,
as above).
I hope I'm wrong on this...am I wrong, right?

TIA, Mauro.

Relevant Pages

  • Re: ODBC failing to connect
    ... Well looking at the Firewall logs I can see the it is opening the port then ... First off I went into the SQL Server logs and found out that it is ... Back to the ISA machine, and opened up telnet and tried to connect to SQL ... You'd also want to check your ports and protocols - one way ...
    (microsoft.public.sqlserver.connect)
  • Re: Sql Express (Build 2047) XP SP2 not listening
    ... Did you enable remote connections for the protocols? ... I ran the Sql Server Configuration Manager to set the Protocols for ... SqlExpress and the Client Protocols to TCP and port 1433. ... I run netstat -ano and I still cannot see the service listening on port ...
    (microsoft.public.sqlserver.connect)
  • RE: Problems connecting to MSDE server
    ... Thank you for your post regarding unable to connect to SQL Server. ... didn't specify to enable protocols when installing, ... run svrnetcn.exe which will bring up the Server Network configuration ... The client tools ship with a full copy of SQL Server, ...
    (microsoft.public.sqlserver.msde)
  • Re: error on conn.open()
    ... ugg helps when i have the; in the connection string... ... and i did not find the "Protocols for MSSQLSERVER" then enable the ... SQL Server 2005 Open SQL Server Configuration Manager. ... 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: TCP/IP and security
    ... Jasper Smith (SQL Server MVP) ... I need to change the protocols settings during installation or, ... is selected as the default port instead ...
    (microsoft.public.sqlserver.security)