arg!!! what the hell.. there is a bunch of porn on that page!!!Rosjahh wrote:Another good article on connecting to you vncserver (even when it's behind a router) from windows with ssh tunneling:
[url]http://
EDIT: Removed URL. --pjp
arg!!! what the hell.. there is a bunch of porn on that page!!!Rosjahh wrote:Another good article on connecting to you vncserver (even when it's behind a router) from windows with ssh tunneling:
[url]http://


Sweet! Thanks for the tip.outspoken wrote:arg!!! what the hell.. there is a bunch of porn on that page!!!Rosjahh wrote:Another good article on connecting to you vncserver (even when it's behind a router) from windows with ssh tunneling:
[url]http://[/url]

Code: Select all
Apr 28 12:19:57 [xinetd] Protocol tcp_ not in /etc/protocols [file=/etc/xinetd.d/xvncserver] [line=3]
Apr 28 12:19:57 [xinetd] Error parsing attribute protocol - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=3]
Apr 28 12:19:57 [xinetd] Bad socket type: stream_ [file=/etc/xinetd.d/xvncserver] [line=4]
Apr 28 12:19:57 [xinetd] Error parsing attribute socket_type - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=4]
Apr 28 12:19:57 [xinetd] Bad value for wait: no_ [file=/etc/xinetd.d/xvncserver] [line=5]
Apr 28 12:19:57 [xinetd] Error parsing attribute wait - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=5]
Apr 28 12:19:57 [xinetd] Unknown user: nobody_ [file=/etc/xinetd.d/xvncserver] [line=6]
Apr 28 12:19:57 [xinetd] Error parsing attribute user - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=6]
Apr 28 12:19:57 [xinetd] Server /usr/bin/Xvnc_ is not executable [file=/etc/xinetd.d/xvncserver] [line=7]
Apr 28 12:19:57 [xinetd] Error parsing attribute server - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=7]
Apr 28 12:19:57 [xinetd] Protocol tcp_ not in /etc/protocols [file=/etc/xinetd.d/xvncserver] [line=13]
Apr 28 12:19:57 [xinetd] Error parsing attribute protocol - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=13]
Apr 28 12:19:57 [xinetd] Bad socket type: stream_ [file=/etc/xinetd.d/xvncserver] [line=14]
Apr 28 12:19:57 [xinetd] Error parsing attribute socket_type - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=14]
Apr 28 12:19:57 [xinetd] Bad value for wait: no_ [file=/etc/xinetd.d/xvncserver] [line=15]
Apr 28 12:19:57 [xinetd] Error parsing attribute wait - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=15]
Apr 28 12:19:57 [xinetd] Unknown user: nobody_ [file=/etc/xinetd.d/xvncserver] [line=16]
Apr 28 12:19:57 [xinetd] Error parsing attribute user - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=16]
Apr 28 12:19:57 [xinetd] Server /usr/bin/Xvnc_ is not executable [file=/etc/xinetd.d/xvncserver] [line=17]
Apr 28 12:19:57 [xinetd] Error parsing attribute server - DISABLING SERVICE [file=/etc/xinetd.d/xvncserver] [line=17]
...

Code: Select all
$ Xvnc :1 -desktop 800x600 -depth 16
Code: Select all
service vnc-800x600x32
{
protocol = tcp
socket_type = stream
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -geometry 1024x768 -depth 16 -fp unix/:-1
}
So, make sure you have [b]font-server[/b] in your USE flags and re-merge xorg-x11. That should take care of the problem.

Code: Select all
vncviewer: VNC server closed connection My problem is now solved. It had noting to do with the configuration or anything. The problem was that my xinetd and vnc packages was compiled with -march=pentium4, when -march=pentium3 is the correct for my computer. I think vnc simply didn't work correctly. (I've had illegal instruction errors from various applications)Any ideas what might cause this:When trying to connect from my Windows machine (which is the purpose of this for me) I get an "The connection closed unexpectedly" error.Code: Select all
htpc@HTPC htpc $ vncviewer localhost:71 VNC viewer version 3.3.7 - built Jun 23 2005 18:25:08 Copyright (C) 2002-2003 RealVNC Ltd. Copyright (C) 1994-2000 AT&T Laboratories Cambridge. See http://www.realvnc.com for information on VNC. ReadFromRFBServer: rdr::EndOfStream
Are there any logs I should check for better error descriptions?
I obvously have read in this thread, and rechecked every step of the HOWTO, but it still doesn work.
Any help very appreciated.
Login to the machine remotely. Run vncserver. Look at the screen number you get assigned. Connect to that screen number on the remote host. For example, if you are assigned :2, connect to remotecomputer:2. If you are running over ssh, then you might want to specify the display number on the command line of vncserver.mahir wrote:can SOMEBODY help me
with this persistant connectino thing!
somebody told me to try freenx, cos it supports it
but the problem is
i'm going to have to install the client on machines
and I AM NOT ALLOWED TO INSTALL ANYTHING ON THE MACHINES
apart from the server (dont ask, 2 sister companies, 1 wanker of a boss) anyway...
so i need to have accesss to a SCREEN via the JAVA class/jar thing u get on the windows version.
how do i doooooooo that?
and 2ndly,
i neeeeed to make the connections persissssssstanttttttt!
help me plzzzz

AnimeUnrivaled wrote:Well, I've followed the steps exactly as indicated (did have to do a "locate kdmrc" to find its actual location), and I've read every single response in this thread. I've searched as much as possible across the internet only to find that I can't solve my prblem. No, I'm not having the grey screen problem. I'm not that lucky. Each time I do attempt to connect via vncviewer, I get:
That's all.Code: Select all
vncviewer: VNC server closed connection
xinetd is loaded correctly, the ports are being listened on correctly, and I can't figure out what's wrong. If I start a vncserver manually as a user, I can connect to it no problem. This message reminds me of an error that I will rarely come up against while running a RealVNC server on Windows XP. Occasionally the server will still be running but will simply "close" the connection immediately upon connecting from elsewhere. A quick restart of the Windows system fixes the problem. It seems to occur at random, but only if I've been connected several times during the current boot (It never happens the first or second time I connect after a reboot). I don't care about fixing the Windows thing, but I wanted to put that out there for reference.
So, the problem is that Xvnc seems to be running, but it is closing connections immediately (ie, never actually letting me do anything at all).
Any help would be appreciated.
Code: Select all
tail -f /var/log/everything/current
Code: Select all
Error: Can't open display:I verified this bug on :newtonian wrote:Hi-
I followed this tutorial and got everything to work fine.
The users that use the vnc terminal system primarily use eclipse.
There is a bug in vnc versions before 4.0-5 that causes the vncserver
to crash when used with eclipse. Details at :
from https://bugzilla.redhat.com/bugzilla/sh ... ?id=127134
Any tips on how to install VNC server 4.1.1?
Is it just a matter of umerging vnc, downloading the source from realvnc and running the install script?
Do you think the RealVNC 4.0-r1 ebuild is newer than 4.0-5?
Cheers,
Code: Select all
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
startkde &
Code: Select all
New 'X' desktop is linux:2
Code: Select all
vncserver localhost:2