Re: SQL Server 2008 remote connection problem

The default (un-named) instance should install with the fixed port 1433. There are unusual ways that it can choose dynamic ports. If port 1433 is taken by something else at the time of install. For instance an existing named instance that already has port 1433. Or if the new install is SQL Server Express and you are installing it with the name MSSQLSERVER which makes it the default instance, but Express still does dynamic ports (I think). These are all rare situations though.
Perhaps this is an artifact of a previous installation.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Glenn" <Glenn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:45E6AA10-CBD3-41AA-B9BD-9B4674CA255D@xxxxxxxxxxxxxxxx
It was the default instance, which is why I quoted that line from the docs.

"Sylvain Lafontaine" wrote:

Is this the default instance or a named instance?

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"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: SQL 200 Dev edition on workgroup will not connect
    ... I have been using sql server for about 8 years but mainly working with sql 2000. ... know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform. ... I suggest you to check for the dynamic port number that your SQL Server graps. ... Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. ...
    (microsoft.public.sqlserver.connect)
  • Is FreeBSD ready for desktop (Mozilla Flash)
    ... monitor,, somehow the install fails to detect ... "Macromedia Flash plugin is not available for FreeBSD. ... I quote again "Install the www/linuxpluginwrapper port. ... servers, ...
    (comp.unix.bsd.freebsd.misc)
  • New software uploaded by Denise on Oct 23 07:10:00 -4 2006
    ... and starting compiling the 'bar' port. ... and now where should you install your terminators? ... filter option may run a filter on the wrong type of file and cause ... FreeBSD does not currently support IBM's microchannel bus. ...
    (Linux-Kernel)
  • Re: KMDF Fakemodem not working
    ... I'm using the `Windows Vista and Windows Server Longhorn x86 Checked Build ... install the fakemodem with devcon: ... INf in the sample should tell you how to use devcon to install the driver. ... Why do I need to choose a COM port? ...
    (microsoft.public.development.device.drivers)
  • Re: Bind failed on TCP port 1433
    ... It does sound like something is checking or blocking the port. ... Can we assume that once started SQL Server works OK? ... > fresh operating system install and is running SQL Server along with a ...
    (microsoft.public.sqlserver.setup)
Loading