Forum Replies Created
-
Posts
-
Yes, the “pacemaker (heartbeat)” is handled directly by nxserver. The shared IP is assigned to the host that is presently working as the master, so that the master host is working as the frontend of the cluster. In the case the master goes down (and the nxserver keeps the other host under control and checks the availability by itself), the shared IP is assigned to the slave host, so that the slave host becomes the new frontend of the cluster. The cluster product includes also load balancing functionality, but this load balancing, at the moment, is unfortunately limited, since all sessions are basically working only on the host that is master and thus only a limited set of functions can be spread across the two. This is going to change with the next version, that will be available soon, as part of an 8 update, where, after the session negotiation, connections will be “redirected” to the host that is less loaded, so providing the best load balancing. When will this be made available? W are presently working on the final tests. And this will be included in the subscription users already purchased.
To Doug, the logs of the client side do not show the issue (no correspondence to the server side logs). We need to receive the correct player side logs. What I suggest you do is make sure that “Don’t delete old log file in the player” checbox is enabled, reproduce the problem and send both server and player logs again. Thanks.
To MasterOfus, your issue seems to be a different issue which we are investigating and will come back to you soon.
Hi, in version 8 support for hardware encoding on macOS was released (for both Intel and M1). Let’s check if it is related to that, so on the Mac server please disable HW encoding: server settings -> server performance -> uncheck “Use hardware encoding”.
We would need you to enable debug, reproduce the problem and extract the logs again. The logs you attached were not complete, they did not include the node component.
Please see the instructions on how to do that: https://kb.nomachine.com/DT07S00243 and send them to forum[at]nomachine[dot]com. Use the title of this topic as the subject of your email.
It’s possible that the latest update 8.2.3 fixes the problem you have. So please try. If that doesn’t help, we would need you to enable debug, reproduce the problem and extract the logs.
Please see the instructions on how to do that: https://kb.nomachine.com/DT07S00243 and send them to forum[at]nomachine[dot]com. Use the title of this topic as the subject of your email.
Thanks!
Hi BriBri,
you can of course request an extension with the sales team if you go to the footer of this website and click Contact us -> Sales enquiries and submit your request there.
Regarding the error that you reported, we have reproduced it and would like to send you a fixed package to test. Can I assume you are using Enterprise Desktop for Windows?
So that’s certainly good news. Thanks for providing feedback and do keep us updated if things change 🙂
We will need to see logs from the affected Windows server. First enable verbose 7 in the server settings (Settings -> Server -> Server status) on the Windows 11 machine and restart the nxserver. Reproduce the problem.
Then find the \NoMachine\var folder which on Windows is generally at this path: C:\ProgramData\NoMachine\var\
and create a zip file of it.
Then find
C:\users\USERNAME\.nx
and zip up that folder as well.
Send both to us using forum[at]nomachine[dot]com. Please use the topic’s title as the subject of your email. Thanks!
Everyone encountering this behaviour please update to the latest v8.2.3 and open a new topic if necessary.
This is now closed because we got no response.
Please download the latest version (both sides) and let us know if you continue to have issues.As far as I understand, now that “NoMachine Enterprise Desktop” provides virtual desktops to also have multiple virtual monitors there.
No, Enterprise Desktop does not create multiple virtual desktops. As I wrote before, in the case of headless Linux, it can create one virtual display for you. Enterprise Desktop cannot create multiple virtual displays on Linux. To do that, you need one of the products from the NoMachine Terminal Server for Linux suite e.g Workstation. Workstation can run up to 4 individual “nomachine virtual desktops” on the same host.
That said, we have a feature planned to allow users to handle multiple monitors connected on the server as separate windows on the client side. ie. display each remote server-side monitor in a separate window.
For real physical monitors connected on the server side (which is not your case I believe), take a look at the tutorial here: https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session
Hi, thanks for taking the time to report this. Our tests also reproduced this issue and it will be fixed in the next maintenance.
Trouble Report is documented here: https://kb.nomachine.com/TR09T10609
If I understand what you mean, when the user has multiple monitors on the client, it is possible to choose if the virtual desktop (with Terminal Server products) has to be spanned on all monitors, so that the virtual desktop sees this as one giant monitor, or maximized to one of the monitors.
In the first case when you for example maximize a window, it spans on all monitors. In the second case each monitor is treated individually and maximized applications only span one monitor. You can also drag files or application windows between monitors.
To enable it:
– Open the NoMachine menu panel inside the session (ctrl+alt+0 or click on the page peel in the upper right corner of the window)
– Click on ‘Display’
– Click on ‘Resize remote display’ then on ‘Fullscreen on all monitors’To access this feature you need to have a NoMachine Terminal Server Product installed e.g NoMachine Workstation. You should first uninstall Enterprise Desktop and then proceed to install Workstation.