Windows 10: wcf ssl3 and windows 11

Our customer has an installation of about 70 wcf services running sslStreamSecurity sslProtocols="Ssl3" on operating systems W2012 to W2022. He also has about 300 wpf clients connecting to these services.In addition, the certificates used in the system have md5 algorithm.Everything works over a private network, so the privacy of communications is not the most important thing.Neither Ssl3.0 nor md5 works on Windows 11 and it is a big problem. We don't know how to deal with the upgrade of the operating systems.Is there any way to force Windows 11 to use Ssl3 and md5 certificates?If not, how can

:)

 

a call from WCF Client using a distributed transaction on one workstaion blocks all WCF Clients that use the same WCF Service from different workstation for an extended period of time?

Aside from removing the TransactionScope created on the WCF client (and effectively taking msdtc out of the picture), Is there an alternate way to avoid the excessively long WCF-service-wide hang when a single workstation hosting
the WCF client is misconfigured (or experiencing communications issues)?

We have a simple WCF service implemented using C#, and a simple WCF Client which creates TransactionScope before invoking the WCF service proxy.

Both work fine as far as concurrency goes if Windows Firewall allows TCP communication from/to msdtc.exe thru firewall. However if a single workstation is misconfigured (i.e. has firewall enabled, and has an Inbound Rule for TCP for msdtc.exe disabled),
its attempt to communicate with the service will block all other WCF clients (which are properly configured) from communicating with the WCF Service for at least 41 seconds (given the currect settings for TCP retransmissions), despite us using much shorter
timeout settings for the WCF binding as well as for the TransactionScope timeout.

The WCF service is decorated with

[System.ServiceModel.ServiceBehavior(

InstanceContextMode = System.ServiceModel.InstanceContextMode.PerCall,

ReleaseServiceInstanceOnTransactionComplete = false,

ConcurrencyMode = System.ServiceModel.ConcurrencyMode.Multiple,

IncludeExceptionDetailInFaults = false,

TransactionTimeout = "00:00:13"

)

The WCF service has a single operation contract, decorated with [System.ServiceModel.TransactionFlow(System.ServiceModel.TransactionFlowOption.Mandatory)] in the class interface.In the class itself, the same method is decorated with [System.ServiceModel.OperationBehavior(TransactionScopeRequired
= true)].

The WCF service is hosted using a Windows console application which uses a netTcpBinding configured with transactionFlow="true" transactionProtocol="OleTransactions" sendTimeout="00:00:20" receiveTimeout="00:00:20"

The service is accessed from a Windows Forms client application configured with the following values for its netTcpBinding:

transactionFlow="true"

transactionProtocol="OleTransactions"

transferMode="Streamed"

sendTimeout="00:00:20"

receiveTimeout="00:00:20"

 

Windows WCF Service Concurrency

Hi,

I am rajesh from chennai, We have created WCF Service and hosted as Windows Service, the service don't response on concurrency mode (we have added concurrency mode as multiple and percall instance). when limited users are accessing the service it works fine,
but on multiple access (more than 50 users) , the service don't respond and after restarting service, it works. can you please suggest any settings have been missed out / misconfigured.

 

WCF rest service template

How do you add the WCF rest Service template to Visual Studio 2015?