Prev: VDI backup slows down
Next: SSRS sevice start with error after clean 2008 install?
From: nzrdb6 on 2 Dec 2009 12:59
Please help, my head hurts now!

I have 2 SQL Server 2005 instances on separate physical servers.

Instance A and instance B

I am trying to create a linked server on A to point at B.

I get Error 18456 - login failed for user 'Domain\Login'.

there is no double-hop issue because I am creating the linked server
on server A via terminal services, not via another client.

On server A I can connect to instance B via sqlcmd, using Domain
\Login.

I can also connect to instance B via SSMS as Domain\Login.

Please help!
From: Russell Fields on 2 Dec 2009 13:44
There is more information available to you in the State of the 18456 error
as found in the SQL Server Errorlog. Here is the classic discussion of
this topic:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

In the discussion of the blog post several states not discussed in the
article are also considered.

Also, Laurentiu Cristofor's guidance on further troubleshooting login
failures:
http://blogs.msdn.com/lcris/archive/2008/02/21/sql-server-2005-how-to-debug-login-failures-18456-anyone.aspx

RLF

"nzrdb6" <nzrdb6(a)googlemail.com> wrote in message
news:b13e8c88-e43e-4090-9ec9-765891c1874a(a)v25g2000yqk.googlegroups.com...
> Please help, my head hurts now!
>
> I have 2 SQL Server 2005 instances on separate physical servers.
>
> Instance A and instance B
>
> I am trying to create a linked server on A to point at B.
>
> I get Error 18456 - login failed for user 'Domain\Login'.
>
> there is no double-hop issue because I am creating the linked server
> on server A via terminal services, not via another client.
>
> On server A I can connect to instance B via sqlcmd, using Domain
> \Login.
>
> I can also connect to instance B via SSMS as Domain\Login.
>
> Please help!

 | 
Pages: 1
Prev: VDI backup slows down
Next: SSRS sevice start with error after clean 2008 install?