Can't created a linked server on a named instance to default insta

I have been trying to create a linked server on a named instance to a defaul
t
instance using intergrated security. It seems to work fine from a default
instance to any other SQL instance, including a named instance, but any time
I create the linked server on the named instance a call to the linked server
fails with the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
All servers are running SQL Server 2000 and the only difference in the
installation besides the fact one is named, is that the named instance is SP
4
and all others are SP3.
From a default instance the following works fine:
sp_addlinkedserver 'ORDEV01'
ORDEV01.Master.dbo.sp_helpdb
and the following to a named instance works as well:
sp_addlinkedserver 'LOU\Master'
[LOU\Master].Master.dbo.sp_helpdb
But if I try to created a linked server on the name dinstance LOU\Master I
get the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Thanks in advance for any help.Byron
Does the instance have Windows Authentication?
"Byron" <Byron@.discussions.microsoft.com> wrote in message
news:CB90A676-83FF-41CC-9C04-221920F998FF@.microsoft.com...
>I have been trying to create a linked server on a named instance to a
>default
> instance using intergrated security. It seems to work fine from a default
> instance to any other SQL instance, including a named instance, but any
> time
> I create the linked server on the named instance a call to the linked
> server
> fails with the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> All servers are running SQL Server 2000 and the only difference in the
> installation besides the fact one is named, is that the named instance is
> SP4
> and all others are SP3.
> From a default instance the following works fine:
> sp_addlinkedserver 'ORDEV01'
> ORDEV01.Master.dbo.sp_helpdb
> and the following to a named instance works as well:
> sp_addlinkedserver 'LOU\Master'
> [LOU\Master].Master.dbo.sp_helpdb
> But if I try to created a linked server on the name dinstance LOU\Master I
> get the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> Thanks in advance for any help.

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use jus
t
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:

> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!