SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My administration page and webpart make calls to a service via .Net remoting.

I've added AD credential checking to the service and discovered that the calls being made from both the admin page and the web part are coming thru as "NT AUTHORITY\ANONYMOUS LOGON" instead of the logged-on user.

As a test, I've written a WinForms application that makes the same calls and the service is correctly figuring out the credentials. there some special code that I can add to my SharePoint code to get the correct username attached to the thread making the calls?

share|improve this question
up vote 2 down vote accepted

I assume the service is running on a seperate server? It sounds like uou are running into the classic "double hop" issue with authentication.

Here is one (of many) blog posts that describes the double-hop authentication issue.

Double-hop authentication: Why NTLM fails and Kerberos works

You have 3 choices:

  • Configure Kerberos (doable)
  • Configure Claims and re-instrument your .NET remoting service to support claims (complicated)
  • Use the Secure Store Service and configure single sign-on
share|improve this answer
Thanks Chris, I had COMPLETELY forgotten about the double-hop problem. I ran the service on the SharePoint server and the problem went away. – Iunknown Apr 14 '11 at 1:16

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.