Results 1 to 6 of 6

Thread: Remote access with SSH/TightVNC failed with new Kali 2.0

  1. #1
    Junior Member
    Join Date
    Aug 2015
    Posts
    1

    Remote access with SSH/TightVNC failed with new Kali 2.0

    Hello,

    I have a problem since the new Kali 2.0 with getting access to an installed TightVNC Server.
    It seems to crash Gnome?

    Description of working steps until Kali 1.1.0
    # Connect to Kali with SSH
    # Install TightVNC
    sudo apt-get install tightvncserver
    # Run VNC Server only localhost on Kali
    sudo tightvncserver -localhost
    # Set password before for remote access
    # Tunnel a ThightVNC viewer over SSH to Kali and open i.e. 127.0.0.1:5901
    It worked perfect until Kali 1.1.0 to get a "X Windows" which really helps sometimes for remote access.

    If I am doing the same steps on Kali 2.0 and connect with the TightVNC viewer
    I get a password prompt and then the TightVNC viewer opens with an error message
    > Oh no! Something has gone wrong.

    I have no idea why and how I can fix it.
    Maybe a setting in /etc/init.d/gdm3 ?

    I would really appreciate every help
    or for an other solution to get access to the X.

    Kind regards,
    Sabi

  2. #2
    Junior Member
    Join Date
    Sep 2015
    Posts
    1
    Same issue here - are we the only two running into this problem or the only two using vnc to get to a kali host?

  3. #3
    Junior Member
    Join Date
    Jun 2014
    Posts
    3
    Same issue here, has anyone got vnc working?

  4. #4
    Junior Member
    Join Date
    Nov 2015
    Location
    Germany
    Posts
    1
    Quote Originally Posted by JKAD View Post
    Same issue here, has anyone got vnc working?
    I have, but it involves installing the MATE desktop environment, which is a GNOME 2 fork.

    First, you have to install MATE:

    Code:
    $ sudo apt-get install mate-core mate-desktop-environment-extra mate-desktop-environment-extras mate-themes
    Then, you have to change a line in the ~/.vnc/xstartup, replacing

    Code:
    /etc/X11/Xsession
    with

    Code:
    /usr/bin/mate-session
    It is just a workaround, as MATE offers a different look and feel than GNOME.

    The underlying problems with GNOME and VNC (and RDP, NX, ...) are described here:

    https://bugs.debian.org/cgi-bin/bugr...cgi?bug=776746
    https://bugs.launchpad.net/ubuntu/+s...n/+bug/1251281

    and it looks like a fix for Debian will take some time...

  5. #5
    Junior Member
    Join Date
    Nov 2015
    Posts
    4
    great thanks the workaround is great

  6. #6
    Junior Member
    Join Date
    May 2014
    Posts
    13
    ok just a thought guys but i recently found that mikogo works well with kali gnome - the interesting thing is mikogo seems to be based on vnc protocols so the million dollar question is why does mikogo vnc work but sana/debian does not ??

Tags for this Thread

Posting Permissions

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