Can't remotely access SQL 2005 named instance

SuHi,
I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
server. I installed a default instance, and then a named instance called
"DEV".
Initially, I could not access either instance from a remote machine. I went
into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
under the Remote Access portion of the dialog for BOTH instances.
I can access the default instance from a remote machine. I still cannot
access the named instance from a remote machine. I have triple checked all
my settings. They are exactly the same for both instances.
The error message I receive is:
26 - Error locating server/instance specified
I can't see the DEV instance in the SQL Server browse list either.
Can anyone help?
Is the SQL Server Browser service started on the server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked all
> my settings. They are exactly the same for both instances.
> The error message I receive is:
> 26 - Error locating server/instance specified
> I can't see the DEV instance in the SQL Server browse list either.
> Can anyone help?
|||Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice

I read a blurb somewhere that enabling the Browser service opens security
holes in SQL Server. Is this true, and if it is how does it indeed open
security holes?
- Anthony
"Tibor Karaszi" wrote:

> Is the SQL Server Browser service started on the server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
>
|||You're welcome Anthony. :-)

> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
Every surface you open opens increases the threat area. I don't know of any particular issues with
the SQL Browser. The same functionality existed in 2000, but it was built-in to the database engine.
To be more specific I guess we would have to see that comment.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:B18F79B4-C704-4903-A98C-FC3D5F25323D@.microsoft.com...[vbcol=seagreen]
> Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
> you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice
>
> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
> - Anthony
> "Tibor Karaszi" wrote:
|||"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I
> went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named
> Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked
> all
> my settings. They are exactly the same for both instances.
Have you tried the SQL Server Configuration Manager on the W2K machine.
This iw wher you open up the IP/Named pipes.