Re: Close 1433 port

From: John Bell (jrm_bell@hotmail.com)
Date: 08/31/02 

From: John Bell <jrm_bell@hotmail.com>
Date: Sat, 31 Aug 2002 18:03:24 +0100

Hi

Check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_runsetup_77g3.asp

for information. If you are using TCP/IP to connect to the database
server then 1433 is the default. Even if you change it from the
default you will need a port.

If you are not using TCP/IP then you can remove it from the available
protocols see:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_3oxf.asp?frame=true

John

On Sat, 31 Aug 2002 08:25:20 -0700, "Laith Hattab"
<laithbiz@yahoo.com> wrote:

>Hi all:
>i am using MS SQL2k server on a Win2k server platform, i
>have been informed that port no 1433 is open and may a
>security thrit to the my system is there a way to close or
>control this port.
>
>thanks alot
>Laith Hattab

Relevant Pages

  • Re: SQL2005: Cannot connect error 11001
    ... user mapped to one database. ... Does the issue has to do with the login account / user ... Server connection. ... if you changed the port ...
    (microsoft.public.sqlserver.connect)
  • DB Fault Tolerance - network connections
    ... a Perl server which talks to a PostgreSQL database on a different phys. ... block the port on the DB server, ... Note that I'm using iptables on the box that is running the Postgresql ...
    (perl.dbi.users)
  • Re: Created on Access 2003, but.......................
    ... But that's not secure under any scenario, as any port scanner ... Well, you still need a userid, password and database name. ... You're assuming the server remains in a secured configuration. ...
    (comp.databases.ms-access)
  • Re: .NET and SQL Server on Separate Machines
    ... of the default Network Configurations includes NamedPipes as well as TCP/IP ... This may also be a role/user access issue on the Win3 server. ... Everything was running correctly when the database ... > The connection string in our web.config file originally looked like this: ...
    (microsoft.public.sqlserver.connect)
  • Re: .NET and SQL Server on Separate Machines
    ... of the default Network Configurations includes NamedPipes as well as TCP/IP ... This may also be a role/user access issue on the Win3 server. ... Everything was running correctly when the database ... > The connection string in our web.config file originally looked like this: ...
    (microsoft.public.dotnet.framework.adonet)