Re: Remote connection to SQL Server 2005
- From: "Rick Byham [MS]" <rickbyh@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 May 2006 09:01:44 -0700
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@xxxxxxxxx> wrote in message
news:1147702273.174968.231850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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.
.
- Follow-Ups:
- Re: Remote connection to SQL Server 2005
- From: John
- Re: Remote connection to SQL Server 2005
- References:
- Remote connection to SQL Server 2005
- From: bostonguy
- Remote connection to SQL Server 2005
- Prev by Date: Remote connection to SQL Server 2005
- Next by Date: Re: Connecting to SQL Express from C# via connection string
- Previous by thread: Remote connection to SQL Server 2005
- Next by thread: Re: Remote connection to SQL Server 2005
- Index(es):
Relevant Pages
|
Loading