[SOLVED] "Open Remote Session" not working

_0M0D0 · May 6, 2013, 7:39pm

Hi,

I have installed the latest version of ESM in a Windows 2008R2 server and was able to deploy CES into a Windows 7 Endpoint. The server is located in the US, and the endpoint is located in El Salvador, Central America (Windows and Comodo Firewall are off).

I am trying to use the “Open Remote Session” option and is not working.
When “Current Connection Mode” is INTERNET, is it possible to OPEN A REMOTE SESSION?

I am only getting this message:

noVNC ready: WebSockets emulation, canvas rendering
Connect timeout
Trying to reconnect...
Connect timeout
Trying to reconnect...
Connect timeout
Trying to reconnect...

…and so on…

MichelB · May 7, 2013, 10:08am

Hi,

Are you connecting to the ESM server via an IP address?

If so then the VNC connection capabilities are erratic at best, try to RDP to the ESM server and VNC to the target from there.

Please advise your results.

Kind regards,
Michel.

_0M0D0 · May 7, 2013, 4:03pm

Do you have those intructions for a “dummy”? 88) :embarassed:

MichelB · May 7, 2013, 5:58pm

Sure (not so much of the ‘dummy’ though please :))

Your ESM host is internet-accessible I presume so,

Open port 3389 (RDP) on your firewall and NAT it to port 3389 on your server.
from the remote machine, run mstsc.exe and put the ESM server’s public address in the dialog box
you should then have a Remote Desktop Connection to your ESM server
open a browser on your ESM server and log in
click on a tile and launch Remote Connection

Let us know what happens…

_0M0D0 · May 7, 2013, 8:27pm

Oh ok! Now I understand what you mean. Sorry. :embarassed:
What you mentioned is precisely what I am doing.

As I mentioned, ESM server is in USA. So the only way I can access that server is through RDP.
So I installed and did all the setup (console and ces) through RDP.

Once I am in the console (using the server’s browser) connected through RDP, I try to open the remote session to my laptop which is in El Salvador (right in front of me). Then I get the connection error I reported.

Do I have to tweak something in the server, besides already doing what you mentioned?

Thank you for your assistance.

MichelB · May 11, 2013, 7:27am

Hi,

Could you let us have the ping times please?

_0M0D0 · May 11, 2013, 7:44pm

PING from Endpoint to Server

C:\Users\USER>ping X.X.X.140 -t
Pinging X.X.X.140 with 32 bytes of data:
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=80ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=78ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=78ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=78ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=82ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=78ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=169ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=210ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=79ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47
Respuesta desde X.X.X.140: bytes=32 tiempo=77ms TTL=47

Ping statistics for X.X.X.140:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 210ms, Average = 88ms

PING from Server to Endpoint

C:\Users\Administrator>ping X.X.X.190 -t
Pinging X.X.X.190 with 32 bytes of data:
Reply from X.X.X.190: bytes=32 time=89ms TTL=49
Reply from X.X.X.190: bytes=32 time=77ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=75ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=75ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=75ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=75ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49
Reply from X.X.X.190: bytes=32 time=75ms TTL=49
Reply from X.X.X.190: bytes=32 time=76ms TTL=49

Ping statistics for X.X.X.190:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 75ms, Maximum = 89ms, Average = 76ms

_0M0D0 · May 11, 2013, 8:38pm

What about this screenshot?

[attachment deleted by admin]

_0M0D0 · May 12, 2013, 11:51pm

I am also getting this WARNING in the Configuration Tool:

DNS failed to be resolved by IP
 address: 190.X.X.X
 exception: No such host is known

That IP address is the one assigned to the endpoint.
Could that be the reason why I cannot connect remotely through desktop?

_0M0D0 · May 19, 2013, 4:39am

Any comment?

Denmihalich · May 20, 2013, 11:42am

Hello w-e-v,

“Open Remote Session” functionality currently works only inside the same local network.

In one of the future sprints ability to establish remote connection to endpoint over the internet will be implemented.

Thank you for your interest in our product!

_0M0D0 · May 20, 2013, 1:56pm

Thank you. Any time frame or approximate date?

MichelB · May 20, 2013, 8:16pm

We are expecting to have this working by end-June or early July

Regards,
Michel.

reelgriff · July 6, 2013, 2:29am

I’m having the same problem with the remote desktop failing on my CESM 3.0. It worked well for a few weeks, but now I can not remote desktop any of the machines on my tiny LAN. V 3.0.60418.2 Any assistance appreciated.

MichelB · July 7, 2013, 7:53am

Hi guys,

Please bear with us while we do internal testing of version 3.0.60702.3. We will be releasing a little later this coming week to our MSPs for private testing and then public release shortly thereafter.

Thank you for your patience.

Regards,
Michel.

reelgriff · July 7, 2013, 1:07pm

My issue may have been different. I think my install became corrupt. Only with a system restore did it start working correctly again.

MichelB · July 8, 2013, 8:04am

Glad to hear it is working again

_0M0D0 · October 10, 2013, 10:44pm

Thank you. This issue has been solved.

MichelB · October 11, 2013, 12:02am

…and another one gone…