- Login to the members area using any web browser.
- Create a support ticket for each client's PC you wish to access.
- Instruct your client to visit www.iremotepcsupport.com and enter the Ticket ID. (Optionally - client can check their e-mail for the support link)
- When the client clicks the link, a temporary program loads onto their system (which will not require any install/admin rights and works on any Windows PC). They need not be iRemotePC users at all.
- You now have complete access to their PC for remote assistance
Launch Quick Start guide - Remote Support Service
No Matter where your clients are - our Remote Support service will work for you. iRemotePC is Firewall Friendly and works securely behind Firewalls/NAT!
iRemotePC provides you with a guaranteed connection to your Customer by automatically going through a secure, safe encrypted security process everytime you remotely access your client/recipient's PC for remote support!
iRemotePC Architecture
iRemotePC establishes a direct connection between the local and remote PC for fast and secure remote access (i.e. remote control or file transfer purpose). The system does so by utilizing a sophisticated approach called; TCP NAT Traversal – Hole-Punching. This involves client and host to negotiate with a rendezvous server using SSL and hole-punch through the respective NATs of clients and hosts using TCP.
The benefits are numerous with TCP NAT traversing. Having a TCP network layer itself provides excellent reliability and speed by facilitating automatic recovery of packets, robust error-handling, platform independence, guaranteed delivery, and requiring low data overhead.
Once a dedicated connection has been established between two peers, iRemotePC encrypts all data sent and received in the connected path using 128-bit Advanced Encryption Standard (AES) algorithm; which is a standard by the U.S. Government for robust security.
http://en.wikipedia.org/wiki/Advanced_Encryption_Standard
Process flow
- There would be three main entities involved in this process:
- iRemotePC Rendezvous Server (Always be visible on the internet. Facilitates the communication between components).
- Client (Technician visible on the internet or behind some Proxy)
- Host (Customer visible on Internet or behind some Proxy)
- Host registers with Rendezvous server and has a persistent connection by exchanging messages periodically
- Client connects to Rendezvous server requesting for a remote access connection to its Host
- Host opens a TCP connection with Rendezvous server on which the identity of Host and client is exchanged
- The same TCP connection is used to perform NAT Traversal directly between host and client.
- Actual TCP connection is established between the NAT on the two sides of the host and client. On-the-fly 128 bit AES encryption/decryption kicks in during the actual data exchange between the peers.
- If TCP NAT Traversal is unsuccessful, a fall-back RELAY mechanism kicks in where the connection between the Host and Client is relayed through a least-loaded Rendezvous server over 128-256 bit enterprise-grade SSL encrypted connection. The data is then 'streamed' in real-time between the host <> rendezvous server <> client. This SSL connection is based on native TCP SSL sockets and handshaking. So its independent of the web browser. No data resides on the central server at any point of time for any reason.
