From: Mark Shields <laebshade@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] vnc
Date: Mon, 24 Oct 2005 11:09:27 -0400 [thread overview]
Message-ID: <642958cc0510240809m16f97569yda8fb02c8af63d93@mail.gmail.com> (raw)
In-Reply-To: <200510240846.00996.john@jolet.net>
[-- Attachment #1: Type: text/plain, Size: 1994 bytes --]
Vnc (I've only dealt with tightvnc, can't speak for others) is pretty easy
to use/start. After you've emerged tightvnc, simply type xvncserver :1
-geometry 1024x768 -depth 24 from a shell and it will setup a vnc server.
>From there you can use a vnc client to connect to the server, using this
format: <IP address of server>:1 --- the colon is important as it denoted
screen 1. Once you connect to that it will give you a vnc desktop running at
a 1024x768 resolution with a 24-bit color depth. By default, tightvnc
(Gentoo-specific?) uses twm as the window manager, but you can easily change
this to use gnome, kde, or virtually any other window manager/desktop
environment by editing ~/.vnc/xstartup
On 10/24/05, John Jolet <john@jolet.net> wrote:
>
> first make sure vnc is actually running and listening. when you start the
> server, it should tell you what address and X display offset it's using.
> Make sure with netstat -a that it really is listening there. Second, are
> you
> running iptables on that box? as a quick test, if you are, shut down
> iptables and see if you can see it.
> On Sunday 23 October 2005 18:10, Mark wrote:
> > I followed the instructions on the Gentoo wiki about configuring VNC
> > server, but I am not able to connect either inside the LAN or from the
> > outside, despite having port forwarding enabled for it on my firewall. I
> > went through the instructions twice, and everything is as listed.
> Anybody
> > know if there are some common mistakes made not mentioned in the article
> > that I might check for? Alternatively, is there a better solution for
> > remote access to my Gentoo box I should be looking at? Thanks!
> >
> > --
> > Mark
> > [unwieldy legal disclaimer would go here - feel free to type your own]
>
> --
> John Jolet
> Your On-Demand IT Department
> 512-762-0729
> www.jolet.net <http://www.jolet.net>
> john@jolet.net
> --
> gentoo-user@gentoo.org mailing list
>
>
--
- Mark Shields
[-- Attachment #2: Type: text/html, Size: 2507 bytes --]
prev parent reply other threads:[~2005-10-24 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 23:10 [gentoo-user] vnc Mark
2005-10-24 8:28 ` Nick Rout
2005-10-24 12:05 ` Digby Tarvin
2005-11-08 18:35 ` Ralf Fischer
2005-10-24 13:46 ` John Jolet
2005-10-24 15:09 ` Mark Shields [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=642958cc0510240809m16f97569yda8fb02c8af63d93@mail.gmail.com \
--to=laebshade@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox