Ask Slashdot: Options For FOSS Remote Support Software?
Albanach writes "I'm sure I'm not alone in being asked to help friends and family with computer issues. These folk typically run Windows (everything from XP onward) or OS X (typically 10.4 onward). Naturally, desktop sharing is often much easier than trying to talk the other end through various steps. I've found free sites like join.me but they don't work with OS X 10.4, neither does the Chrome plugin. I'd also prefer not to compromise security by using a third party in the middle of the connection. Is there a good, free solution I can run on my linux box that supports old and new clients that run Windows, OS X and possibly linux? I'd love it if the users could simply bring their systems up to date, but that doesn't solve the third party issue and it's not easy when it requires a non-trivial RAM upgrade on a Mac Mini."
Because that's what you want.
Hail Eris, full of mischief...
E pluribus sanguinem
VNC is probably the most prolific remote access client / server software in existence. It is open source, although some companies have created enhanced functionality on top of VNC which is available as commercial products. OSX supports VNC type remote access natively.
Better known as 318230.
The Google+ hangouts works for my students when they have software issues. I second-seat them and things run smoothly. If you are doing the maintenance on their computers, you can ensure that the plugin installs correctly and go from there. -TN
OK, that's a stretch....
It isn't the best but it runs on just about anything you can think of.
LMGTFY - two of the top 5 hits point to TightVNC...
its free for non-commercial use. my mom lives almost 2000 miles away and that's what i use to help her.
Free and Open Source Software Remote Support Software
For the Windows boxes at least, an RDP client like Remmina works. (xrdp works as server on linux btw.) This might not work on Mac, so VNC is good to have also, but some Windows boxes will just happen to have RDP available (remote desktop) and it's easier to use something they don't need to figure out how to install.
What you're looking for doesn't exist. VNC is great, but without the middleman you're never going to have ease-of-use for the people you're trying to help... they're going to give up trying to get port-forwards set up on their router long before you actually get in to help them.
Logmein / Teamviewer / etc is what is needed, and just plain works. If you have to choose one, it should be Teamviewer... can run client and support on all three specified platforms, and the QuickSupport option on Windows is a godsend - nothing like telling a client / grandma / whoever to simply download and run a small executable to let you in and help them.
Other posts have already mentioned VNC, naturally. But more specifically, what you want is reverse VNC. You set up a VNC listener, and firewall port forwarding etc. on you end. Then ask the user to download a simple server executable (e.g. tvnserver.exe in the case of Windows/TightVNC) and connect to your IP address.
Its not FOSS, and there is a middle man to negotiate things to get you connected.
It is however free for non-commercial use.
You can remote control -from- Windows, OSX, Linux, iphone, and android.
You can remote control -to- windows, OSX, Linux, and recently samsung androids.
It just works. The person you are trying to support can get connected to you by clicking the "Join Remote Support Session" URL, and running the quick support app. They don't have to install the software, or configure their firewall, or fiddle with various modes etc.
You can connect to pretty much anyone anywhere from pretty much anything anywhere.
How does it compare to the various VNCs? Its much easier to get a connection going, and you don't waste more time trying to get a remote session going than it takes to actually perform the remote support.
Now, VNC is great, and if you set up your own public VNC repeater, and bundle your own VNC client to use that repeater you can get most of the way towards what you get with teamviewer without any effort at all.
Jitsi
I am the family geek and have found the best way of dealing with this is to organize a time to visit. Hop in car and stare at the problem in person. Set up access levels. (You don't get to be admin all the time there Mum) Set up schedules.(Leave your computer on overnight on Sunday night so the little maintenance men can do their work) Setup backups. (Where is that USB hard drive you got with this?)
If people get into problems, and they need service right away, tell them to drop the computer off at the local computer store. If it's important enough to need to happen now, then it's important enough to pay for the privilege.
Remote tools are handy for intranets (As I type I am using 2 different types). They are a security risk for internets.
A sig is placed here
To display how futile
English Haiku is
I've been helping my now 83-year-old dad since the Win2K days using this solution:
- On dad's machine, install VNC server and PuTTY SSH client
- Set the VNC server NOT to run in service mode.
- Set the VNC server to accept connections from localhost (That used to be a registry setting, but it might be the default now)
- Set up a user called "sonarman" on my Linux machine. sonarman's shell is a script that loops forever, printing the date and hostname, then sleep 60.
- Set up a public/private keypair so sonarman can log into my linux machine without a password
- Set up a PuTTY session for sonarman that uses the private key to connect, and that forwards some port on my linux machine to the VNC server port on my dad's computer (5901)
- If necessary, tell Windows to allow PuTTY.exe to go OUT through the Windows firewall.
- Created a folder on dad's desktop called "Get help from Mike" - inside are two windows shortcuts, one to start sonarman's ssh connection to form the encrypted tunnel, and one to start the VNC server.
So when dad has a problem, he calls me, he opens the "Get help from Mike" folder, and double-clicks the PuTTY shortcut. When he says "OK, it's showing me today's date", I tell him to double click the other shortcut, and he tells me when the VNC icon shows up in the notifications area.
Once that's done, I connect a vncviewer to localhost:<whatever port I set up>, and I have a view of and control of Dad's desktop.
He can't do any harm to my system, because sonarman's shell doesn't accept any input.
Because his computer is initiating the connection, he doesn't need a fixed IP, nor any holes through the firewall besides the *outgoing* ssh connection.
My linux machine has an entry in DynDNS, and dad's PuTTY connects to my machine by hostname, so as long as my dyndnsd keeps the name up-to-date with Comcast's periodic re-assignments of my IP address, dad's computer can always find mine.
My firewall must be configured to allow incoming ssh connections (but I want that anyway).
I see most people here are recommending VNC. VNC and its brethren work, but can be very slow. A propriety alternative is Team Viewer. It is free as in beer and like VNC runs on all platforms under the sun (including Android and iOS). It is unlike VNC in that it is rock solid (I've never seen it hang), always quick enough to useable and requires no special setup to pierce NAT and firewalls.
I hope that one day open source figures our what the magic sauce is in Team View is and replicates it in VNC. Until that day arrives when I need to get shit down, I just use TeamView.
Its self hosted and cheap and doesn't have the VNC problems like it works via the firewall.
Next I PHONE the person and get them to start up "Terminal" and copy/paste the commands above into the Terminal window. I also tell them what to type into the Terminal window when it asks for the "help" account's password.
Now I can start up my VNC client and connect via port 5901
-- "At Microsoft, quality is job 1.1" -- PC Magazine, Nov. 1994
Logitech and best buy routinely sell cheap decent webcams. I've picked up regular ones, and 720p and 1080p HD versions for under ten bucks each shipped.
Bought one for each family member.
When they have a problem, I start a video chat with them, they take the webcam off the monitor and point it at the screen. On some cams you have to click the 'mirror' button to reverse the image. Then we work on the problem. If that computer is dead, put the webcam on a laptop and use that, or do a video chat with their phone or pad if they have one.
Securing software, poking hole in firewalls and all that seems like a waste of time when you can actually SEE whats going on for yourself.
Start with something quick, commonly used and easy to "get 'er done".
Middle man or not. Even a 30 day evaluation package.
Then load and configure something more to your liking, test it
and unload the first tool.
The alternative is a house call which might be fine.
I would bet you owe the family members involved a visit!
Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities; Truth isn't. Mark Twain.
I've been using Ultra VNC Single Click http://www.uvnc.com/pchelpware/sc/index.html for years. It only works with Windows, but it is small, open source, and relatively secure.
1 Your support client calls you
2 You open VNC in listen mode
3 Your support client runs a custom version of UltraVNC SC that is set to connect only to you.
Easy. Fast. Cheap. And it works.
engineers are all basically high-functioning autistics who have no idea how normal people do stuff
I'd suggest TeamViewer (http://www.teamviewer.com/)
No, it's not FOSS. But it is free as in beer and it also runs on Windows, OS X and Linux (the Linux build though is technically the Windows build packaged via a Wine bottle, all self contained and preconfigured well though). Sounds like the $-free and cross-platform aspects are probably more important overall to your needs than being open source. Plus you don't have to worry about firewalls or anything - I can even access my home system at my workplace through just the browser, no extra ports except 80.
Most people on Slashdot are fucking idiots.
When I sent my dad a Linux computer because his old Windows machine was taken over by malware (no amount of remote help with running various cleanup tools helped), I set it up to automatically SSH to my home server every 5 minutes and open a tunnel back to his computer desktop's VNC port as well as an SSH port as a fallback.
it came in handy when I had mistyped his home wireless router's WPA key before sending the computer, I just had him plug the computer directly to one of his router's LAN ports, and then I was able to remote in and fix it.
VNC, as others have noted, works on lots of platforms (including older ones). You'll have to configure it in their firewall, and I use a non-standard port as well.
Some VNC versions allow a form of access control, but that doesn't help if your IP or IP range changes.
And while I realize that there is an actual cost involved to fix it, letting them stay on primitive hardware and OS is not really helping them. Sadly, "because it still works" is less and less a good reason to keep an old PC running. Not too long ago I was asked to clean up a virus-infested Windows ME box - yes, it still boots ... but it had so little memory that none of the current antiviruses I had available would even run.
Doug
VN fucking C... !!!
Is this what slashdot has come to now???
As mentioned elsewhere there are two main commercial solutions - non-foss. Teamviewer and Logmein. Logmein free is legal for commerical purposes and I put it on clients machines when I have them on my bench but it is limited. Teamviewer is just plain awesome but is not free for commercial use and they seem to watch. As is their right.
So the solution is obviously to make your own teamviewer-like solution. After much hairpulling I realized VNC is the answer but I wanted a use-anywhere-help-anyone solution. I then realized I needed a VNC repeater, this is basically what teamviewer et-al do. Otherwise YOU have to be behind a configured firewall.
Chunk VNC (you can google it yourself ;-p) is a project that is imminently doable. I deployed a repeater on my own always-on computer, configured the firewall appropriately, and customized the appropriate files. After some patience I have a totally free and branded remote support solution that requires no more from the client than teamviewer instant-support does. And, it works AS GOOD AS vnc is rightly known for.
Flappinbooger isn't my real name
You might want to check out a program called Checkride. It is an open source program developed in Lazarus. It is basically a preconfigured portable VNC and stunnel package. To use you configure it to connect to your computer and give it to the person you are trying to help. The executable you send them starts VNC server and then connects to your computer via stunnel. Your PC then starts VNC viewer on your side and connects to their desktop via the secure stunnel connection.
Checkride
It is NOT open source, but is in free as in beer for your use.
It supports Windows, Linux, and OS X.
Teamviewer is very use to use; I worked in IT at a business with about 800-1000 desktops and laptops, and i never experienced the users having trouble with it. They just called support, and it would go "Please click the "Company-Name Support" icon on your dekstop" "OK" "Now tell me your ID" "xxx xxx xxx" "And your newly generated passkey?" "xxxx" and they would be good to go.
I installed it on my grandparents (85 and 82) laptops to ease the time i had to use on helping them, with the laptops. They never had any problems with it.
Theres some options, like VNC, Skype, theres a Plugin in pidgin (not sure). But, my option to do same of you want, is Hangout and TeamViewer. Simple and Easy, and free for not comercial use. :)
Don't be ridiculous. The likelihood that a hard disk will die or your house will burn down is far greater than the likelihood that someone will try to break in to the computer of your relatives by exploiting a VNC connection, and even if they do they will be in for quite a let down when they realize that their booty is nada. There are far better ways to compromise a Windows system. Only a moron would forgo those in favor of the "dreaded VNC attack vector" of which you are so afraid.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
I use this commercially, and its a super product. In fact I am duplicating 1 TB across a vpn tunnel on it right now.
Now you may not have noticed, but on the team viewer web site, on the main page is a link for "Join Remote Control Session"
this requires no admin access at all, and is not a installable product. I use this for exactly the case you state. You walk them there
to the website, tell them to click and run that. Then ask for their numbers. Really that is as about as simple as it gets.
This is also the only product my "secure" customers trust. So we plunked down 1400 for a real license after using it for
several months. Great product.
Mikogo (www.mikogo.com/) is pretty good. I think it's pretty much what you're looking for, FLOSS and cross-platform.
If you're capable of mapping the ports on your router and setting up a free ddns provider you might want to give Gitso a try.
https://code.google.com/p/gitso/
UltraVNC Single Click. I have a binary in my public dropbox for all buddies to download and run. Just a matter of starting the listener in my side.
OK, windows-only, but you can make a OSX shell script to do the same thing there; at least you have a full-featured shell.
And for security, UVNC have a DSM plugin, if you don't really care about full compatibility
eliphas
1. Set up a secure VPN server at your site. This serves two purposes: getting access to external machines, and security.
OpenVPN is a good one to use, but if you can set up OpenVPN AS either on a Linux box or in a Linux VM you'll make life much simpler for everyone.
2. Set up the people you want to support with VPN access.
3. Set up VNC on their machines. TightVNC running as a service is ideal, but take the following precautions:
a. Set the service to Manual so they have to turn it on each time.
b. Have authentication.
4. Create easily-accessible shortcuts for them to use, and train them to use them.
5. At the start of a support session, get them to connect to the VPN, start the VNC service. You can either get them to tell you the IP address, or look at the currently-active VPN connections.
6. At the end of a support session, get them to shut down the VNC service and disconnect from the VPN.
I've found that even computer neophytes can be trained to do their part, and if they've got a minimal level of skill it's possible to talk them through the initial setup of the VPN and VNC client software. You just need to get them to the point that you can remote control, and then you can lock it down (changing service to Manual, etc).
As you know, in order for you to remotely control any computer, it must have real IP, static IP, whatever IP, or with other words: well known IP. And as you very well know, 99% of your friends (including you) don't have this little feature. The only possible solution to this problem is to have dedicated server, where you could rune your redirector, router, tunneler, you name it. Once you have this server, and he is under your full control, you could use any encryption, any client, any OS.
For familial tech support I swear by Teamviewer..Its not opensource but for non-commercial use, such as what I use it for, its free. It works on Mac/Linux/Windows AND Android.. I'm in Nevada and I have relatives in San Diego, Sacramento and back in Illinois.. I have Teamviewer installed on everybody and when they need a hand with their systems, I connect up and "look over their shoulders". Since I'm usually on Linux, its fantastic to be able to help them no matter if I'm on Windows or Linux.. Once a cousin gave me a call saying he was having trouble printing, so I teamview'ed from my Android smartphone... Worked fine, and got him going in a few minutes... Can't beat it..
THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
Gitso is cross-platform and - get this - you do the "hard stuff" like open ports (easy for you, hard for grandma), your relatives just need to install the program and click a dialog box. That's it. I don't know if it's been updated in the past year or two, but it was extremely promising back in the day.
http://code.google.com/p/gitso/
http://code.google.com/p/gitso/
.
.
.
.
"Gitso is a frontend to reverse VNC connections. It is meant to be a simple two-step process that connects one person to another's screen. First, the support person offers to give support. Second, the person who needs help connects and has their screen remotely visible. Because Gitso is cross-platform (Linux, OS X and Windows) and uses a reverse VNC connection, it greatly simplifies the process of getting support. "
I'll repeat Gitso just because of how useful it is. If you just need visual, Skype's screen-sharing can be invaluable if you already use Skype to communicate.
Not too sure if you have hear of teamviewer ?
http://www.teamviewer.com/
There are clients for Windows / Linux and Mac ...
This was always a problem with "that" generation. The people in their dotage now, were the same generation that were leaving their IFF on over the whole journey to Germany and back in the early forties.
Apparently they used to think it was "lucky". (Don't ask me why. Apparently when you are stressed-out you start relying on superstition more than logic.)
Fortunately not many of them have survived to become computer users. Or if they did, they got so badly mauled in the 1990's that they gave it all up as a bad job along time ago.
If you have a server in your client network, you can test Guacamole. It's web app writen in java that you can easy install on tomcat. You can find all information in http://guac-dev.org/
You all are trying to go at this the wrong way.
You should run a 'listening server' on your end, and send them a VNC single click binary.
http://www.uvnc.com/products/uvnc-sc.html
Single click binary does need to be setup by the admin (Ultra VNC has a webpage that generates the executable, the admin can do anything from having a single entry that just connects to your IP (on the listening server) upto having pretty graphics and customized greeter screens.). Having a dns entry that always points to your domain (johnsupport.dyndns.com in the worst case for example) also makes those single click instances working for quite some time.
I'm quite surprised so little people know about SC, even though VNC is quite well known here.
And again, TeamViewer is nice (albeit closed source) one always has to wonder, why would a company give you such a service, for free. Yes, they also have commercial offerings where there bread and butter comes from I'm sure. So does google/facebook, yet we all know what they really sell.
https://www.copilot.com/
I have been using gitso for a few years now. My mom and sister have an icon called "help me" on the desktop. Thats all that is required.
You're a filthy nigger. Just shut the fuck up.
Since when has Slashdot suddenly turned into 4chan /b/ ?
I see TeamViewer mentioned a lot. Another proprietary but free as in beer alternative is CrossLoop: http://www.crossloop.com/. I have no experience with TeamViewer, but I am very happy with CrossLoop, which is also free for personal use, very easy to use (start it, and read a name and twelve digit code over the phone), automagically punches through NAT routers and firewalls, and is based on VNC under water. They don't have a native client for Linux, but the Windows version runs fine under Wine.
...would have been PERFECT, but strange things seem to have happened to this project. It may still be useful though.
It was purchased and closed sourced, but forked into a project called Adito, which was later renamed to OpenVPN SSH... but looking at this page the project seems to have since languished.
It is a web based VPN with a noob friendly "desktop" on which you can include multiple links to eg. intranet web apps and/or Java apps such as a preconfigured VNC client - it would seem easy enough to fashion a point-and-click solution for what you want to do, even if both "customer" and "support" are remote to the VPN+etc server. NOTHING needs to be installed on client machines (unless you're just using it as a vanilla VPN). It's really a shame that this project seems to have stalled... it had a "wow factor" and it was in the back of my head just waiting for a deployment opportunity.
This is an obvious opportunity for a FOSS solution, yet no one sees it. Much more fun to bicker, I guess.
Here's my method:
I put the ultravnc executable and an ini file with my encrypted password into a self-expanding zip file. The zip file also contains a batch file that expands the vnc executable on the remote machine, starts vnc, and makes a reverse connection to my machine. I used the Winzip Self Extractor to which allows a specified program, in this case the batch file that starts vnc and makes a connection to me, to run after extraction. I'm not sure but maybe that's also possible with 7-zip. Then I uploaded the self-expanding zip fle to a website. When a user needs to connect to me, I just tell them to go to the website/self-expanding zip file name.exe. The user gets a prompt asking them if they want to run or save the file. I tell them to click run. Then he gets another prompt telling him that the author of the program is unknown. I tell them to click run again. So the only thing a remote user has to do is go to a website address and click run twice and we're connected.
I'll mention this because it's what I'm doing and I haven't seen anyone else suggest it yet.
What I personally do for remote help is to use SSH with X forwarding directly, without using anything like VNC. I always set up SSH servers on non-default ports and also install fail2ban "just in case" a remote attacker actually finds the SSH servers and tries to brute-force them -- of which no attempt has ever been made so far. [And I can say that because I also set up 'logcheck', tweak logcheck to filter out noise so that it only reports actual issues, and then I actually read the resulting emails it sends.] In addition I also set up a "pre-shared" ssh key with no password and copy the key to the remote router so that the password to log into the router is not passed over the 'net, and also disable root logins. (Okay -- call me paranoid. :-P)
One place I've found with simple instructions for setting up pre-shared ssh keys:
http://rcsg-gsir.imsb-dsgi.nrc-cnrc.gc.ca/documents/internet/node31.html
And although I know I could do the same thing to log into the user's box through the router via pre-shared keys and ssh-agent forwarding:
http://unixwiz.net/techtips/ssh-agent-forwarding.html
instead I don't actually bother to do so, and just use a normal ssh password login to the user's box.
Login steps to get to user's box:
- log in via SSH to the remote router, with X fowarding
ssh -l (normal_user_username) -X -p (port) (remote_router) # ex: ssh -l mooha -X -p 1022 router.mydomain.com
- log in via SSH (as a normal user) to the user's box, with X forwarding
- su to root on user's box
- su to that user
- tell the user to quit the program they're having a problem with
- run the specific program they're having a problem with myself and have a look
Upsides:
- secure
- gives user some privacy (can't see their screen)
- never "take over" the user's mouse
Downsides:
- can't see the user's screen
- need to know the actual program name to run, rather than using the menus in the window manager
- difficult to have a look at "non-application" programs such as desktop widgets (which is usually not a problem)
VNC was fine ten years ago when nothing better was around, internet connections were slow and RDP required tons of bandwidth. But, VNC has not advanced with the times, the free version not at all. Using VNC, as I do daily, is frustrating to say the least. The Performance is slow and bandwidth utilization is relatively high in spite of the fact that color depth and resolution vaporizes in an attempt to conserve bandwidth. VNC doesn't work well, AT ALL, when UAC pops up, locking the connection which almost never fully recovers. VNC latency is high and increases, sometimes exponentially, over the course of the session.
The fact of the matter is that, compared to Join.me, LogmeIn, GoToMyPC or even RDP, VNC SUCKS ASS! Anyone that argues that point is either a lying apologist or has no experience in the other products.
In my assessment, there are only two advantages to VNC. First it is free and second it is more cross platform that most. But, VNC still sucks ass!
The poster of the Ask Slashdot is looking for that better solution. Something that works as well as these other services(much better than VNC), something that is cross platform, and something that is free. There are a few solutions out there and ironically, some of them are actually based on VNC. But, they have grown and aren't really VNC anymore and they definitely aren't free.
We, need to improve VNC or find a replacement. But, enough with the VNC adulation.
I've just discovered a product called Teamviewer and it's free. Works on Linux as well as Linux.
I admit I didn't read every last reply but have you considered uVNC single click? It comes default with an encryption plugin and you simply email the no-install exe to your relative. Or I suppose you could host it on a web site. This app ends itself once the intended helper disconnects. It solves the port problem on the customer side, is secure, and simple. The only caveat is, it's windows only.
The admin who recently left used it all the time to get to Windows servers, etc. It's a std. package under RHEL/CentOS, installable with yum.
mark
http://www.uvnc.com/products/uvnc-sc.html
I've been using this for years to support remote users..
I tend to use OpenVPN for the encryption / privacy and rdesktop to connect to Windows. I don't have to play with Macs anymore, but I used the sshd and the standard X session. It worked well enough.
Where's the Slashdot for non-noobs?
I'm getting sick and tired of all of these grade 3 computer class questions. Use google people. Do some fucking research and stop relying on us to do it for you.
I hacked up ChunkVNC and SSVNC (for Mac support) with some scripts in order to provide a remote support solution for our clients. It's smooth enough to work reasonably well about 95% of the time, failing the last for various reasons. (firewall? permissions? who knows, it's different in each situation) We have a (somewhat expensive) shared account for LogMeIn as a fallback position when the VNC solution doesn't work out.
It's a bit inelegant with respect to how it handles UAC prompts (it doesn't at all) which results in need for annoyingly common manual reconnects, and the default viewer is Windows-Only, although I hacked up ssvnc to work on Linux for my needs.
Most of the scripting is very situation-specific. I've considered offering it as a very low cost service, but there are enough issues that I haven't really wanted to bother with the tech support hassle it would cause me.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
Since your relative's most likely problem is "I can't get to my internets", any solution that involves them going to a web page or whatever is doomed to fail.
Your best bet is to get your friends and family to not think of you as tech support. /doh... (really made my life easier 8-)
The reversed (server-calls-dispay) vnc thing works well enough.
Set up a VPN host at your place and VPN clients on their machines and then just "have that on"...
You could put Xen under windows and support Windows and Linux (no joy for OSX of course).
Firewall rules to filter out brute forcers on your host (but let you have up to 5 SSH sessions from each/any one host per hour):
iptables --new-chain SSHTHROTTLE
iptables --append SSHTHROTTLE --match recent --name bad_actors --update --jump DROP
iptables --append SSHTHROTTLE --match hashlimit --hashlimit-name ssh_throttle --hashlimit-upto 5/hour --hashlimit-mode srcip --hashlimit-burst 2 --jump ACCEPT # or --jump RETURN if you have other rules to check on this link
iptables --append SSHTHROTTLE --match recent --name bad_actors --set --jump DROP
iptables --append INPUT --in-interface (external_interface) --proto tcp --match state --state NEW --dport 22 --syn --jump SSHTHROTTLE
Innocent people shouldn't be forced to pay for inferior software development.
--"Code Complete" Microsoft Press
Your assertion that the poster was looking for a "better" solution (than VNC) is false, as he didn't say that.
You don't like VNC. I get that.
Doesn't make it a bad choice just because you don't like it.
Now leaving the VNC server running bare on the internet is bad, but that was handled elsewere by talking about reversing the link direction etc. That windows UAC is crap is sad, yes. But the fact that people need to turn to their family when their household appliances fail them (and Windows is a houshold appliance at this point) is sad as well.
Innocent people shouldn't be forced to pay for inferior software development.
--"Code Complete" Microsoft Press
you may be able to get a clueless user to launch VNC server in under ten minutess of painful explanation..
but to then be able to talk a clueless user through how to enable port forwarding for port 5900 to their router IP on any given router they may happen to have.. over the phone... i have done it, but it was more than painful -- get them to find out the router ip; get them to type it into browser. pray they havent lost the posty w the router admin password.. no not the wifi password. ok, i found you a list of default router passwords.. yess hold the paperclip for 30 seconds.. login (half hour later).. okay, send me a screenshot of the router's webpage, instruct them how to do a screenshot over the phone (cmd shift 3.. no, dont hold the 3...!!).. instruct them how to attach a file to their yahoo mail.. email it to me.. half hour later.. okay, now we know what youre seeing, do blah blah blah to enable port forwarding of port 5900 to your ip, and click apply.. back to finding, downloading and installing vnc server, because youre still running osx 10.4..!?! another half hour. great.. types password, and we're in -- good, now i can install that scanner driver that was hanging on you because you tried to install the version for snow leopard.. :-%
it is truly niave to think you can talk a clueless user through setting up vnc and enabling port forwarding over the phone if you havent previously been there yourself in person to setup the session.
2cents from toronto island
jp
Now I normally don't check comment, but check out GoToAssist:
http://www.gotoassist.com
It works and is way easy for them to setup for you to have access remotely. It works through nat firewalls as well and is secure.
And it is designed for tech support as well.
If you insist on open source, it's not gonna be as easy to setup.
ChunkVNC, you can even edit the autoit scripts to your linking.
plop in the latest compiler execs from autoIT and the latest exes from the ultravnc project and it'll less likely trip up on antivirus programs. (they see something self extracting and has zero reputation, they freak out on it.
Try FreeNX / Nomachine: http://www.nomachine.com/ It's in the Debian/Ubuntu repository as well. Used/using it often to use a X display over a SSH tunnel: more secure and better performance than VNC over SSH.
forget about explaining VNC to the relative.
As stated above, you'll already be running SSHD for encryption purpose (and tunneling purposes too).
So why not also use the SSHD remote CLI capabilities and launche VNC yourself?
The only thing now is getting SSHD running:
- with suffisent login security (accepts encryption keys only, no passwords allowed), it can simply be left running.
If behind a problematic firewall, use something like autossh to have a SSH-link acting as a reverse tunnel. As long as the security is sufficient (encryptions keys, your SSH server doesn't allow much beyond reverse tunnels: no remote CLI, etc.) it will be decent too.
If the user isn't that much clueless, a link automating the tunnel setup (and optionally launching VNC) can be left in a useful place (pinned to the Windows 7 dock).
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]