Bug 8209 - Difficult to discover NAT connection problems
Summary: Difficult to discover NAT connection problems
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Bugzilla mail exporter
Depends on:
Reported: 2023-08-23 13:50 CEST by Pierre Ossman
Modified: 2023-08-29 13:10 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2023-08-23 13:50:38 CEST
A common issue is that users fail to configure the ThinLinc setup properly for a NAT environment (mostly forgetting agent_hostname). Unfortunately, it is not terribly obvious that this is the issue if you aren't experienced with those types of issues.

The client could probably report things in a better way, where it might be more obvious what is going on. E.g.:

 * Clearly specify what address it tried to talk to

 * Suggest that NAT might be an issue

 * Detect that the agent address is a RFC1918 address and complain a bit extra
Comment 1 Pierre Ossman cendio 2023-08-23 13:51:30 CEST
A related issue is also that the client will generally lock up whilst waiting for a timeout for the unreachable NAT address. We have bug 1197 for this.

Note You need to log in before you can comment on or make changes to this bug.