netnamedpipebinding

I am running a windows service to which I send messages over a NetNamedPipeBinding. The messages are send from a client application which is triggered by a GPO. I just installed the service and client on a new server and I'm getting the following message: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/VOXAServices/VOXADefaultPipe that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. There is no inner exception. If I run the client application by double

Intro: I successfully implemented a WCF Service hosted in a Windows Service a few days ago. The community here at StackOverflow helped me with the WSDL exposure here . I thank you once again. However recently I found out that there is another potential client for this service this time located on the same machine as the service and this lead me to think I should add another endpoint with the namedPipesBinding. Named pipes seem to be the best solution for intra-machine communication as far as I am concerned. Please correct me if this is wrong. Problem: I need to expose another endpoint for the

Given : - the application - desktop GUI (WPF) .NET app - windows service watching for application (.NET also) The windows service periodically "pings" application to get sure it's healthy (and if it's not winservice will restart it). I was going to implement "pinging" via named pipes. To make things simpler I decided to do it with WCF. The application hosts a WCF-service (one operation Ping returning something). The windows service is a client for this WCF-service, invokes it periodically based on a timer. That's all in Windows 7. Windows service is running under LocalService (in session#0).