How to allow netNamedPipeBinding to work with the required UAC?

Question

I have a service running under a local system account. I have an application running in a mode other than UAC. Both interact with each other because they act as both a server and a client.

Application, as the client can exchange data with the Service. But the service as a client cannot communicate with the application.

If I run UAC, the problem is resolved.

<customBinding>
   <binding name="net.pipe">
      <namedPipeTransport  />
    </binding>
</customBinding>

Answer 1

Design Behavior. pah.

Great article cleans up named pipe binding Exploring WCF Name Binding