TightVNC problem...


Recommended Posts

Hi! Today I heard about program called TightVNC, that would make managing X programs possible. So I emerged it with gentoo`s packet manager and ran passwd and vncserver. Then the troubles started... I installed viewer program to my WinXP and tried to connect to my gentoo`s ip, "connection failed", then I tried to connect to my dns (no-ip), "connection failed", then I tried localhost both 127.0.0.1 and 192.168.x.x "connection failed"... Weird part is that, when i do: vncserver -kill 0, it says I cant kill it, and I have to kill Xvnc manualy, so i killed it, and started vncserver again with proper options (including :0), but it starts :1 insted of :0 and still I cant access, even if I connect to myip::1. Now I dont know what to try next... You guys have any idea what could be wrong, or any other program to manage my X apps...?

EDIT: Now it all works fine, thanks for your help :)

Edited by OsiXzoR
Link to comment
Share on other sites

TightVNC was a cinch to set up.

Just start over:

rm -rf ~/.vnc

vncserver :1

<type in password>

vncserver -kill :1

echo "exec gnome-session" > ~/.vnc/xstartup (If you are using GNOME. xstartup's format is the same as xinitrc, so edit it to your needs)

vncserver :1

Then on the Win comp use the VNC viewer to connect to myip:1. Port 5901+whatever window you are running it on needs to be open. (IE if you are using :1 then 5901 + 1 = 5902). It is good to start VNC on :1 because Xfree usually runs on :0, and VNC is completely independent of Xfree. If you want to forward your current Xfree desktop without running a seperate server, try gemsvnc. It is in Portage and even easier to set up. The only problem is that it is slower because it doesn't support all the compression that Tight does.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.