How do I configure security to get rid of a .NET Remoting AuthenticationException

Question

0.00/5 (No votes)

See more:

I have installed a client application that uses remoting on a new PC (running Windows XP SP2). When the server tries to connect to it to perform remoting I get an AuthenticationException:

System.Security.Authentication.AuthenticationException was unhandled.
A remote side security requirement was not fulfilled during authentication. Try increasing the ProtectionLevel and/or
ImpersonationLevel.

It worked okay on the old PC - so it must be a security configuration issue.

I have Googled for a solution (with no useful results).

Any ideas please as to where the configuration might be - or any other ideas.

(Note: The PCs are in the same WORKGROUP domain.)

Thanks.
Paul

Posted 28-Jan-10 5:13am

Wags

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wags · Answer 1 · 2010-01-29T00:37:00

Solution 2

The solution was to turn off the Simple File Sharing (in Explorer under Tools | Folder Options - View tab, last item, "Use simple file sharing (recommended" ;P ).

Posted 29-Jan-10 0:37am

Wags

Comments

pinx 14-Sep-10 5:55am

We have been struggling with this problem and Googling for a solution, and this simple setting was the thing that solved it.
THANKS!

askoan · Answer 2 · 2010-01-28T08:09:00

I had once a similar exception using remoting between 2 PCs (though they were not on the same domain I think).
As I remember, I solved it unactivating the security option when initializing the TCP Channel (can't remember if it's needed both on client and server side).
I just looked over MSDN, and this TCP Channel property seems to be "IsSecured".

Hope it helps.