Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

VNC, krfb, X? Which o, what?

  • 24-04-2004 2:48pm
    #1
    Dizz
    Closed Accounts Posts: 423 ✭✭


    Right having set up a remote machine of mine the way I like it as regards console environment I was wondering what is best for remote desktoping? VNC seems perhaps slim in features (with regard to window manager) but don't quote me on that, krfb is nice if you already have KDE up and running and you logged in under your login, X (XDMCP) is a beast and on first look a nightmare to configure. Personally I'd prefer X but don't have the time. What would you recommend? Those who have a nice remote setup feel free to tell all! :p

    Cheers

    Dizz

    (I'm assuming a secure setup up here - either ssh port redirects or stunnel wrapping)


Comments

  • #2
    Zaltais
    Closed Accounts Posts: 304 ✭✭Zaltais


    Can't beat full on X forwarding.

    Personaly I found it trickier to set up secure VNC than secure X forwarding, and it's not that hard at all.

    I use Cygwin to forward a Linux box to my windows desktop in work.

    It really eats the bandwidth though so I wouldn't recommend it over a dialup ;)


  • #3
    tomk
    Registered Users, Registered Users 2 Posts: 1,067 ✭✭✭tomk


    I don't use anything except SSH for remote access - as Zaltais says, anything graphical is heavy on bandwidth. Anything I need to do remotely can be done from the CLI - your requirements (and bandwidth) may differ, of course.


  • #4
    Red Alert
    Hosted Moderators Posts: 7,486 ✭✭✭Red Alert


    I use KDE via VNC, you do need to modify the default VNC startup script to do this, although it's very easy. I can send it to you if you like.


  • #5
    Dizz
    Closed Accounts Posts: 423 ✭✭Dizz


    Fire it my way Red Alert! :) (dump it into a pm)

    Cheers

    Dizz


  • #6
    Dizz
    Closed Accounts Posts: 423 ✭✭Dizz


    S'ok red alert got it sorted - cheers :)

    Dizz


  • Advertisement
  • #7
    niallb
    Registered Users, Registered Users 2 Posts: 2,755 ✭✭✭niallb


    This works reasonably well over dialup (ISDN anyway!) so long as the other end has a reasonable connection.
    It's about as compressed as you can go while still comfortably using a remote browser on the other end.
    It expects the VNC password saved in the file
    /home/user/.vnc/passwords/targetmachine
    and a working ssh connection to the gateway machine at the target network.
    By this I just mean that ssh user@gateway.targetnetwork.tld gives you a prompt.
    ip.as.seen.by.gateway is simply the target machine's IP address on the internal network as visible from the gateway. The :0 may be a different display number, the vnc server will tell you.
    With public keys, this is a one click desktop.
    You can just run it without the password bits and type them in every time, but that's less fun...
    To start the VNC environment, you may just have to run vncserver on the other end.
    If Xvnc is installed, it should set everything up.
    Try a lighter window manager than KDE though!

    #!/bin/sh
    vncviewer -via user@gateway.targetnetwork.tld -bgr233 -nocursorshape -compresslevel 7 -quality 3 -encodings "copyrect tight" -passwd /home/user/.vnc/passwords/targetmachine -fullscreen ip.as.seen.by.gateway:0

    NiallB


Advertisement