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 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 MSDE2000RelA

I was able to install MSDE into WXP and migrated my Access
databases through Windows Integrated Authentication Method.
But whenever I tried connecting to MSDE by SQL login it
gives me the following error:
Invalid username and/or password, you are using a windows
login that is not your own, or server does not exist.
Please help.
Tnx,
Jess
hi Jess,
jess.tayag@.dhl.com wrote:
> I was able to install MSDE into WXP and migrated my Access
> databases through Windows Integrated Authentication Method.
> But whenever I tried connecting to MSDE by SQL login it
> gives me the following error:
> Invalid username and/or password, you are using a windows
> login that is not your own, or server does not exist.
>
if the raised error is
"Login failed for user 'UserName'. Reason: Not associated with a trusted SQL
Server connection."
the reason is MSDE is only allowing WindowsNT trusted connections and not
SQL Server authenticated connections, and this can be solved as explained in
http://support.microsoft.com/default...b;en-us;285097 in the part
regarding the Windows registry modification, while the
"SQL Server does not exists or access denied"
message is usually related to other kind of troubles, as indicated in
http://support.microsoft.com/default...06&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply