Web based remote support

[p3rlphr33k]

Hello, this is my first post and I hope this is of useful substance to everyone here. My name is Bryan and I want to share a working demo with you.

I have built up a web-based VNC remote support AND unattended access software. This is running live on my website! I will share the link but first, I want to make sure I am not spamming the board so I need the OK from the admins. Second, It is not perfect and relies on a whole pile of technologies i will list off:

UltraVNC SC is used for the server (person receiving the support)

NoVNC is used for that viewer so a technician can assist from any browser!

ultravnc_repeater.pl is used to bypass NAT issues (unless oubound filtering is enabled) <--- THIS IS WHERE I NEED HELP!

websockify is used to proxy the viewer to the repeater to eliminate the admin needing PC privileges.

Here is a walk through of the process..

Scenario I:
A person needs assistance, calls the tech support.
Tech support directs customer to said (secure) website.
Customer clicks "Connect as a customer" and technician visits the same site, clicks "connect as technician"
technician is issues a random ID of whatever length specified in the code.
customer is presented with a box to enter the code.
customer enters code provided by technician. both click connect.
customers code is processed by a script that builds an executable containing the SC config with the ID (currently only windows support) using 7z.sfx binary and 7zip
Same goes for technician, program processes the generated pin and redirects technician to (secure) NoVNC where viewer is connected to repeater using secure websockets (WSS)
Customer is asked to run the executable (SC) it to connects to the repeater using the ID provided by the technician.
TaDa - NAT is bypassed and technician can now access customers PC, no software installed only UltraVNC SC generated on the fly!

Scenario II:

Technician logs into (secure) website on customers physical PC
Technician installs a small "listener" client.
Technician configures client with his account credentials
technician can now see if the machine is registering on the website with last checkin, WAN IP, current status (online/offline)
NOW, technician can login into website from anywhere and click "Connect" on any PC that is showing "ONLINE" status
the technician is redirected to a (secure) NoVNC page that already has a random session PIN generated.
NoVNC uses WSS to connect to repeater same as before.

Here is when things get strange...

When the technician clicked "Connect", this triggered:
A) random ID to generate
B) a script to generate the response URL for NoVNC
C) a SQL entry for the "listener" agent

The listener checks in with the server using SSL every 60 seconds (configurable)
If the server has a response in the database it replies with that data, which is a connection string containing... the repeater ID!
the "listener" sees the string and calls UltraVNC with the connection string

TaDa - unattended access!

I would like to make this more reliable and cut out the repeater making these connections peer2peer using the unreleased Nat-To-Nat "ServerHelper" software. Can someone provide a download?

As stated before, I can provide links for testing this working configuration but I would like the OK from the admins prior to posting links.

I would appreciate any assistance in making this stable LogMeIn and LogMeIn123 replacement.

Thank you for reading.

-Bryan

[p3rlphr33k]

Here are some photos of the applications at work.

Remote Support (NoVNC & UltraVNC SC)

Customer Remote Support Screen


Technician Remote Support Screen


Customer SC application


Customer App Launch


Technician NoVNC


Unattended Access Screens (NoVNC, UltraVNC SC, agent, web)

[Sainsuper]

It 's seems a great project. It is prossible to try it?

[p3rlphr33k]

yes it is, at the top of my post i requested permission from admins to post the link but I have not gotten the go-ahead. I will message you my website address. Keep in mind that I build and demo a lot of different projects on the site i am about to send you.