cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 7

Can't connect Internet sessions ; link invalid or expired

Hey guys,

I'm trying out Dameware as a replacement for Logmein, but it seem to only work locally, with users within the organisation firewall. If a user is outside, he can connect to the DameWare Internet Proxy URL, download the agent, but the Mini Remote Control can't connect with the agent.

In this scenario, the central server is standalone (1 machine) configured using port 11443 (Take note that i tried 443 with same result), the corporate firewall is redirecting this port to the central server and the Mini remote control is on the same subnet as the central server (no firewall). SRV01, a test machine is located outside the corporate firewall. It can connect via the URL to the DameWare Internet proxy URL and installed the agent. It shows as online in the Remote Host.

Steps :

1 - MRC start an internet session

2 - SRV02 manually enter the URL in FireFox

3 - DameWare open, then it show that the session is not avaiable. (The session shown in the administration console status)

My Internet proxy config

0 Kudos
9 Replies
Level 9

techfred

This is a Windows 10/Server 2016 related issue where the internet proxy/remote host does not support http2.

To resolve this, you will need to manually add a new Dameware registry key either on the Internet proxy or the remote host

*IMPORTANT* You need to use only one of the settings: either the server or the client setting, not both. We recommend using the server-side setting because it ensures that the issue is solved for all client computers.

Perform the following procedure to add a new registry key on the Dameware Proxy server.

1) Log in to the system hosting the Dameware Proxy.

2) Open Regedit.

3) Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameter

4) Change the following parameters:

Value name: EnableHttp2Tls

Value type: DWORD (32 bit)

Value data: 00000000

5) Save your changes.

6) Reboot the server.

This could also be performed on the remote host (Windows 10 v1709 and later) if the internet proxy is inaccessible:

1) On the remote computer, open Regedit

2) Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp

3) Add this registry entry with the following values

Value name: EnableDefaultHttp2

Value type: DWORD (32 bit)

Value data: 00000000

You need to restart Client Agent service (on remote machine) for the new setting to take effect.

It appears to have worked.  Good to know someone has fixed this and deduced to be a problem on the OS side.  Thanks.

Great help.  Thanks.

So it is a problem on the Operating System side rather than Dameware itself..   Good to know.  Thank you for this..

Level 7

Same here since had Dameware remote support. Gone through the proper channels as well and spoke to the support team on the phone, they are as useful as a chocolate fire guard. Let's wait and hope that someone without a script under their nose will ever read this post and help us out.

0 Kudos
Level 7

Hi,

I have the same issue.. Any luck solving this??

thanks

*edit:

I tried a lot of things, and got it to work.

The client I was using has the Dameware miniremote control agent installed. That's normal, it is used Inside the organisation as well as outside.

So I tried disabling the dwmrcs service, so it forced it to download the Dameware Internet Session agent; that works.

So it is the mini remote control agent that is broken it seems… (I was v12.0.5.6002 then upgraded to 12.1.0.34)

0 Kudos

The http/2 is a Microsoft implementation to make the server-client communication faster and more secure.   

There are 2 parts to this equation, the internet proxy and the Windows machine hosting the MRC console.

For the moment focus on the host where the internet proxy is installed and add the registry key to allow the server-client connection using the steps below:

1) Log in to the system hosting the Dameware Proxy.

2) Open Regedit.

3) Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameter

 

4) Change the following parameters:

Value name: EnableHttp2Tls

Value type: DWORD (32 bit)

Value data: 00000000

 

5) Save your changes.

6) Reboot the server.

0 Kudos
Level 7

DameWare.Server.AdminConsole_2018-12-15_08-07-34.png2018-12-15_08-09-22.pngScreenConnect.WindowsClient_2018-12-15_00-43-55.png

0 Kudos

Any ideas on this type of issue?