Similar Threads:
1.IPC security problem (.NET remoting)
I have a problem for my IpcClient to connect to my IpcServer.
I get "Access denied" message.
It appears that the solution is to write this:
dict["authorizedGroup"] = "Everyone";
This works fine on my computer at work.
The problem is this is not working on my home computer. It is a Windows XP
french edition. The group "Everyone" does not exists.
Isn't it possible to remove security from the Ipc engine so it will allow
access to every group ?
2.Remoting;IPC; instance problem
Hi to all,
my scenario is this, i have an application running and i need to
connect to that instance from another application so i thougth to use
dotnet remoting.
The problem is that when i had to register the class
(RegisterWellKnownServiceType) i realised that the service instance
that i wanted is already running, created by an application that isn't
using remoting.
The question is, how do i solve this problem? My mind is opened to any
possible scenarios. I already spend many time around this issue.
3.problem with using IPC and TCP channels
I have a service which has both an IPC and TCP remoting channel. A client
can use either to access my service and I talk to the clients via a callback
they pass to me. If I try to have the service talk to another instance of
the service running on a different machine, the callback fails and an
exception is thrown "Unable to case object of type
'System.Runtime.Remoting.Identity' to type
'System.Runtime.Remoting.ServerIdentity'. Any ideas on why this doesn't work
across machines?
If I take out the one line of code where I register the IPC channel,
everything works fine.
4.a couple remoting questions (.net 2.0 - ipc)
Hi,
First a bit of background: I'm shooting for a "single instance running", and I've implemented that with a named local mutex. (I only want it limited to a single instance within an e.g. "terminal services session".
This appears to be working fine.
Next I want to have subsequent launch attempts of the program to communicate with the running instance so that it can take care of any command line args etc.
I've implemented the interprocess communication using remoting via the new IPC channels. It too appears to be working fine.
-------------
My first question relates to redundancy?
Is the ChannelServices.RegisterChannel method itself already protected by a mutex? (that is: if multiple program instances simply try to create the named server channel, am I gauranteed that only one will succeed while the rest will be tossed a "Remoting Exception - This channel has already been registered"?
If so, then manually creating a mutex is redundant and unnecessary.
-------------
My second question relates to the name of the IPC channel. In a terminal services environment, are IPC channel names unique to a "machine" or to a "terminal session"? Can you prefix channel names "local\" or "global\" like you can mutex names to enforce the proper semantics? Or is it machine only and I'd have to query some "session token" to include in the channel name to prevent conflicts?
(And if so, can you suggest the 'session token' that should be used and how it is obtained?)
Thanks,
Dave
5.IPC Remoting In a Windows Service
Hi, I have created a Windows Service which uses IPC Remoting to share data
with a VB.Net application. The service process runs in the LocalSystem
Account. When the the client VB app attempts to access data from the shared
class, I get the following error:
"Failed to connect to IPC Port. Access is denied."
Initialy, I developed & debuged the Windows Service code in a VB.Net
Windows application and all worked fine. Is there some security issue I need
to contend with when running as a LocalSystem service?
RML
6. IPC Remoting "pipe is being closed"
7. Windows-service remoting - IPC vs. COM
8. WCF/Remoting on IPC