Rnon wrote:WOW... thank you very much petoulachi.
you'r welcome
Rnon wrote:
I'll now get to work on it but I wanted to ask one last question about the concept if you guys don't mind:
Why using that strange "inverse connection" concept?
Took me some time to get used to it (I must say that the docs were very CLEAR about it - I just had to except what was clearly there).
When I use UVNC to connect to my LAN computers, the concept is clear - the computers are listening all the time and I choose (when I feel like it) to initiate the connection and check them (much more intuitive and makes total sense).
Inverse connection concept is ESSENTIAL if you don't want to configure anything (NAT) on the VNC Server : indeed, the server will initiate the connection, so NAT will not block it.
Don't forget when using inverse connection, the server isn't waiting for a viewer connection as it's the server himself that will connect to the viewer (if you are not using Repeater). So, you cannot use inverse connection and take a remote control without any action from the remote PC, as the VNC Server is not running all the time as a Windows Service.
Rnon wrote:
Connection to the remote computer via remote Repeater is also reasonable (the way that petoulachi nicely explained, thank you again).
BUT if I wanted to host my Repeater in my own LAN, I need to permanently Open Ports on my router Repeator to the Repeator that is forwarding those ports to my computer???
AM I RIGHT?
If you want to host the Repeater on your LAN, you will only need to open 1 port (5500) and forward it to the Repeater Server. then, the remote PC will launch VNC Server using inverse connection, and going to initiate connection with you repeater on the 5500 port.
Rnon wrote:
And if I am, why do I need Repeater? (if I choose to open those porst and I'm using one computer to view many other remote computers, I may just forward those ports/that port directly yo him....
no, in fact you don't understand that when using a Repeater on your LAN, you will only need to open ONE and only ONE port : 5500. The VNC Server will connect on this port BUT GIVEN ALSO AN ID THAT IS MANDATORY.
You also need the SAME ID when launching the viewer. Without this ID, the repeater can't connect the VNC Server with the VNC Viewer.
So if you want to take control of 3 remote PC, you will need to have 3 differents ID, giving one ID for each VNC Server, and you will also need to launch 3 VNC Viewer, each using one of the three ID.
Rnon wrote:
I just wanted to understand the concept (and the motivation) better. I feel better somewhat to use a remote server that is protected as a server and is having a static IP anyway.
The way suggested by petoulachi is just what I wanted and the concept really remind the NAT2NAT I was talking about except thise time, I'm hosting the NH - many people were asking for that in the past.
Thank you.
I think that Repeater is not the solution for you, as you seems to need to take remote control whenever you want and without any action of the server. You need to have the VNC Server to wait everytime for a connection, and Repeater is not made for that.
PHW is made to make remote assistance much easier : indeed, to take control of a remote customer PC, it's become much much easier as the customer don't have to configure anything : launch the VNC Server using inverse connection, filling an ID given by the hot line.
, I was looking to find in the docs as first thing the general idea of each was the the differences (UVNC, NH, SC, REPEATER, PHW - lots of GREAT solutions and big mess)
).