A timeout error occurred while attempting to connect to … on port 4000

[nx4fun]

Hello NoMachine Development Team,

Misleading error message:

A timeout error occurred while attempting to connect to “192.168.1.250” on port “4000”. The problem could have been caused by a network issue, a firewall or NAT blocking incoming traffic, or an incorrect server address. Please check your configuration and try again.

The real cause is user inactivity for a period longer than the timeout (approx. 180 seconds).

How to reproduce the error:

1. Start NoMachine Player (==> the login window with “Username” and “Password” appears).
2. Wait approx. 180 seconds without doing anything.
3. Enter the username and password.
4. Click “OK” (==> the above message appears).
5. Click the “Try again” button.
6. Re-enter the username and password and click “OK” (the connection is established without any problems).

I suspect that the real reason for this is that the timeout timer starts running when the application is launched. I don’t see any advantage in this design.

I have used the current NoMachine Player on Windows for connections to Debian. However, I suspect that the problem exists on all platforms.

Best regards,

nx4fun

[Britgirl]

The error message is printed when the POSIX error is a timeout. The reason why the error is received could be wrong, but our tests on the fly didn’t reproduce a similar issue. Can you send us the logs from both client and server machines? You can extract them from the UI using the instructions here: https://kb.nomachine.com/DT08U00298

Send them to forum[at]nomachine[dot]com or attach them here. Please use the title of this topic as the subject of your email. Thanks!

[Author]

Posts