ODBC call failed when trying to open a SQL Server view linked to Access

Access 2007 database, lots of linked SQL tables and views, all with connection strings that look like:

ODBC;DRIVER=SQL Server Native Client 11.0;SERVER=XXXXXX;Trusted_Connection=Yes;APP=SSMA;DATABASE=XXX_System_Tables;

Every one of these linked tables and views run properly except one, which generates an error:

ODBC--call failed
[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.(#18456)

The only difference I can find between this view and others is that this view includes a reference to a table in a linked server, so I can only assume that there is something about the permissions established for querying the linked server.  When I open Access on the server and create a pass-thru query using the SQL from the view, it runs fine.  But when I open Access from my desktop, connect to the server via a VPN with the same login credentials I get the error mentioned above.
LVL 50
Dale FyeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

John TsioumprisSoftware & Systems EngineerCommented:
i think you need to read this
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Dale,

 Sounds like one of the servers is running under the network service account.

 Make sure all the SQL Services are running under Domain Level accounts.

Jim.
0
Dale FyeAuthor Commented:
Have not had a chance to return to this question lately.  Am working on another similar issue that looks like it has to do with the first SQL Server not being able to pass the Windows authentication information to the 2nd server.  Will hopefully get this resolved, or ask more questions shortly.

Dale
0
Dale FyeAuthor Commented:
Thanks for your help guys.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.