Re: SQL Server 2008 remote connection problem

It might be right. I stopped using (and recommending the use of) the default instance 8 years ago. Sorry for the confusion... but again, I'm not certain that even the default instance listens on 443 anymore but I don't have a default instance rig here to test against. I can't comment on the docs at this point--I stopped writing them in 1996 or so. ;)

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________



"Glenn" <Glenn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:95C72A87-8260-4C07-B6D6-491D03D4359E@xxxxxxxxxxxxxxxx
That directly contradicts the documentation, which states "If enabled, the
default instance of the SQL Server Database Engine listens on TCP port 1433",
as well as this article on how to set up ports:
http://msdn.microsoft.com/en-us/library/cc646023.aspx

So how is anyone supposed to figure this out? Stuff like this bugs the hell
out of me.


"William Vaughn (MVP)" wrote:

Yup, by design. Since SQL Server 2000, you can install multiple instances of
the engine. Each has to listen on its own ports and that port mapping and
exposure are handled differently in each version since. In SQL Server 2005
and 2008 the SQL Browser plays a new role that exposes the server to the
network and translates the ports in use to facilitate the connection.
However, since the ports are assigned dynamically (unless disabled), you
can't tell the firewall to pass through IO on a specific port. What you
ended up doing, is fairly typical. Consider that most sites don't expose SQL
Server outside of the domain and intra-domain firewalls are sometimes
unnecessary.

hth

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________



"Glenn" <Glenn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1B595984-3AC4-42A2-88A9-07004341A576@xxxxxxxxxxxxxxxx
> I was trying to establish a remote connection to SQL Server 2008 from
> another
> machine on my network. The server is running the XP firewall. I thought > I
> had
> everything set up correctly on the server (TCP/IP enabled, remote
> connections
> enabled, TCP port 1433 enabled on the firewall). The remote connection
> repeatedly failed. Based on some information I found on another forum, > I
> set
> up an exception in the firewall for the SQL Server program > (sqlserver.exe)
> and then the remote connection worked. I also got some advice to check
> the
> settings on the TCP/IP Properties dialog in the SQL Server > Configuration
> Manager. Here is a screen shot of that dialog with the original > settings:
> http://www.galcott.com/tcp.jpg. This does not show port 1433 at all. By
> removing the dynamic port settings and putting 1433 in manually I was > able
> to
> get it to work. But why was it set up like this on installation? 1433 > has
> always been the default port in previous versions but it doesn't appear
> that
> 2008 sets it up that way. It seems that something has changed in this
> version
> to make it more difficult to set up but I wonder if I am missing
> something.
>
>
.

Relevant Pages

  • Re: Connecting to an instance in a cluster
    ... "Geoff N. Hiten" wrote: ... you cannot reuse port numbers. ... Microsoft SQL Server MVP ... That is the port you have to open on the firewall. ...
    (microsoft.public.sqlserver.clustering)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... Queries to the Data Engine must go to the port that SQL Server is ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL server connection problem
    ... no firewall is installed? ... Also i have check that port 1433 is not ... Will SQL server only connect to this ... > to configure the firewall to permit connections to SQL Server. ...
    (comp.databases.ms-sqlserver)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)