Linked Server setup - SQL 2005 RTM

<<cross posted from microsoft.public.sqlserver.server>>

Environment: Windows 2003 Standard Edition SP1, SQL 2005 EE RTM (both
servers)


I am getting the following messages when I run this query:


select * from LINKEDSERVER.databasename.dbo.tablename


OLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returned
message "An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow
remote connections.".
Msg 782, Level 16, State 1, Line 0
SQL Network Interfaces: No credentials are available in the security
package
OLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returned
message "Client unable to establish connection".
Msg 782, Level 16, State 1, Line 0
SQL Network Interfaces: No credentials are available in the security
package


LINKEDSERVER is set up as a SQL Server linked server., with no login
mapping, and connections will be made using the login's current
security context.


Both servers allow local and remote connections via TCP/IP, and Named
Pipes is disabled on both servers.  Both servers are trusted for
delegation, and the service accounts for the MSSQLSERVER service on
both servers are also trusted for delegation.


We are auditing successful and failed logins, and are not seeing any
activity on the linked server.


Any help would be appreciated.
Randy

Hi

Have you checked the properties/server options on the linked server to make
sure RPC is enabled?
Also have you looked at the service area configuration tool to see if remote
connections are available on a protocol you are using?

John

"RandyMartin" <randy.martin@ds-iq.com> wrote in message
news:1137777482.665471.8410@g44g2000cwa.googlegroups.com...
> <<cross posted from microsoft.public.sqlserver.server>>
>
> Environment: Windows 2003 Standard Edition SP1, SQL 2005 EE RTM (both
> servers)
>
>
> I am getting the following messages when I run this query:
>
>
> select * from LINKEDSERVER.databasename.dbo.tablename
>
>
> OLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returned
> message "An error has occurred while establishing a connection to the
> server. When connecting to SQL Server 2005, this failure may be caused
> by the fact that under the default settings SQL Server does not allow
> remote connections.".
> Msg 782, Level 16, State 1, Line 0
> SQL Network Interfaces: No credentials are available in the security
> package
> OLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returned
> message "Client unable to establish connection".
> Msg 782, Level 16, State 1, Line 0
> SQL Network Interfaces: No credentials are available in the security
> package
>
>
> LINKEDSERVER is set up as a SQL Server linked server., with no login
> mapping, and connections will be made using the login's current
> security context.
>
>
> Both servers allow local and remote connections via TCP/IP, and Named
> Pipes is disabled on both servers.  Both servers are trusted for
> delegation, and the service accounts for the MSSQLSERVER service on
> both servers are also trusted for delegation.
>
>
> We are auditing successful and failed logins, and are not seeing any
> activity on the linked server.
>
>
> Any help would be appreciated.
> Randy
>

Hi John,

The linked server is set up for RPC=True and RPC Out=True.  The Surface
Area Configuration show both Local and Remote Connections allowed over
TCP/IP.  Both servers are set to accept only Shared Memory and TCP/IP
traffic, and the clients on both servers have only Shared Memory and
TCP/IP enabled.

One item I am chasing is the SPN.  In doing some digging, it seems the
SPN has to be fully qualified out to the port.  I need to make sure
that ours are, for both servers.  A symptom I am seeing is that a
non-linked server connection shows up as NTLM, not Kerberos as
expected.  This link had the details on how to discover that:
http://blogs.msdn.com/sql_protocols...12/479871.aspx.

I'll keep you posted...

More info, the NTLM auth scheme I was seeing was when I was connecting
via Mgmt Studio on the local server and going for the local instance.
Mgmt Studio chooses Shared Memory, not TCP/IP, as the protocol, and
gets NTLM auth scheme as a result.  If I connect to a remote machine
via Mgmt Studio, I get KERBEROS as expected.

I tried doing the connect to the remote server (KERBEROS) and doing a
4-part SELECT on that connection to the linked server.  Same (sad)
result...