I think when you do localhost:1 it uses the same port which is 5900. It kinda seems like it is not posible but when you think about web servers they are sending a whole bunch of info on one port.
Printable View
I think when you do localhost:1 it uses the same port which is 5900. It kinda seems like it is not posible but when you think about web servers they are sending a whole bunch of info on one port.
Running Hardy, and followed the instructions in the initial post.
Here is my issue: I am trying to VNC into my Ubuntu box at home from work, which blocks a lot of ports. But that's okay, I setup OpenSSH so that I can tunnel in. SSH tunnel works fine because I used it in some other programs successfully.
VNC server is listening on port 5900 as it should but when I try to connect I get a "server closed unexpectedly" error.
Now... I am setting this all up remotely via SSH. I was never able to test of things worked locally because X11 obviously could not display. So right now I am using PuTTY+xming to open X11 applications. Of course I do not intend to run X this way but I just wanted to see if it could connect. When I try "vncviewer localhost:0" (or if I change the listen port to 5901 like the original instructions in the main post and do localhost:1) it shows me that it connected but I get a "read: Connection reset by peer (104)" error.
Am I missing a step here?
Edit: No firewall or NAT, just a direct connection.
If you want to login to the console of the computer you have to login and then you can remote from your work place.
Update: After scouring this thread some more I changed to :02/5902 and things seem to be actually working now.
Two questions:
Is there anyway to make it restart the session automatically on reboot??
and why does nm-applet not load up / how can I make nm-applet load up automatically?
Thanks, Ant
When you are done with the session click the power button on the top right corner of the desktop. Then click log out and that’s all you need to do but if you want it to do it automatically when you shut down that is a good question.
If you go to System >>> Sessions >>> Select the Session Option tab, Check the box next to Automatically remember running applicatiopn when logging out.
For Hardy 8.04.*
VNC Speedfix reported here
http://ubuntuforums.org/showpost.php...22&postcount=5
also if your theme keeps changing when running a vnc session, on your remote machine, run
gconf-editor
and disable apps > gnome-settings-daemon > plugins > keyboard
then reboot
EDIT
Hardy is still "jaggy" with slow refresh rates compared to previous versions, even with these fixes