Forum Replies Created
-
Posts
-
Hi,
In a corporate environment, where the company is requesting the use of NoMachine software to its users, that would be considered commercial use. So a better fit would be the NoMachine Enterprise Desktop to access the Ubuntu desktops which reside in the office (or wherever it is they are).
I would also recommend it because you have direct access to the support team which would be able to help you with exploring possible options on how to pre-configure the settings for your specific environment and usage (whether that could be via script of some sort or other solution could be explored with them), and of course for any other problems or questions.
Some additional information about what defines personal and commercial use is available here: https://www.nomachine.com/AR03P00972 You can compare Enterprise Desktop and free NoMachine package here: https://www.nomachine.com/remote-access-for-your-needs. From what you write I understand you’ve got quite a few users, so packs of 10 subscriptions seem like the best option. If you contact our sales team, they will be able to answer any commercial-related questions (and also pre-sales support) further.
As a client-side software, your users can use NoMachine free on the personal Macs or, if they only require the connection GUI and they don’t want to enable access to the Macs, Enterprise Client is available.
We dug deeper in to the problem because, actually, things were not fully clear. Maybe we’ve found a bug with the nVidia hardware encoder that causes post-processing to be applied when it shouldn’t. We’ve sent you an email with instructions to confirm the problem.
@enverex and @martinidry, check your inboxes. I’ve just sent you both an email with instructions to help us find what’s causing the weird behaviour.
Hi sdcinvan, when deciding default settings we have to consider a number of criteria, such as who is using the software and what they are using it for 🙂
So changing the default server settings for one group of users would upset a load of other users, and vice-versa, such as users who are engaging in remote collaboration vs. those who are using it for unattended access. Your question, though, has given us food for thought, and we’ll definitely be looking in to ways to how we can handle better such situations.
You published this in the Linux category. I’m not sure how you are using the software and how the software is being installed (by you or directly by the users you mention). If your users are all using Linux on the server, and you’re concerned they’ll forget to blank the monitor when accessing their desktop or skip your advice on how to best configure their computers for unattended access, could the terminal server family be more appropriate, such as Workstation?
Did you follow the instructions in the Getting Started Guide? See Fig. 13:
https://www.nomachine.com/getting-started-with-nomachineYou need to put the hostname in the first field (‘host’), and then in the second field (‘port’) put the port number you have mentioned in your example (25520).
Did you take the IP address and port number from the Welcome panel on the host you want to access as you can see in Fig. 10?
The player logs are actually missing from the logs you sent us.
Did you check “Don’t delete log files on exit” in the UI? Is it possible for us to receive them? Ideally, you would need to submit those and the server-side logs again from the same session.
From the server-side logs you sent we see you are connecting from Mac to a NoMachine virtual desktop on Ubuntu. Please confirm that this is your scenario.
Provided you are trying to run a virtual desktop session, try running it with X11 Vector Graphics enabled and disabled and see if there’s a difference. You can also try to connect to physical session – does the problem still happen? More about this is here:
https://www.nomachine.com/AR02L00779
https://www.nomachine.com/DT10O00153You also state that the client closes. Are you able to try connecting from another client machine and see if the problem persists (a different OS)?
So that other readers can see the related topic, here’s the link: https://forums.nomachine.com/topic/black-screen-oops-rendering-issues-on-red-hat.
Hi dc2008, there’s a Trouble Report here: https://www.nomachine.com/TR05P08581
You can sign up to receive a notification from us by clicking “notify me” 🙂
Hi Howard in Florida 🙂
thanks for your starting comment, that’s what we like to hear!
Bionic Beaver is supported, we added support for Ubuntu 18.04 in the last release, 6.2.4. This is what you need to update to. The workaround that you mentioned from the other forum topic shouldn’t be necessary. Remember that on 18.04, Ubuntu switched back to X.org, so Wayland is optional now, not the default display.
Once you’re running Bionic Beaver, update NoMachine to 6.2.4.
If you do want to use Wayland, you’d better take a look at our notes here:
Notes for connections to Linux physical desktops running Wayland
https://www.nomachine.com/AR02P00969As for that version 4 client on Windows you are using, I would strongly recommend you bring that up-to-date to the latest version as well. Why it’s failing to update to v5 is hard to say without seeing the error message you get and install logs which you have, you could attach them here. Was that using the manual install procedure or automatic update from the GUI? Did you try uninstalling and reinstalling?
Removing v4 completely and installing v6 from our website would be the sensible thing to do, i) because version 4 is no longer supported ii) a number of issues have been fixed since that version.
Let us know how you get on!
Have you see this?
Guidelines for sizing a NoMachine infrastructure and benchmark tests for v. 6
https://www.nomachine.com/AR02P00966