WCF issues with using net.pipe binding remotely

Question

I am having a problem with the WCF application that I wrote.

When the client and server are on the same computer, it works fine, however, when I try to run it with the client and server on two separate computers (as it should be), I get the following except:

System.ServiceModel.EndpointNotFoundException: there was no endpoint listening in net.pipe: //vm101.lab.foo.co.uk/VDNService that could receive the message. This is often caused by the wrong address or SOAP action. See InnerException, if available, for more details.
System.IO.PipeException: pipe endpoint net.pipe: //vm101.lab.foo.co.uk/VDNService not found on your local machine.

What I don't understand is the second line of exception, that it cannot find the endpoint on my local machine. Is the endpoint on another computer, and not on my local machine?

I am using net named pipe ( NetNamedPipeBinding) binding , not HTTP code.

And the WCF code is manually encoded, but not generated (as I understand it, this is the norm, I did not know about it until I wrote the application).

Any help would be appreciated.

Answer 1

"net.pipe" addresses the local transport. You need to use another binding for talking on machines. You probably want to use netTcp.

http://msdn.microsoft.com/en-us/library/ms730879.aspx