Britgirl

[Britgirl]

This is a duplicate of https://forum.nomachine.com/topic/error-is-108-connection-reset-by-peer-5.

[Britgirl]

Hi,

please confirm:

– you can connect from Win 10 to Win 11, there are no problems

– the problem is that you cannot the other way round, ie. you cannot connect from Win 11 to Win 10

– you have disabled HW encoding on the Win 11 server

[Britgirl]

Ah so Dell m1330 has a 32-bit architecture! The general rule is that when HW architecture is 32-bit, you need to install NoMachine 32-bit packages. You cannot install 64-bit packages (including NoMachine) on 32-bit architecture.

Instead, NoMachine 32-bit packages can be installed on a 64-bit OS or 64-bit architecture provided you have the necessary 32-bit compatibility layer in place.

Good to know it’s now working 🙂

[Britgirl]

Hi, thanks for confirming that, we had to make sure that it was indeed NX and not SSH in the Edit connection panel. Connecting over NX with key-based authentication to a Free Edition server is supported.

There are some instructions here:

How to set up key based authentication with NX protocol
https://kb.nomachine.com/AR02L00785

[Britgirl]

Thanks for confirming. Developers have already found the cause and implemented a patch. The fix will be released in the next software update.

[Britgirl]

Please check the following Trouble Report. Your issue looks very similar to that.

High CPU usage when installing NoMachine v8.15 on Ubuntu
https://kb.nomachine.com/TR01W11263

As a temporary workaround, execute in a local terminal:

sudo /etc/NX/nxserver --eglcapture no

Restart the desktop manager or logout from the desktop and login again.

[Britgirl]

Yes, ECS (Enterprise Cloud Server) supports multi-homing, allowing it to connect to more than one network. By default, ECS listens on all available network interfaces (as do all other NoMachine server products). This makes it inherently capable of handling connections from multiple networks without requiring additional configuration. Of course, you can limit it to listen to specific interfaces if you want.That’s done using the NXdListenAddress key in the server.cfg.

[Britgirl]

Can you send us the logs from that Ubuntu machine? Compress the archive of the .nx directory in the user’s home and send to us at forum[at]nomachine[dot]com.

[Britgirl]

Can you submit a screenshot of the Edit connection panel, Address section?  Or tell us the details that are configured therein, we’d like to know what protocol is set in that panel.

[Britgirl]

Based on what you’ve told us, that updating to Plasma 6.2.5 eliminates the problem, the test library we sent you should be uninstalled, and we consider the issue solved. Update to NoMachine 8.15, if the problem comes back, we can investigate further.

[Britgirl]

There are multiple errors in the install log, and we are unfortunately unable to reproduce the problem with the Trend Micro products we have installed in our lab. Could you tell us the exact product and version you are using from Trend Micro? If we can reproduce it, we can report this false positive to them.

[Britgirl]

In the ‘Edit connection’ panel are you changing the protocol to SSH?

[Britgirl]

Hi, with the release of NoMachine 9, it will change to what you are asking 🙂 So, the order of the window title will be: , – NoMachine.

[Britgirl]

Hmm, strange.

Please tell us:

– NoMachine product and version on the client device you are connecting from.
– OS version on that device/computer.
– NoMachine free edition version on the computer you are connecting to.
– OS version on that computer. If it’s Linux please clarify the distribution and version.
– the exact steps you are taking to connect using a NoMachine SSH session.

Thanks.

[Britgirl]

Hi, thanks for reporting. There is a fix for this in the 8.15.3 software update.

https://kb.nomachine.com/TR01W11254

[Author]

Posts