Mailinglist Archive: opensuse (3232 mails)

< Previous Next >
Re: [SLE] tightvnc and suse
  • From: Peter Sutter <sutterp@xxxxxxxxxxxx>
  • Date: Tue, 1 Aug 2006 14:31:57 +0000 (UTC)
  • Message-id: <200608012231.27674.sutterp@xxxxxxxxxxxx>
host> vncviewer ipaddress

This defaults to display 0 on port 5900 which refers to the display you are
(normally) logged in (your current X session). i.e. you connect to the
currently logged-in users desktop. This implies that vncserver is running on
the remote host, i.e. somebody is logged in on the remote host and he has
remote access enabled.

You may also run a vncserver explicitly as a service (most likely under
xinetd) on the remote host, in which case the call is:

host> vncviewer ipaddress:display
or
host> vncviewer::port

both methods will then present you with the login screen where you have to
login with username and password and start your own X session, independently
of the user ogged on on screen 0

Peter

On Monday 31 July 2006 20:26, Silviu Marin-Caea wrote:
> On Monday 31 July 2006 15:07, Richard Bown wrote:
> > Hi
> > I've been using tightvnc on Mandrake for a long time, its very easy to
> > use on that distro, click on the icon from the apps menus and enter the
> > remote address and display number, then off it goes.
> >
> > Seems to be a little different on suse
>
> It's the same on SUSE.
>
> KDE Lauch, System, Remote Access, Krdc
>
> Enter the address like this:
> vnc://remote_computer_name_or_IP

< Previous Next >
Follow Ups