In SQL Server 2000 IIRC, the browser (which uses 1434) functionality was
part of the server process. In SQL Server 2005 and above, its a separate
service, which can be turned off if you don't need instance discovery (ie,
you use specific port numbers and either use default port for default
instance or specify port number in the connection string).
SQL Server must use a TCP port for connections, you can configure a port
other than 1433. Not sure exactly what you mean by "disable for untrusted
connections" in this context or the specific "same" vulnerability to which
you refer.
Cheers,
Bob Beauchemin
SQLskills
Post by Peter NolanThank you,
I know what the ports are for my question is does SQL Server 2005 have the
same vunerability as SQL 2000.
Thanks
Peter
Post by Dan GuzmanSQL Server listens on TCP 1433 by default. If you block the port, then you
will need to either assign a different port for SQL Server to listen on
unless you want to disable remote connections entirely. These are not
related specifically to trusted (Windows authenticated) connections.
UDP 1434 is used for named instance enumeration (SQL Browser in SQL 2005)
and is is only needed if you have named instances. You can use the SQL
Server Configuration Manager tool to disable the SQL Browser service and set
the listing ports in SQL 2005 and SQL 2008.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
Post by Peter NolanHello,
I know that in SQL 2000 these ports needed to be disabled for none trusted
connections. Do you need to do the dame for 2005 and 2008?
Thanks
Peter