Dameware Version 12.1
Running in Centralized Mode with Seperate Proxy Server on DMZ. All necessary ports verified open.
I have finally reached the end of my patience and so has my employer. We purchased Dameware Remote Support with Centralized Server to meet client support needs and support our employees worldwide during the Covid-19 response as we have been migrating thousands of people to Work At Home. Everything we run is on Windows 10. 1809/1903/1909. All kept up to date. So far all functions of Mini Remote and Central Server work except for the one we purchased this for. Remote Host connection. We can connect via temporary internet session link. We are unable to connect to machines that have downloaded the client from the permanent link if they are Win10. I can connect to Win7 and Server 16. More than two weeks of troubleshooting, daily Solarwinds support calls and this is still not working. I am in the hot seat now as I suggested this product to my employer as a solution to our need. Now it does not work. Have always been a huge fan of Dameware, this has been a very disappointing experience.
Any help would be greatly appreciated. My tail is seriously on the line here and I am not sure if Dameware realizes the position they have put me in.
Ronny Tagoylo gave me the fix for this.
Here's the article that made your Windows 10 connect with the unattended session.
Below are the steps that made that work.
1) On the remote computer, open Regedit
2) Navigate to the following registry key:
3) Add this registry entry with the following values
Value name: EnableDefaultHttp2
Value type: DWORD (32 bit)
Value data: 00000000
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.