There is no real super-easy way/application, to let someone take control of another's PC over the Internet, without any intervention by the owner at all. If that was possbile, that means there is a security problem. (I know there are some server-based solutions in the market, but those are for the large-scale deployment by off-site/remote maintenance pro's and companies, for example.)
So, be it Windows Remote Assistance or a VNC variant that you will want to use eventually, there are certain number steps of configuration unavoidable. By further reading into the descriptions at
UltraVNC site, I find that the
SC (SimpleClick) feature they offer should best fit your needs. It will reduce the config hassle for your counterpart to the minimum, while it gives that task over to yourself; what you will do is to pre-configure a couple of things for your counterpart to use UltraVNC, and you will send that pre-configured package to him over e-mail or some other way.
You will have to do the following setups on your own local network:
1. Define one PC that you will want to use to control the other's and assign a static IP to it; this is a must-requirement to use UltraVNC across routers (=over the internet) in this scenario. (I see that you have multiple PCs within your LAN; I'll come back to the point as to how to handle this situation.)
2. Forward port 5500 to the defined PC, with its static local IP.
3. Find out what global IP is assigned by the ISP to your router.
Since your global IP will likely change each time you connect to your ISP, you will need to check it up every time you do a preconfiguration.
This info is needed for you to preconfigure the UltraVNC SC package for your counterpart. It should be noted in the "HOST" section of the "helpdesk.txt"
Then create the customized UltraVNC SC package. I am not further going into details of how to create it, as this should be self-explanatory at their site.
Once the creation is done, hand it over to your counterpart. He will start the SC executable, and you will start UltraVNC Viewer in "listen mode" on your end. You may want to advise your counterpart to simply turn off his third-party firewall software, if any, only during the connection for the ease of operation; otherwise, he may be seeing warning messages telling him there are some outbound connection being made, to which he should agree.
I have tried this myself successfully using two different networks with Windows XP machines at both end.
[Assigning static IPs]Assuming you are the admin of your home LAN, in other words, there is no one else on the network who will manually and randomly change the IP settings of the PCs, I would recommend you to provide all the permanent PCs with a static IP. Like that way you will have less chance of PCs fighting for an IP. Additionally, it will be handier should you decide to set up a server inside your LAN later on. You can still leave your DHCP on, just in case somebody comes and visits you with a wireless PC and you want to let him use your network. Keep DHCP ranges separate from the pre-assinged IPs, in order to avoid such "visitor" PC try and grab a pre-assigned IP.
Example:Your DHCP range (found in the router setup) : starts from 192.168.1.45
Your PCs ---
Desktop : 192.168.1.31
Laptop1 : (Wired adaptor) 192.168.1.32 (Wireless adaptor) 192.168.1.33
Laptop2 : (Wired adaptor) 192.168.1.34 (Wireless adaptor) 192.168.1.35
... and so on
If you do not want to assign static IPs to the whole fleet, that's okay. But do assign one to the PC you want to use for UltraVNC, and keep that IP number away from the DHCP range. From what you are writing, my guess is that your router is configured to assign IPs starting 192.168.1.4X, so it should be safe for you to try 192.168.1.3X numbers. It shouldn't mess things up, but in case you really don't get a connection, do not panic. Put it back to "automatic assignment" and it'll be fine. Just make sure there aren't many PCs booting up at the same time you are changing IPs.
With Windows Remote Assistance, static IP isn't really a must-must, so long as you have UPnP on both ends and MSN Messenger or Windows Messenger is working with the two parties on-line at the same time. (Other way around, if UPnP isn't active then yes static IP is a must.)
Reply
Not only that, if they are using other firewall programs that I'm not familiar with, well...you know the rest LOL.
).
