Date: Mon, 10 Sep 2007 18:21:58 -0400 (EDT) From: doug <doug@fledge.watson.org> To: Pollywog <lists-fbsd@shadypond.com> Cc: freebsd-questions@freebsd.org Subject: Re: Sadly, my tinker-time has run out.... Message-ID: <20070910181001.R5423@fledge.watson.org> In-Reply-To: <200709030021.30393.lists-fbsd@shadypond.com> References: <200709020222.21000.mchauber@gmx.net> <200709021356.23513.mchauber@gmx.net> <d356c5630709021637g46c823b5lf3a980b12e91688@mail.gmail.com> <200709030021.30393.lists-fbsd@shadypond.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 3 Sep 2007, Pollywog wrote: > On Sunday 02 September 2007 23:37:49 Andrew Gould wrote: > >> >> Don't feel guilty. Keep a FreeBSD server running at home while you travel! >> You can backup your data securely and use it remotely via tightvnc. >> >> Andrew > > There must be some trick to accessing a FreeBSD server via VNC. > I have done it on Linux but I could not get it to work in FreeBSD. I am using tightvnc-1.2.9_1 on FreeBSD and the windows versions of tightvnc on win2k and windows XP Pro. On FreeBSD I only have used vncviewer running the server on the winders boxes. I am using FreeBSD 6.2. The only issue I had was the screen quality with XP Pro which went away with the latest version of the tightvnc windows software. On Mac OS/X I am running Vine VNC from Redstone Software. The thing that I have not tried is going from windows/mac to FreeBSD, using ssh for that. Is that the issue for you?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070910181001.R5423>