Link to home
Start Free TrialLog in
Avatar of Mark
Mark

asked on

How to select and set up VNC on Ubuntu

I want to set up VNC (or whatever) on my office workstation so I can connect from home. I've been to https://help.ubuntu.com/community/VNC/Servers and askubuntu and find a bewildering selection of VNC server some of which can start at boot, other require user login first, some require passwords, etc. Doing `apt-cache search vnc` lists 84 different VNC packages or related tools. There's also an x11rdp that suppose to work like Windows RDC, but that development is several years old, so maybe not a good choice. I find "krdc - Remote Desktop Connection client" in my `apt-cache` list. Is that something interesting? Here's what I'd like if it exists:

I'd like to be able to remotely connect to my running desktop session, or to get a new login prompt if there is not active session. I do not want to first have to ssh into the workstation and run something (vncclient?)

Help me sort through the pile!
Avatar of Dan Craciun
Dan Craciun
Flag of Romania image

Avatar of Mark
Mark

ASKER

Dan Craciun: Thanks! I'll check that out. Interestingly, teamviewer wasn't on any Ubuntu list I checked. Wonder why?

Other Experts, other suggestions?
Teamviewer runs pretty much on anything. Their professional version is expensive, so they make sure you can access/support anything from anywhere.
Avatar of Mark

ASKER

OK, I'll give it a shot and post back results. The problem is, I want to use this in our office, so I think we'd need to buy the commercial version.
Avatar of Mark

ASKER

more info ... OK, I installed Teamviewer on Ubuntu and Windows 7. I'll have to say, installation was dead simple. I've connected from my Windows computer to the Ubuntu computer.

Issues/questions:

To start, I have to run teamviewer from a terminal on the Ubuntu. This gives me a session ID and password. What I want is to always have teamviewer in "server" mode, not necessarily associated with a session. Ideally, if there is a running session my remote would connect to that. Otherwise, I want to see a login screen. I do not want the user to have to run teamviewer from a terminal session. For one thing, I don't want my users launching terminals. For another, the user would have to anticipate needing his/her computer remotely and remember to run teamviewer before he/she left the office. Also, if the office workstation happened to reboot (power loss ...) that would be the end of the user being able to get in.

Can teamviewer always be in "server" mode?

When I connected from my Windows workstations, I had to simply enter the session ID and password. I suppose that's fine if the target computer is on the LAN, but what if I'm trying to connect to my office? I don't see anywhere to enter an IP address.

When the teamviewer image of the remote desktop comes up on my Windows computer it is maybe 80% of the size of my Windows screen. Is that adjustable? Yes, I clicked full-screen mode.
SOLUTION
Avatar of Dan Craciun
Dan Craciun
Flag of Romania image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Mark

ASKER

Dan Cracium:
There is no Teamviewer host for Linux.
Actually, yes there is: https://www.teamviewer.com/en/download/linux.aspx, but no matter, you are right, it doesn't suit my needs.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Mark

ASKER

Latest bit. I've found ssvnc: http://www.karlrunge.com/x11vnc/ssvnc.html, which creates an ssl tunnel from Windows to x11vnc on the Ubuntu host. No-brainer to configure, just run the ssvnc.exe. This works just fine except that the version of TightVNC viewer that ships with ssvnc 1.0.[29|30] is 1.3.9 which is older and much slower than the version 2.7.10 I downloaded earlier. My solution was to copy the 2.7.10 executable into the ..\ssvnc\Windows\util folder and rename it to the same as the 1.3.9 version. Odd that such an old version of TIghtVNC viewer is shipped with ssvnc (the 2.7.10 itself is from 2013).

I think this issue is resolved!
Avatar of Mark

ASKER

I researched the solution.

Thanks to Dan Craciun for being the lone participant in this question