netnamedpipebinding

I'm trying to get IIS6 to work reliably with a WCF service I have hosted in a separate Windows Service application on the same machine. Users connect to IIS via some HTTP exposed services, which is working fine, and then IIS needs to get some information from the Windows service to put in the HTTP response. I also need a callback channel between the Windows Service and IIS. After a lot of effort I got it working with a netTcpBinding and everything would be rosey for 5 or 10 minutes but after that IIS would report the WCF channel as being faulted and then clam up and stop processing any

I would like to know if netNamedPipeBinding is considered safe: On one hand NetNamedPipeBinding implements security only on the transport Layer and it uses NTLM ( source ) that is no longer recommended by Microsoft ( source ) On the other hand the Named Pipie is not accessible from a remote computer, and there is no way to eavesdrop on a particular open pipe instance being used to transfer data, or write data to it, unless one can obtain the handle to the specific instance concerned. This is the reason why I don't know what to think about the security of this solution. Chris Dickson You are

I am trying to run multiple WCF Service hosting apps on the same Machine. I want to run multiple Applications - not multiple services in one application. var host = new ServiceHost(typeof(MyClass1), new Uri[] { new Uri("net.pipe://localhost") }); host.AddServiceEndpoint(typeof(ISomeInterface), new NetNamedPipeBinding(), "FOO"); host.Open(); I change "FOO" for every app, but still can not start multiple Services. Guess its pretty simple, but im stuck :( Regards Approaching it like this will do what you want, I believe: string relativeUriPart = GetUniquePartFromConfigOfThisApplicationInstance();

I have a client app that hosts a WCF service using net.pipe protocol. The client can't communicate with other WCF services which are running under the admin user. I have read that you can't communicate using net.pipe between different users. Is there way to by pass it? Chris Dickson I have read that you can't communicate using net.pipe between different users. This isn't true in general. Here is a summary of what I think you are referring to: If you are running on an operating system earlier than Windows Vista there is no problem: any process should be able to host a WCF net.pipe service

I have been trying to get up to speed on Named Pipes this week. The task I am trying to solve with them is that I have an existing windows service that is acting as a device driver that funnels data from an external device into a database. Now I have to modify this service and add an optional user front end (on the same machine, using a form of IPC) that can monitor the data as it passes between the device and the DB as well as send some commands back to the service. My initial ideas for the IPC were either named pipes or memory mapped files. So far I have been working through the named pipe

I noticed that 2147483647 seems to be a popular choice for maxReceivedMessageSize but is this the limit? AgileJon Nope, the limit is Int64.MaxValue 1 which is: 9223372036854775807 MaxMessageReceivedSize in basicHttpBinding appears to be an int32 - setting it over the max value of an int32 results in: This factory buffers messages, so the message sizes must be in the range of an integer value. Parameter name: bindingElement.MaxReceivedMessageSize fernando MaxReceivedMessageSize and MaxBufferSize must same value and MaxBufferSize is Int32 . Use the defaults for the maximum size so one doesn't