Results 1 to 4 of 4

Thread: VNC not working now but SSH yes !

  1. #1
    Join Date
    Oct 2010
    Location
    Switzerland
    Beans
    12
    Distro
    Ubuntu 10.10 Maverick Meerkat

    VNC not working now but SSH yes !

    Hi again,

    This is now strange, I did a reboot and now SSH is working but no VNC





    See previous post http://ubuntuforums.org/showthread.php?t=1597764

    Thanks once more,
    Last edited by pimpys; October 16th, 2010 at 12:53 PM.

  2. #2
    Join Date
    Oct 2010
    Location
    Switzerland
    Beans
    12
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: VNC not working now but SSH yes !

    Do you have any idea why this is not working now ?
    Thanks,

  3. #3
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: VNC not working now but SSH yes !

    Are you trying to tunnel VNC over SSH, or just connect directly to the vnc server?

    Which VNC server are you using?
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

  4. #4
    Join Date
    Jul 2009
    Location
    #ubuntu
    Beans
    141
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: VNC not working now but SSH yes !

    If you are using SSH as a tunnel, do you have port forwarding set up right?

    I see you are using PuTTY to SSH. You should go to Tunnels under SSH directory thing in the left part of PuTTY's configuration, and set a port forward there.

    Source port=5900
    Destination=localhost:5900

    Then you have to tell the VNC viewer to connect to localhost::5900.

    This is assuming that your VNC server is running on the default port, and is listening to loopback requests. Also assuming that you are not running a VNC server on the machine you are VNC'ing from. Then you have to set a different source port so it won't conflict.

    If you're just trying to do plain un-tunneled VNC (unwise outside your LAN), make sure that the VNC server is not only listening to loopback. Also make sure something stupid isn't happening, like iptables rejecting the connection or possibly a firewall in Windows blocking the outgoing connection (had that happen to me more than once, lawl).

    EDITz0rz: I just looked at the other post. I've seen you're wrestled with iptables before getting SSH working. If you're wondering, ufw is a frontend for iptables. ufw being an acronym for Uncomplicated FireWall. Fun. You have to add rules to allow both 22 and 5900, of iptables will reject them.

    If you haven't already:

    sudo ufw allow 5900
    sudo ufw allow 22

    Then make sure they work by

    sudo ufw status

    BTW, I would change your SSH port to something other than 22 to reduce the hacking risk somewhat. Security through obscurity, and all that. Just choose something unused over 1023, because that's how high most port scanners/scripts go.
    Last edited by ThatBum; October 21st, 2010 at 11:00 PM.
    Poof.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •