Remote connection to SQL Server 2005

I am unable to connect to a SQL Server 2005 instance running remotely
on a Windows 2003 Server machine behind a router. I can connect to the
instance via SQL Server Management Studio Express when I place the
server machine in the DMZ, but I cannot connect when I forward traffic
on port 1433. Note that I am able to forward Remote Desktop requests to
my server, so I know that port forwarding works in other cases.
Any suggestions? I'd rather not leave my server machine in the DMZ.
Thanks for the help.Only the default (un-named) instance listens on port 1433. If you have a
named instance or are running SQL Express, which is a named instance named
(SQLEXPRESS) you are listening on dynamic ports.
For more ideas, run through my short connectivity tutorial at
http://msdn2.microsoft.com/en-us/library/ms345318(SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
<bostonguy@.gmail.com> wrote in message
news:1147702273.174968.231850@.i40g2000cwc.googlegroups.com...
>I am unable to connect to a SQL Server 2005 instance running remotely
> on a Windows 2003 Server machine behind a router. I can connect to the
> instance via SQL Server Management Studio Express when I place the
> server machine in the DMZ, but I cannot connect when I forward traffic
> on port 1433. Note that I am able to forward Remote Desktop requests to
> my server, so I know that port forwarding works in other cases.
> Any suggestions? I'd rather not leave my server machine in the DMZ.
> Thanks for the help.
>|||Is it recommended to use something other than port 1433 when
configuring a static port for a named instance like (SQLEXPRESS)?
Thanks,
John
Rick Byham [MS] wrote:[vbcol=seagreen]
> Only the default (un-named) instance listens on port 1433. If you have a
> named instance or are running SQL Express, which is a named instance named
> (SQLEXPRESS) you are listening on dynamic ports.
> For more ideas, run through my short connectivity tutorial at
> http://msdn2.microsoft.com/en-us/library/ms345318(SQL.90).aspx
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Documentation Manager,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> <bostonguy@.gmail.com> wrote in message
> news:1147702273.174968.231850@.i40g2000cwc.googlegroups.com...|||There is no particular reason to use a different port number. Some people
use different numbers in case there is another SQL Server installed on the
system. Some people like to make it harder for viruses or hackers that are
targeting port 1433, but using a different port doesn't confuse them that
much.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"John" <john@.destinytours.com> wrote in message
news:1147905901.881404.59600@.j55g2000cwa.googlegroups.com...
> Is it recommended to use something other than port 1433 when
> configuring a static port for a named instance like (SQLEXPRESS)?
> Thanks,
> John
> Rick Byham [MS] wrote:
>|||Yes, I experienced this first hand when I discovered someone from
Amsterdam trying to hack into my server with repeated login attemps
(trying every few seconds).
Rick Byham [MS] wrote:[vbcol=seagreen]
> There is no particular reason to use a different port number. Some people
> use different numbers in case there is another SQL Server installed on the
> system. Some people like to make it harder for viruses or hackers that are
> targeting port 1433, but using a different port doesn't confuse them that
> much.
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Documentation Manager,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "John" <john@.destinytours.com> wrote in message
> news:1147905901.881404.59600@.j55g2000cwa.googlegroups.com...