Bug 179379 - krdc should detect when the target host is not available
Summary: krdc should detect when the target host is not available
Status: CONFIRMED
Alias: None
Product: krdc
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-02 15:31 UTC by Dominik Stadler
Modified: 2015-12-21 02:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Stadler 2009-01-02 15:31:07 UTC
Version:           4.1.3 (using KDE 4.1.3)
Installed from:    Ubuntu Packages

My VPN connection is not very stable, it often breaks in between. Now when I try to establish a RDP connection using KRDC while the vpn connection is not actually active, KRDC does not report that the host itself is not available, but silently waits forever without any notice to the user that it can not work at all.

I understand that it is possible that things like ping do not work to the remote machine due to security reasons, but there could be an option to enable this simple check before trying to connect so that a useful error message can be printed to make the user aware that the host is not available at all.
Comment 1 Urs Wolfer 2009-01-03 12:35:40 UTC
I will try to provide more feedback when RDP fails to connect. VNC provides already such feedback.
Comment 2 Sean Pappalardo 2015-12-21 02:30:32 UTC
This is still a problem in v4.14.1 and is more frustrating after the switch to the freerdp back-end. KRDC should check the return code from the freerdp/rdesktop commands and pop up a dialog if its anything other than success.