Results 1 to 9 of 9

Thread: RPI3 and VNC Connect / server

  1. #1
    Junior Member
    Join Date
    Apr 2017
    Posts
    7

    RPI3 and VNC Connect / server

    Is there any way to get VNC Connect / Server working as it does on other distros and OS's on Kali? I have multiple Raspberry Pi's running different OS's and none of them have an issue with VNC Server. All of them have no issue, auto starts on boot, logs into my account without issue and overall works as it should. When i install VNC connect on Kali, VNC viewer works fine (which is useless to me), but, VNC server does not even show as an available application. Any work around for this? I am just looking for a simple straight forward way to remotely connect to my Kali PI, suggestions would be appreciated. Just wanting VNC to work as it does on Raspbian in Kali....

  2. #2
    Senior Member
    Join Date
    Nov 2015
    Location
    Australia
    Posts
    118
    tightvnc is the vnc server of choice for kali but if you prefer VNC Connect, you can install it like this:

    wget https://www.realvnc.com/download/fil...ARM-DEB.tar.gz
    tar -xvf VNC-6.0.2-pi-refresh2-Linux-ARM-DEB.tar.gz
    dpkg -i VNC-Server-6.0.2-Linux-ARM.deb
    systemctl enable vncserver-x11-serviced && systemctl start vncserver-x11-serviced

    Fire up X Window on your Pi, goto the VNC status menu and enter your license information.

    That's it.
    ----------------------------------------
    Check out "Sticky Fingers Kali-Pi":
    https://whitedome.com.au/kali-pi

    Now with mana-toolkit and more goodies!

  3. #3
    Junior Member
    Join Date
    Apr 2017
    Posts
    7
    Quote Originally Posted by re4son View Post
    tightvnc is the vnc server of choice for kali but if you prefer VNC Connect, you can install it like this:

    wget https://www.realvnc.com/download/fil...ARM-DEB.tar.gz
    tar -xvf VNC-6.0.2-pi-refresh2-Linux-ARM-DEB.tar.gz
    dpkg -i VNC-Server-6.0.2-Linux-ARM.deb
    systemctl enable vncserver-x11-serviced && systemctl start vncserver-x11-serviced

    Fire up X Window on your Pi, goto the VNC status menu and enter your license information.

    That's it.
    What do you mean by "Fire up X Window on your Pi"?

  4. #4
    Senior Member
    Join Date
    Nov 2015
    Location
    Australia
    Posts
    118
    Quote Originally Posted by oneDARtech View Post
    What do you mean by "Fire up X Window on your Pi"?
    That was a bit old school, sorry.
    I mean boot into GUI or type startx.
    ----------------------------------------
    Check out "Sticky Fingers Kali-Pi":
    https://whitedome.com.au/kali-pi

    Now with mana-toolkit and more goodies!

  5. #5
    Junior Member
    Join Date
    Apr 2017
    Posts
    7
    Quote Originally Posted by re4son View Post
    That was a bit old school, sorry.
    I mean boot into GUI or type startx.

    Got it! Can't tell you how much i appreciate your input on this, been trying for days to get this set up.

    How can I set up VNC server to autostart on boot?

  6. #6
    Senior Member
    Join Date
    Nov 2015
    Location
    Australia
    Posts
    118
    Did you end up using Tight(or Tiger)VNC? If so you can do this:

    Code:
    sudo wget -O /lib/systemd/system/vncserver@.service https://github.com/Re4son/vncservice/raw/master/vncserver@.service
    sudo systemctl enable vncserver@1.service && sudo systemctl start vncserver@1.service
    This will start the vnc service as root - you can change that by editing /lib/systemd/system/vncserver@.service
    Last edited by re4son; 2017-04-10 at 06:05 AM.
    ----------------------------------------
    Check out "Sticky Fingers Kali-Pi":
    https://whitedome.com.au/kali-pi

    Now with mana-toolkit and more goodies!

  7. #7
    Junior Member
    Join Date
    Apr 2017
    Posts
    7
    Once again thanks, I'm almost there! Last thing I need to do is enable autologin. I've already tried editing the /etc/gdm3/daemon.conf file, but, that did not work...

  8. #8
    Junior Member
    Join Date
    Aug 2017
    Posts
    6
    @re4son followed your instructions and here's what I got:

    Code:
    root@kali:~/Documents# dpkg -i VNC-Server-6.2.0-Linux-ARM.deb
    (Reading database ... 110930 files and directories currently installed.)
    Preparing to unpack VNC-Server-6.2.0-Linux-ARM.deb ...
    Unpacking realvnc-vnc-server (6.2.0.29523) over (6.2.0.29523) ...
    Setting up realvnc-vnc-server (6.2.0.29523) ...
    Updating /etc/pam.d/vncserver
    Updating /etc/pam.conf... done
    Looking for font path... not found.
    /usr/bin/vncserver-x11: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
    /usr/bin/vncserver-x11: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory
    Installed systemd unit for VNC Server in Service Mode daemon
    Start or stop the service with:
      systemctl (start|stop) vncserver-x11-serviced.service
    Mark or unmark the service to be started at boot time with:
      systemctl (enable|disable) vncserver-x11-serviced.service
    
    Installed systemd unit for VNC Server in Virtual Mode daemon
    Start or stop the service with:
      systemctl (start|stop) vncserver-virtuald.service
    Mark or unmark the service to be started at boot time with:
      systemctl (enable|disable) vncserver-virtuald.service
    
    Processing triggers for desktop-file-utils (0.23-2) ...
    Processing triggers for mime-support (3.60) ...
    Processing triggers for man-db (2.7.6.1-2) ...
    Processing triggers for shared-mime-info (1.8-1) ...
    Processing triggers for hicolor-icon-theme (0.15-1) ...
    root@kali:~/Documents# VNC-Server-6.2.0-Linux-ARM.debcd
    -bash: VNC-Server-6.2.0-Linux-ARM.debcd: command not found
    root@kali:~/Documents# systemctl enable vncserver-x11-serviced && systemctl start vncserver-x11-serviced
    root@kali:~/Documents# root@kali:~/Documents# startx
    
    
    X.Org X Server 1.19.3
    Release Date: 2017-03-15
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.16.0-4-armmp-lpae armv7l Debian
    Current Operating System: Linux kali 4.4.50-v7 #1 SMP Fri Apr 21 01:18:29 CDT 2017 armv7l
    Kernel command line: bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2709.boardrev=0xa01041 bcm2709.serial=0xc6d066f2 bcm2709.uart_clock=48000000 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=B8:27:EB:D0:66:F2 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.fiq_fix_enable=2 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0
    Build Date: 07 July 2017  08:55:08AM
    xorg-server 2:1.19.3-2 (https://www.debian.org/support) 
    Current version of pixman: 0.34.0
    	Before reporting problems, check http://wiki.x.org
    	to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    	(++) from command line, (!!) notice, (II) informational,
    	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.1.log", Time: Tue Aug 29 06:20:36 2017
    (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    xinit: connection to X server lost
    
    waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
    Any thoughts on what's going on with those libraries?

  9. #9
    Senior Member
    Join Date
    Nov 2015
    Location
    Australia
    Posts
    118
    libbcm_host.so should be in "/opt/vc/lib/". Anything there?

    Did you install the Re4son-Kernel? It contains this library.
    ----------------------------------------
    Check out "Sticky Fingers Kali-Pi":
    https://whitedome.com.au/kali-pi

    Now with mana-toolkit and more goodies!

Posting Permissions

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