Posted by John Bell on 01/21/06 12:53

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
>

[Back to original message]