[olug] looking for an application

[Ryan O'Rourke]

On Fri, 2003-02-28 at 04:08, William E. Kempf wrote:
> 
> 2) As others have pointed out, another solution (and the better one, IMHO)
> is to use VNC.  The TightVNC package is quite nice, and I think Cygwin
> installs it? (Been a while since I had to set that up.)  To use VNC you'll
> need it installed on both the Windows box (for the client) and the Linux
> box (for the server).  Usage is really easy, but I'm going to tell you to
> RTFM (http://www.tightvnc.com/ and http://www.tightvnc.com/docs.html).
 
There's no need to install Cygwin to use TightVNC on Windows. TightVNC
has it's own client and server packages for Windows as well as Linux.
Just install the correct packages on the clients and servers.

> 3) I've been creating a document on how to configure Cygwin to work
> "nicely".  I'll share this with the community when I'm done.

Thank you! It's been a couple years since I've used Cygwin, but from
what I remember both the configuration and installation procedure were a
bit tricky.

> I used to use VNC a lot, but I find most of what I need/want to do now is
> done on the console, so I just use ssh.  Much faster, and easier to deal
> with.  If you do use VNC, I'd suggest tunnelling it under ssh for
> security.

I use TightVNC all the time for work related activities. It works
securely across the VPN without having to tunnel, which makes things a
bit easier if you are using a combination of OS's. 
We also use it across a frame-relay connection for troubleshooting
remote clients. We have RedHat in the office, they have Windows
remotely. We simply fire up a TightVNC session for their machine and
take over their desktop.
My former roommate always used VNC at home. He'd boot his laptop to
Windows and then use VNC to connect to a Linux box on the LAN. That way
he could always have a Linux desktop and a Windows desktop running at
the same time.

-- Ryan