Reverse ssh tunnel error

[rob]

I’m trying to connect through a reverse ssh tunnel as per https://www.nomachine.com/AR01N00870 but get an error in the client:

Could not connect to the server.

Error is 111: Connection refused

In my case Host A & B are the same machine.

I can connect to this server from a different machine on the same LAN as the server. The server log after the failed connection contains:

2017-09-05 11:20:04 678.838 2341 NXSERVER checkLocalSession: cookie for session on display ‘0’ found WMRunning set to ‘1’.
2017-09-05 11:20:04 678.937 2341 NXSERVER checkLocalSession: found seat ‘seat0’.
2017-09-05 11:20:04 679.035 2341 NXSERVER checkLocalSession: session kind ‘session’ detected.
2017-09-05 11:20:04 679.130 2341 NXSERVER checkLocalSession: session type by WMRunning is ‘desktop’.
2017-09-05 11:20:04 679.210 2341 NXSERVER checkLocalSession: session type by systemd ‘user’.
2017-09-05 11:20:04 679.297 2341 NXSERVER checkLocalSession: type ‘desktop’ confirmed by systemd session database.
2017-09-05 11:20:04 679.372 2341 NXSERVER checkLocalSession: session type ‘desktop’ detected.
2017-09-05 11:20:04 679.455 2341 NXSERVER checkLocalSession: checking is session ‘0’ active.
2017-09-05 11:20:04 679.529 2341 NXSERVER checkLocalSession: active session found.
2017-09-05 11:20:04 679.604 2341 NXSERVER checkLocalSession: handling sessions. Display manager is ‘Simple Desktop Display Manager’.
2017-09-05 11:20:04 679.875 2341 NXSERVER Checking local session with line: NX> 153 6904:user1:0:opensuse+leap+42.2:desktop:session:19919:%%2frun%%2fsddm%%2f%%7b2141701a-f8c7-4e7f-8978-c16b7d346906%%7d:*****:1:seat0:empty .
2017-09-05 11:20:04 680.068 2341 NXSERVER Checking local X server for pid: 19919.
2017-09-05 11:20:04 680.154 2341 NXSERVER Session 17B9DBF2CF1C91C85CC2CFE10EA80CF1 associated with pid 19919 is already known.
2017-09-05 11:20:04 680.232 2341 NXSERVER Found node assigned to session: 17B9DBF2CF1C91C85CC2CFE10EA80CF1.
2017-09-05 11:20:04 680.322 2341 NXSERVER Node stdin: FD#13, stdout: FD#14, socket FD#13.
2017-09-05 11:20:04 680.401 2341 NXSERVER Session 17B9DBF2CF1C91C85CC2CFE10EA80CF1 associated with pid 19919 is already running.
2017-09-05 11:20:04 680.656 2341 NXSERVER NXCluster: Feature disabled.
2017-09-05 11:20:04 680.790 2341 NXSERVER Setting new read timeout to 30000

nomachine 5.3.10-6.x86_64; opensuse 42.2; physical display; i3 window manager (same on both machines)

[Britgirl]

There’s not enough information to be able to say what’s going wrong. Debug logs will be more helpful. Please use the following article for instructions on how to enable them for your OS. Then send them to forum[at]nomachine[dot]com making sure you reference your topic.

https://www.nomachine.com/DT07M00098

[rob]

Sorry, there was a mistake in the client port number which I discovered in the client log.  Why doesn’t the client error say “No server at this host/port”? “Connection refused” is misleading.

[Tor]

Hi Rob.

We’re reporting the error of the OS networking layer. Those errors are very common and users are usually aware of what they mean. We’ve often considered the idea to print user friendly errors, but some of them, like those related to networking, can have a so wide set of reasons that we could give a misleading information, ending by causing more troubles instead of helping to solve them.

We’ll make sure to update our Knowledge Base to explain the error and offer some hints for the troubleshooting.

[Author]

Posts