Re: [SLE] KDE Remote Desktop (VNC) troubles - SOLVED
I managed to solve that problem and here is a procedure for anyone with similar troubles: - ssh to a remote server as root - with yast install x11vnc - man x11vnc to learn how to use it - login as an user who is logged on KDE (su <username> ) - x11vnc -display :0 - see on which port x11vnc is listening (5900, 5901?) - on local machine run: vncviewer <server-address>::<port> example: vncviewer my.server.org::5901 Voila, you have again access to your server's screen. Thanks very much to Michael and others for help! Janko Michael Letourneau wrote:
Michael Letourneau wrote:
[snip]
I will definitively upgrade to a newest SuSE as soon as possible but now a have this server on a remote location, running GUI server app, so it would be very nice to restart that VNC somehow remotelly and without rebooting a whole server.
Some silly thinking: what about killing only that socket? Or maybe starting a krfb on different port?
I found that it would not go away because of the crashhandler function, and the parent of that I believe was kded, so unless you wanted to possibly mess up the desktop you were stuck. I found no option to starting krfb on a different port, otherwise I would have tried that, as it seemed to be faster than x11vnc. But, I have had good luck with x11vnc, and I can just ssh in and start it up when I need to, then when I exit it goes away. Or if you desire you can leave it running. Nice thing about it is that it will startup on another port if the default is busy.
Michael
-- Janko Mivšek Svetovalec za informatiko EraNova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
On Tuesday 07 November 2006 17:15, Janko Mivšek wrote:
I managed to solve that problem and here is a procedure for anyone with similar troubles:
- ssh to a remote server as root - with yast install x11vnc - man x11vnc to learn how to use it - login as an user who is logged on KDE (su <username> ) - x11vnc -display :0 - see on which port x11vnc is listening (5900, 5901?) - on local machine run: vncviewer <server-address>::<port> example: vncviewer my.server.org::5901
Voila, you have again access to your server's screen.
Thanks very much to Michael and others for help!
Janko
And thank *you* for a great little summary! This is a perfect example of how effective this list can be. regards, Carl
Carl thank you for your thank! I always feel obliged to contribute at the end of such problem resolution with a summary, because this is some kind of reward for all contributors to the solution, in the form which will be helpful to someone other too. Best regards Janko Carl Hartung wrote:
On Tuesday 07 November 2006 17:15, Janko Mivšek wrote:
I managed to solve that problem and here is a procedure for anyone with similar troubles:
- ssh to a remote server as root - with yast install x11vnc - man x11vnc to learn how to use it - login as an user who is logged on KDE (su <username> ) - x11vnc -display :0 - see on which port x11vnc is listening (5900, 5901?) - on local machine run: vncviewer <server-address>::<port> example: vncviewer my.server.org::5901
Voila, you have again access to your server's screen.
Thanks very much to Michael and others for help!
Janko
And thank *you* for a great little summary! This is a perfect example of how effective this list can be.
regards,
Carl
-- Janko Mivšek Svetovalec za informatiko EraNova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
On Tuesday 07 November 2006 17:15, Janko Mivšek wrote:
I managed to solve that problem and here is a procedure for anyone with similar troubles:
- ssh to a remote server as root
Addendum, for all: I've disabled remote root logins and restricted it to protocol 2 (ssh2).... I can't test this from here, so I need to ask if this 'throws a wrench' in Janko's nicely summarized procedure? Thanks! Carl
you can tunnel vnc through ssh with vncviewer -via sshmachineexternalip user@vncserverlocaladdress(192.x.) B-) On Tuesday 07 November 2006 3:30 pm, Carl Hartung wrote:
On Tuesday 07 November 2006 17:15, Janko Mivšek wrote:
I managed to solve that problem and here is a procedure for anyone with similar troubles:
- ssh to a remote server as root
Addendum, for all: I've disabled remote root logins and restricted it to protocol 2 (ssh2).... I can't test this from here, so I need to ask if this 'throws a wrench' in Janko's nicely summarized procedure?
Thanks!
Carl
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Carl Hartung wrote:
On Tuesday 07 November 2006 17:15, Janko Mivšek wrote:
- ssh to a remote server as root
Addendum, for all: I've disabled remote root logins and restricted it to protocol 2 (ssh2).... I can't test this from here, so I need to ask if this 'throws a wrench' in Janko's nicely summarized procedure?
No, you just login as a user, then su to root. I have also done as you (restricted root login, only protocol 2, as well as only keys allowed and a different port), and this works fine, and could accomplish Janko's solution. HTH -- Joe Morris Registered Linux user 231871
On Tuesday 07 November 2006 17:45, Joe Morris (NTM) wrote:
Carl Hartung wrote:
On Tuesday 07 November 2006 17:15, Janko Mivšek wrote:
- ssh to a remote server as root
Addendum, for all: I've disabled remote root logins and restricted it to protocol 2 (ssh2).... I can't test this from here, so I need to ask if this 'throws a wrench' in Janko's nicely summarized procedure?
No, you just login as a user, then su to root. I have also done as you (restricted root login, only protocol 2, as well as only keys allowed and a different port), and this works fine, and could accomplish Janko's solution. HTH
Thanks Joe! Carl
participants (4)
-
Brad Bourn -
Carl Hartung -
Janko Mivšek -
Joe Morris (NTM)