RE: SQL Server Registration Ports...

Hello,

To work effectively with a firewall, you must ensure that the instance of
SQL Server always listens on the network address that the firewall is
configured to forward. The TCP/IP network addresses for SQL Server are
comprised of two parts: an IP address associated with one or more network
cards in a computer, and a TCP port address specific to an instance of SQL
Server. Default instances of SQL Server use TCP port 1433 by default. Named
instances, however, dynamically assign an unused TCP port number the first
time the instance is started. The named instance can also dynamically
change it's TCP port address on a subsequent startup if the original TCP
port number is being used by another application. SQL Server only
dynamically changes to an unused TCP port if the port it is currently
listening on was dynamically selected. That is, if the port was statically
selected (manually), SQL Server will display an error and continue to
listen on other ports. It is unlikely another application would attempt to
use 1433 since that port is registered as a well-known address for SQL
Server.

For information on using a firewall with SQL Server, refer to the following
documentation:
http://www.microsoft.com/sql/techinfo/administration/2000/securityWP.asp

SQL Server Books Online: Using a Firewall System with SQL Server

You can refer to the following article:

287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932


More information for reference:

Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/kb/328306/

885345 You may not be able to enumerate all the instances of SQL Server
2000 on
http://support.microsoft.com/?id=885345

I hope the information is helpful.


Sophie Guo
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



.

Relevant Pages

  • Re: Exposing data
    ... One port on the firewall is open for HTTP (80, ... The web server, BEHIND THE FIREWALL, can talk to the database server. ... No SQL Server ports ... and SQL Server (network environment only). ...
    (microsoft.public.sqlserver.security)
  • Re: Problems after SP2 Patch, With Pervasive SQL Server
    ... You need to find out what TCP port your SQL Server is listening on, and then make sure that port is open in the Windows firewall. ... > patch was installed, pervasive tested tcip ok,but won't allow access to ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Allow a customer access my sql server over the internet
    ... You can accomplish this by opening tcp port 1433 on your firewall (or ... > I am trying to allow a customer access a certain view in my SQL Server ... > I am using SQL Server 2000 with Windows authentication. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL_Server_does_not_exist_or_access_denied
    ... The connection may have got lost because the client machine opens ... a new TCP port with every access to the SQL Server without ...
    (microsoft.public.sqlserver.odbc)
  • Re: SQL_Server_does_not_exist_or_access_denied
    ... The connection may have got lost because the client machine opens ... a new TCP port with every access to the SQL Server without ...
    (microsoft.public.sqlserver.connect)