title: Why does named pipe WCF service reject Windows service clients?
body: <p>On Windows 7 and .NET 4 I'm getting some very weird effects from the WCF named pipe transport when my WCF client is a Windows service.</p>
  
  <p>My WCF service is hosted in a user mode app and exposed over the named pipe binding.</p>
  
  <p>My WCF client is a Windows service, running as Network Service (I get the same result if it runs as Local System).</p>
  
  <p>If my user mode app (ie WCF service) is running as a domain admin then it works fine, but if the user mode app is an ordinary user (or local admin) then the connection is rejected with a CommunicationObjectFaultedException.</p>
  
  <p>I saw some questions on here relating to UAC being involved, but I haven't seen an actual solution anywhere which just makes the named pipe transport work properly.  Is this just an inescapable framework bug?</p>