RE: Problems with security requirements in Windows WorkGroups.

Hello Steven, first of all, thank you for your quick answer.

Yes, of course I have a security error as you can read in the error message
I obtain:

"A remote side security requirement was not fulfilled during authentication.
Try increase the ProtectionLevel and/or ImpersonationLevel".

(No Inner Exception is thrown)

I can give you some code generated for the error purpose. It consists in a
small chat application between a client (ChatClient) and a server
(ChatServer). By the way, how should I send you the code? I can not find a
way in my web news interface... :(

I am executing the example in two machines with Windows XP, the same users
and passwords in both machines and belonging to a WorkGroup.

When I try to use the TCP channel I get the error (with NO inner exception
messages) I have written above.

Thanks again and regards,

Domingo.
--
Domingo López.
Software Engineer & Project Manager.
Visual Tools.



""Steven Cheng"" wrote:

Hi Domingo,

From your description, I got that you're encountering some security error
when using .net remoting to communicate between client , server
application, correct?

Based on my experience, this general error message could be caused by many
things such as user identity not supplied, or the client and server
channel's security setting not match.....

As for the error, what's the innerException, generally the inner exception
may provide some further information. Also, for non-domain machines that
need to communicate under windows authentication, you need to use a
duplicated account(with same username/password) on both sides. If
convenient, you can try creating a simplified client/server project
pair(with a very simple remoting class) to demonstrate the problem. And you
can send me the package so that I can also perform some tests on my side.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
From: =?Utf-8?B?d29taW4=?= <vt_supervisor@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Problems with security requirements in Windows WorkGroups.
Date: Wed, 5 Mar 2008 07:21:03 -0800

Hello everybody,

I have a .NET C# client-server application that is being used in two
machines with Windows XP installed. Both the client and the server are
executed into users of a Work Group.

I am using .NET Remoting to connect the client and the server with a TCP
channel. The registration of the channel is made by using the following
code:

"ChannelServices.RegisterChannel(channel, true);"

Where "channel" is a TCP channel. The ensureSecurity option is set to
"true"
in order to ensure the channel encryption.

Both the client and sever must send objects to each other (usually using a
proxy).

The problem is, although this environment works well in most of the cases,
I
have an example where I obtain the following error text when the server
tries
to access the client proxy (the error is displayed in the client):

"A remote side security requirement was not fulfilled during
authentication.
Try increase the ProtectionLevel and/or ImpersonationLevel".

It is important to remark that the (.NET Remoting) proxies have right
permissions when accessing the server from the client.

After that, I have proved making the following change to the TCP channel:

"ChannelServices.RegisterChannel(channel, false);"

That is, setting "false" the ensureSecurity option. So this means (as the
Microsoft documentation says) that the channel will be encrypted only in
case
it is possible. So in this case the error is resolved because although the
server does not have the proper client credentials, the channel will not
be
encrypted.

Finally, my question: I mandatory need to ensure the encryption of the
channel, and I need to know which could be the problem with the
impersonation
and credentials in the wrong example. Is it machine configuration
dependant?
Which is the reason for having two environment apparently identical
(Windows
XP, WorkGroup, same users) but with different behavors?

Could you please give me some help about my problem?

Thanks a lot in advance.

Regards,

Domingo.

--
Domingo López.
Software Engineer & Project Manager.
Visual Tools.




.

Relevant Pages

  • Re: UnauthorizedAccessException when using MSDTC
    ... dispatcher2 is the user logged on the client pc. ... Event Source: Security ... Object Server: SC Manager ... Primary Domain: BLITZ ...
    (microsoft.public.data.ado)
  • Re: Routing and Remote Access - Authentication Failure
    ... because the real client computer can tunel through it's local NAT router, ... travel the Intrenet, join the VPN and access the server, when this feature ... Their security system decided that the server was trying to steel ...
    (microsoft.public.windows.server.networking)
  • Re: WCF security advice (and clarification) needed
    ... You, the client, resolve the foo.mycompany.com hostname within your ... TCP/IP) with that ticket as the security token. ... There are two parties participating in a security scenario, the server ... HTTP supports other authentication ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: VPN -- the next consumer "turnkey"?
    ... I'm not a security expert. ... "A Hamachi system is comprised of backend servers and end-node ... Server nodes track client's locations and provide ... services without providing Hamachi with a list of client IP's. ...
    (alt.internet.wireless)
  • Remoting, events and custom encryption channel sinks
    ... - a server app hosts the remotable device service ... - the client app connects to a remote device service which is hosted by the ... The client app instantiates a tcp channel with a given port number because ...
    (microsoft.public.dotnet.framework.remoting)