nettcpbinding

I’m trying to set up a WcfService with the use of NetTcpBinding. I use Transfer mode Streamed since I will transfer large files. I need to use Session, and I have read that NetTcpBinding supports this, but when I turn it on like: SessionMode=SessionMode.Required I get the error: System.InvalidOperationException: Contract requires Session, but Binding 'NetTcpBinding' doesn't support it or isn't configured properly to support it. Does anyone know what I have to do to make NetTcpBinding work with sessions? Thanks for any help :) Mark D Jackson You've no doubt solved this - but for others that

I have a WCF service that has two endpoints. One with basicHttpBinding and one with netTcpBinding. Here is my config... <services> <service name="SomeService.Service"> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="" name="EndPointHttp" contract="SomeService.IService" /> <endpoint address="" binding="netTcpBinding" bindingConfiguration="" name="EndPointTcp" contract="SomeService.IService" /> </service> </services> However, when I consume the service I am trying to compare the difference between to two requests. So I am running fiddler to do this. I can see the

I'm trying to understand how windows authentication / encryption works with the NetTcpBinding in WCF. I need to know exactly what encryption algorithm is used to encrypt the data going across the wire (and some documentation to prove it). Will windows authentication / encryption still work if the client and or host is not on a domain? The netTcpBinding using Windows Credentials requires the caller and the service to be on the same domain - or at least on mutually trusting domains. Otherwise, the server won't be able to verify the Windows credentials and will refuse the service call. As for

I'm attempting to create a WCF service where several thousand (~10,000) clients can connect via a duplex NetTcpBinding for extended periods of time (weeks, maybe months). After a bit of reading, it looks like it's better to host in IIS than a custom application or Windows service. Is using WCF for such a service acceptable, or even possible? If so, where can I expect to run into throttling or performance issues, such as increasing the WCF ListenBacklog & MaxConcurrentConnections? Thanks! Ladislav Mrnka Why do you need to maintain opened connection for weeks / months? That will introduce a lot

I'm trying to re-write one of our old Servers using ZeroMQ, for now I have the following Server setup, (which works for Zmq requests): using (var context = ZmqContext.Create()) using (var server = context.CreateSocket(SocketType.REP)) { server.Bind("tcp://x.x.x.x:5705"); while (true) { ... } This kind of setup works fine if I use the Zmq client library to connect context.CreateSocket(SocketType.REQ) But unfortunately we've got a lot of legacy code that needs to connect to this server and the sockets are created using .net socket libs: Socket = new Socket(ipAddress.AddressFamily, SocketType

I am hosting 3 WCF services inside windows services.Each WCF service contains Multiple endpoints. Right now, i am host all my endpoints thru TCP binding on different ports. Is there any way to host all these end points from different wcf services on same port? JohnC Sure is! You can use the Net.TCP Port Sharing service. Net.TCP Port Sharing on MSDN I just looked into that, out of curiosity. The behavior I discovered seems so strange that I almost don't want to put it here. But it worked in my case, so maybe it's doing the same for you: I am getting the AddressAlreadyInUseException when I'm

I'm making slow and steady progress towards having a duplex communication channel open between a client and a server, using NetTcpBinding. (FYI, you can observe my newbie progress here and here !) I'm now at the stage where I have successfully connected to my server, through the server's firewall, and the client can make requests of the server. In the other direction, however, things aren't quite so happy. It works fine when testing on my own machine, but when testing over the internet, when I try to initiate a callback from the server side, I get an error: The message with Action 'http:/

I have a WCF Service hosted as Windows Service and client is an ASP.Net application consuming WCF Service methods. In process of implementing security, I am confused over which among netTcpBinding / wsHttpBinding will be suitable for my case. Most likely all the applications in scene (WCF Service, Windows Service, ASP.Net Website) will be sitting on different servers in our office, thus in an Intranet. ASP.Net website will be accessed by users over Internet. Though, I can always use wsHttpBinding here, will it be suitable to set the service endpoint using netTcpBinding in my case? Justin