Connecting to named instance in Management Studio fails

I have a remote server with a default instance of Sql 2000 and a named
instance of Sql 2005. Whenever I try to connect to the named instance
in Management Studio, it ALWAYS connects to the default instance. I am
specifying the connection as ServerName\InstanceName. It seems like it
is ignoring the instance name in the connection request. I have tried
creating an alias, but it does not change the behavior. One special
note - due to our network structure we must use fully qualified domain
names when connecting to remote servers. The my local server and my
remote server are in different sub-domains:
local server = ServerA.HQ.domain.com
remote server = ServerX.Remote.domain.com
One interesting observation is that I am able to connect to the remote
server from a different db server in the same sub-domain without any
problems. i.e. ServerY.remote.domain.com can connect to
ServerX.remote.domain.com.
I know there was a bug in MDAC that was similar to this, but it was
supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
the SQLNI code?check with your network admin. it seems there is firewall rule on udp 1434.
also, try to specify the tcp as part of your connection string.
e.g.
sqlcmd -S"ServerX.Remote.domain.com,tcp#"
-oj
"kmart" <kevmart@.gmail.com> wrote in message
news:1146849746.958318.194980@.v46g2000cwv.googlegroups.com...
>I have a remote server with a default instance of Sql 2000 and a named
> instance of Sql 2005. Whenever I try to connect to the named instance
> in Management Studio, it ALWAYS connects to the default instance. I am
> specifying the connection as ServerName\InstanceName. It seems like it
> is ignoring the instance name in the connection request. I have tried
> creating an alias, but it does not change the behavior. One special
> note - due to our network structure we must use fully qualified domain
> names when connecting to remote servers. The my local server and my
> remote server are in different sub-domains:
> local server = ServerA.HQ.domain.com
> remote server = ServerX.Remote.domain.com
> One interesting observation is that I am able to connect to the remote
> server from a different db server in the same sub-domain without any
> problems. i.e. ServerY.remote.domain.com can connect to
> ServerX.remote.domain.com.
> I know there was a bug in MDAC that was similar to this, but it was
> supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
> the SQLNI code?
>

Connecting to an instance of SQL

I have a SQL2000 instance that when I attempt to connect to it by
default\NamedInstance it connects me to the default instance on that server
instead. If I connect with (local)\NamedInstance it connects me to the named
instance.
In addition when I attempt to start the agent for the named instance I get
the below:
SQLServerAgent cannot start because the instance of the server (MSSQLSERVER)
is not the expected instance
thanks for your your helpI'd start by checking for aliases in Client Network Utility.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RomM" <RomM@.discussions.microsoft.com> wrote in message
news:6743587B-BC99-498B-8E1D-519B98C7380C@.microsoft.com...
>I have a SQL2000 instance that when I attempt to connect to it by
> default\NamedInstance it connects me to the default instance on that server
> instead. If I connect with (local)\NamedInstance it connects me to the named
> instance.
> In addition when I attempt to start the agent for the named instance I get
> the below:
> SQLServerAgent cannot start because the instance of the server (MSSQLSERVER)
> is not the expected instance
> thanks for your your help|||It was the correct alias but the port was wrong. I changed and it seems to
be working fine.
What do you think the cause was?
thanks for your help.
"Tibor Karaszi" wrote:
> I'd start by checking for aliases in Client Network Utility.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "RomM" <RomM@.discussions.microsoft.com> wrote in message
> news:6743587B-BC99-498B-8E1D-519B98C7380C@.microsoft.com...
> >I have a SQL2000 instance that when I attempt to connect to it by
> > default\NamedInstance it connects me to the default instance on that server
> > instead. If I connect with (local)\NamedInstance it connects me to the named
> > instance.
> >
> > In addition when I attempt to start the agent for the named instance I get
> > the below:
> > SQLServerAgent cannot start because the instance of the server (MSSQLSERVER)
> > is not the expected instance
> >
> > thanks for your your help
>
>

Connecting to an instance of SQL

I have a SQL2000 instance that when I attempt to connect to it by
default\NamedInstance it connects me to the default instance on that server
instead. If I connect with (local)\NamedInstance it connects me to the name
d
instance.
In addition when I attempt to start the agent for the named instance I get
the below:
SQLServerAgent cannot start because the instance of the server (MSSQLSERVER)
is not the expected instance
thanks for your your helpI'd start by checking for aliases in Client Network Utility.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RomM" <RomM@.discussions.microsoft.com> wrote in message
news:6743587B-BC99-498B-8E1D-519B98C7380C@.microsoft.com...
>I have a SQL2000 instance that when I attempt to connect to it by
> default\NamedInstance it connects me to the default instance on that serve
r
> instead. If I connect with (local)\NamedInstance it connects me to the na
med
> instance.
> In addition when I attempt to start the agent for the named instance I get
> the below:
> SQLServerAgent cannot start because the instance of the server (MSSQLSERVE
R)
> is not the expected instance
> thanks for your your help|||It was the correct alias but the port was wrong. I changed and it seems to
be working fine.
What do you think the cause was?
thanks for your help.
"Tibor Karaszi" wrote:

> I'd start by checking for aliases in Client Network Utility.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "RomM" <RomM@.discussions.microsoft.com> wrote in message
> news:6743587B-BC99-498B-8E1D-519B98C7380C@.microsoft.com...
>
>