Accessing named instance remotely

I've got an instance of SQL server running on my website. I have port
1433 open and I can connect to it via enterprise manager across the
internet just by using the domain name in the server name box.
I recently installed SQL 2K5 beta 2 on the same box and gave it a
different name. I should be able to connect to it using
domainname\instancename correct? For some reason I can't connect to
it. I guess I don't know whether this is something particular to 2K5
or not, or do I need to do something specific for any named instance?
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegr oups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>
|||You will have to specify a PORT NUMBER unless you also have UDP PORT 1434
opened on your firewall.
If you also have dynamic defined, which would not be recommended in your
configuration, you may have to open up several inbound ports to cover those
that SQL Server may use.
You would be better off blocking inbound UDP 1434, configuring your named
instance to use a specific port, say 1533, and then also open up inbound TCP
1533.
Out of curiosity, why would you expose a SQL Server installation to the
public network?
Sincerely,
Anthony Thomas

"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23AZc8EZ$EHA.2568@.TK2MSFTNGP10.phx.gbl...
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegr oups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>