fra81

[fra81]

Update on the disconnection problem:

What the logs show is the expected behaviour. The user connected to the server is not the same user logging in remotely (“root” vs “rbt”). You can either use the same user or set the PhysicalDesktopAuthorization configuration key to 0 in the /usr/NX/etc/server.cfg file. This will allow the connection even if the owner of the desktop is not the same as the connecting user.

[fra81]

Can I assume that the version you tried years ago was the NX 3 free version? In this case, note that NX 3 supported virtual desktop sessions also in the free version, while the free version of NoMachine 4 only allows to attach to the physical display, so it wouldn’t be exactly the same way.

As for the reported problem, logs are still under investigation.

Regards

[fra81]

Hi claus,

the desktop environment in use remotely doesn’t make any difference generally. What can make a difference would be the used protocol, specifically the “lightweight” protocol. I assume you are using the NoMachine free version to connect to the physical display of your remote machine. The lightweight protocol is available in a virtual desktop session or in rootless custom session (with the latter you can forward a single application instead of the full desktop, which is what you may want). To enable those types of session you need one of the Terminal Server products: https://www.nomachine.com/terminal-server. They are available for evaluation.

More info on the lightweight protocol here: https://www.nomachine.com/AR02L00779.

As for the problem you are reporting, we would like to see the logs. You can gather them by following the instructions here: https://www.nomachine.com/AR07K00677. You can attach them here or send to forum[at]nomachine[dot]com.

[fra81]

Hi thomasneh,

1) Please send us a complete set of logs that you can gather by following the instructions in https://www.nomachine.com/AR07K00677. If you prefer, you can email them to forum[at]nomachine[dot]com.
Furthermore, we would like to see a screenshot of the Display settings tab, the one shown at paragraph 5.6 of this guide: https://www.nomachine.com/DT10K00060.

2) Is it the local or the remote host to turn black? Logs of point above can be useful here too.

3) We checked the ffmpeg package of the link in option 2. This pre-built avcodec has also a dependency to swresample-1.dll. So what you need to do is just copy swresample-1.dll to C:\Program Files (x86)\NoMachine\bin and it should work.
You could also use the ffmpeg package we provide here: http://www.nomachine.com/opensource.
Instructions for compiling are here: http://www.nomachine.com/AR09K00690.

4) That warning is not critical and it won’t prevent the software from working correctly. Anyway it will be fixed in the next update.

[fra81]

So what could be causing the

Error: No nodes available for user’s profile’.

That problem seems due to a wrongly formatted key in the cfg file:

Error: Parse error at display option h264,mjpeg,clipboard.

Consider that no change is required in the configuration in order to get H.264 working. If you leave the defaults, H.264 will be automatically used when available.

Anyway, if I understand, you are now able to connect. So please send us a new set of logs when the session is running, as per instructions in my post above. We need client and server side logs.

[fra81]

This looks like a configuration problem on your server. NoMachine will only be able to set a resolution among the supported ones. If you are not able to set the given resolution even with the system xrandr command, NoMachine won’t be able to set it as well.

You may try with the following command:

xrandr –output Virtual1 –mode 1600×1200

You may also check what resolutions are visible in the system settings menu, and if it is possible to set the wanted resolution there.

[fra81]

Hi vstubbs.

Have you downloaded the libx264 sources from our web site and followed the instructions in https://www.nomachine.com/AR10K00695? As exaplained in the article, the libx264 library with our modification is required.

Have you enabled the codec also on client side as explained in https://www.nomachine.com/AR10K00696?

If you followed all the steps and H.264 is still not used, please send us the logs for further investigation. You can find instructions in https://www.nomachine.com/AR07K00677. You can attach them here or email to forum[at]nomachine[dot]com.

[fra81]

Hi Steve,

here are a couple of examples of graphics card models that have been widely tested in our labs: NVIDIA Quadro K600, AMD Radeon HD6570.

Anyway, it would be useful to know what kind of problems you are experiencing, as we can’t be sure they are due to the graphics card.

[fra81]

We’ve been trying to get NoMachine 4.3.30 working with Gnome 3, but no luck.  A physical server connection works somewhat, except that there’s a blue flashing sort of artifact that completely destroys usability.  As the mouse is moved around on the screen and different UI elements gain focus, large parts of the screen will turn blue or black.  Seems to be some sort of colormap or layering issue?

Is that a virtual machine? If so, what virtualization software are you using?
If it is not a virtual machine, what is your graphics card? Did you install proprietary drivers?

A virtual server connection does not have this problem, but it’s very slow.  If one right clicks on the desktop background, it takes many seconds before the background menu is displayed.  Completely unusable.  As a wild guess, maybe Gnome 3′s GPU operations are being emulated slowly in software instead?

Please find the relevant info here: https://www.nomachine.com/AR12L00831.

[fra81]

Can you tell us more about the versions of your operating systems and of the NoMachine software installed on client and server side?

If you are running the last NoMachine version and still reproduce the issue, please gather a complete set of logs as explained in https://www.nomachine.com/AR07K00677. If you prefer, you can send logs to forum[at]nomachine[dot]co.

[fra81]

Hi tommas,

so the relevant logs were probably cleaned up. At this point we would need a new set of logs after setting the ‘SessionLogClean 0’ key to the node.cfg file. Detailed instructions on how to gather a complete set of logs can be found here: https://www.nomachine.com/AR07K00677.

Anyway, before proceeding with new logs, I would recommend to upgrade to the new 4.4.1 version, that contains fixes to several problems, also affecting the Windows server.

[fra81]

Hi tommas,

thanks for the logs. The issue seems due to a failure in creating a session directory in the user’s home on server side (specifically C:\Users\Tommas\.nx\M-Tommas-13001-E98BCB8378573FEFB167B44F544BCD44). To investigate further, we would also need the content of the ‘C:\Users\Tommas\.nx’ directory from the Windows server.

[fra81]

Hi.

There is a issue affecting mac servers tracked in https://www.nomachine.com/TR11L04663. This should be the problem reported by the original poster. A fix will be made available in the upcoming software update.

The problem on the linux server could be different. Does it occur only with Chrome or with any application?

[fra81]

Hi.

As for the the problem with autorepeat, it looks like the issue in https://www.nomachine.com/TR10L04603. It should be already fixed in the last version.

Regarding the first problem, what is the resolution on your client machine? Logs could be useful to understand what’s going on. You can find instructions for gathering a complete set of logs in https://www.nomachine.com/AR07K00677 (you can send them to forum[at]nomachine[dot]com, if you prefer), but for a start client side logs could be enough. Please also check if you have a .config/monitors.xml file in the user’s home on the server, and what resolution is specified there.

[fra81]

Hi andrea,

the original problem looks like a problem with video drivers.

May I assume you are using NoMachine free on server side and you are connecting to the physical desktop of that machine?

Can you check the CPU usage on server side and tell us what processes, if any, consume most of it?

Logs could also be useful. You can find instructions for retrieving them in https://www.nomachine.com/AR07K00677. You can attach logs here or send to forum[at]nomachine[dot]com.

Another possibility could be bad network conditions. You could try to lower the Display quality using the slider in the Display settings tab and check if this alleviates the problem in any way.

[Author]

Posts