How to allow netNamedPipeBinding to work with requiring UAC?

Question

I have a service running under Local system account. I have an application that run in a non-UAC mode. Both interact with each other as both act as server and client.

Application as client can communicate with Service. But Service as client cannot communicate with application.

If I run with UAC the problem is solved.

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

Answer 1

The behavior is by design. ugh.

An excellent article clears named pipe binding Exploring the WCF Named Pipe Binding