KDE Remote Desktop (VNC) troubles
Hello all, I'm repeating this question and I'd really appreciate any help. I cannot connect to a remote server via KDE Remote Desktop Connection anymore. When trying, I got an error: Connection failed, server does not accept new connections On a server there is: - no krfb processes - netstat -anp | grep 590 returns: tcp 0 0 :::5900 :::* LISTEN 2030/kdeinit: kded therefore someone is waiting for connection - this is SuSE 9.0 Is there a way to restart KDE's VNC on this server without restarting KDE completely? Thanks for any hint and best regards Janko
Hello all,
I'm repeating this question and I'd really appreciate any help.
I cannot connect to a remote server via KDE Remote Desktop Connection anymore. When trying, I got an error:
Connection failed, server does not accept new connections
On a server there is: - no krfb processes - netstat -anp | grep 590 returns: tcp 0 0 :::5900 :::* LISTEN 2030/kdeinit: kded therefore someone is waiting for connection - this is SuSE 9.0
Is there a way to restart KDE's VNC on this server without restarting KDE completely?
When I have tried to use the integrated vnc daemon in KDE I have had similar issues. When it would crash their would be a crash screen on the desktop but it would hold the port open, and there would still be a process. So essentially you were locked out. I tried disabling the integration, and tried manually running krfb, there is an option for no crash handler. Which had random luck. I found more consistent, albeit slower results using x11vnc, after upgrading to xorg 7, I found I had to run it with some switches to get it to actually play nice. Hope that is somewhat helpful. Michael
Thanks for any hint and best regards Janko
-- 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
Problems with routers? B-) On Tuesday 07 November 2006 11:28 am, Janko Mivšek wrote:
Hello all,
I'm repeating this question and I'd really appreciate any help.
I cannot connect to a remote server via KDE Remote Desktop Connection anymore. When trying, I got an error:
Connection failed, server does not accept new connections
On a server there is: - no krfb processes - netstat -anp | grep 590 returns: tcp 0 0 :::5900 :::* LISTEN 2030/kdeinit: kded therefore someone is waiting for connection - this is SuSE 9.0
Is there a way to restart KDE's VNC on this server without restarting KDE completely?
Thanks for any hint and best regards Janko
-- 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
On 11/7/06, Janko Mivšek wrote:
Hello all,
I'm repeating this question and I'd really appreciate any help.
I cannot connect to a remote server via KDE Remote Desktop Connection anymore. When trying, I got an error:
Connection failed, server does not accept new connections
On a server there is: - no krfb processes - netstat -anp | grep 590 returns: tcp 0 0 :::5900 :::* LISTEN 2030/kdeinit: kded therefore someone is waiting for connection - this is SuSE 9.0
Router/firewall problems? Are you sure the port is correctly forwarded?
Is there a way to restart KDE's VNC on this server without restarting KDE completely?
Try to enable/disable it in Control Center. Cheers -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap.
Hi Brad and Svetoslav Sunny wrote:
On 11/7/06, Janko Mivšek wrote:
Router/firewall problems? Are you sure the port is correctly forwarded?
Hardly, because it worked no long ago without problems. Also it is not a first time I have this problem.
Is there a way to restart KDE's VNC on this server without restarting KDE completely?
Try to enable/disable it in Control Center.
I can't because this is a remote server and I need to travel there or reboot it. Janko
On 11/7/06, Janko Mivšek wrote:
Is there a way to restart KDE's VNC on this server without restarting KDE completely?
Try to enable/disable it in Control Center.
I can't because this is a remote server and I need to travel there or reboot it.
Janko
How do you access it? Using ssh tunnel? If so, forward the X server (ssh -Y) when you login. Then start the Control Center from a commandline. It will open it on your local machine, using your local X server. -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap.
Sunny wrote:
On 11/7/06, Janko Mivšek wrote:
Is there a way to restart KDE's VNC on this server without restarting KDE completely?
Try to enable/disable it in Control Center.
I can't because this is a remote server and I need to travel there or reboot it.
Janko
How do you access it? Using ssh tunnel? If so, forward the X server (ssh -Y) when you login. Then start the Control Center from a commandline. It will open it on your local machine, using your local X server.
This classical solution can be interesting to try but so far a solution with x11vnc seems much easier to run. Thanks Svetoslav for help! Janko
Janko Mivšek wrote:
Sunny wrote:
On 11/7/06, Janko Mivšek wrote:
Is there a way to restart KDE's VNC on this server without restarting KDE completely?
Try to enable/disable it in Control Center.
I can't because this is a remote server and I need to travel there or reboot it.
Janko
How do you access it? Using ssh tunnel? If so, forward the X server (ssh -Y) when you login. Then start the Control Center from a commandline. It will open it on your local machine, using your local X server.
This classical solution can be interesting to try but so far a solution with x11vnc seems much easier to run. Thanks Svetoslav for help!
Janko
"...a solution with x11vnc seems much easier to run." Easier than what? ssh is very easy to run. I know your message is old, but that comment of yours has me wondering if you've ever even tried using ssh before? If not, you really should familiarize yourself with ssh, as it's a great tool for doing remote work and administering servers remotely. Besides using ssh for remote scripting, installing production apps, and testing end-user scenarios, it's also good for transferring files back and forth using scp thru the ssh tunnel (which by the very nature of ssh, the files are encrypted by the protocol before they're sent over the connection). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Brad Bourn -
Janko Mivs(ek -
Janko Mivšek
-
penguin_powered -
Sunny