Menu
After upgrading from windows 8.1 to windows 10, None of the projects that have a WCF service available through net.tcp connections are able to connect.
The exception i get is:
The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '19:59:59.9769910'
the inner exception code is: 10054
But the exception happens right away. So it's not a time-out.
I checked IIS and everything is still configured right. (still have the right binding on the site, enabled protocols http,net.tcp)
I checked my services if net.tcp listener adapter was running and it was.
I checked windows features and saw that windows communication foundation non-http activation was turned off. so i turned it on and restarted my PC and still get that same exception.
I've waisted a total of 4 hours so far trying to get the net.tcp connection to work but i'm kind of losing hope here.
here are the windows features i've turned on:
and here are the windows services i have running:
Did anyone else run into this issue when upgrading to windows 10?
925
Press the Windows key + R, then type "cmd.exe" and click OK. Enter "telnet + IP address or hostname + port number" (e.g., telnet www.example.com 1723 or telnet 10.17.xxx.xxx 5000) to run the telnet command in Command Prompt and test the TCP port status.
In the Name column of the list of services, right-click the Net. Tcp Port Sharing Service, and select Properties from the menu. To enable the manual start-up of the service, in the Properties window select the General tab, and in the Startup type box select Manual, and then click Apply.
When an unexpected TCP packet arrives at a host, that host usually responds by sending a reset packet back on the same connection. A reset packet is simply one with no payload and with the RST bit set in the TCP header flags.
I finally got it working after hours of trial and error. I am not 100% sure if this is what actually solved my problem in the end, but give it a try:
174
We've managed to resolve this issue.
We were using a certificate in IIS with an old encryption method that was no longer being supported. (it was using MD5-RSA) Now this was stil working in windows 8/8.1 but the certificate was no longer valid in windows 10, causing this behavior.
The solution was to get new certificates with better and supported encryption algorithms and set them up in IIS on my machine.
I'd also like to apologize for answering so late!
35
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
