Forum Replies Created
-
AuthorPosts
-
August 1, 2018 at 16:11 in reply to: H.264 and "Disable multi-pass encoding" – does it work together? #19208
Britgirl
Keymaster@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.
Britgirl
KeymasterHi 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?
Britgirl
KeymasterDid 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?
Britgirl
KeymasterThe 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)?
Britgirl
KeymasterSo 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.
July 30, 2018 at 15:03 in reply to: Frozen virtual desktop when WebRTC is enabled in WebPlayer #19179Britgirl
KeymasterHi 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” 🙂
July 27, 2018 at 10:31 in reply to: Ubuntu 18.04, Wayland, and older versions of NM for client #19164Britgirl
KeymasterHi 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!
July 26, 2018 at 08:51 in reply to: Guidance for node server requirements – remote Linux applications #19145Britgirl
KeymasterHave you see this?
Guidelines for sizing a NoMachine infrastructure and benchmark tests for v. 6
https://www.nomachine.com/AR02P00966Britgirl
KeymasterCan you try reducing the size of the image and reattaching those screenshots? Alternatively, send them to forum[at]nomachine[dot]com. Thanks!
Britgirl
KeymasterI forgot to mention the link to the feature request of the NoMachine Network service
https://www.nomachine.com/FR07J02731
You can sign up to receive a notification once it’s released 🙂
Britgirl
KeymasterYou must know your account credentials on the remote computer in order to get access to it. The username and password is obligatory.
Did you follow the steps in the Getting Started Guide on our website?
https://www.nomachine.com/getting-started-with-nomachineI thought I was supposed to create an account on the website before installing the software?
Creating an account on our website is not available as a service, this will be possible when we release NoMachine Network in the near future. The username and password is of the remote computer (in your appartment) that you want to connect to.
You can find more info about what you need here:
What do I need in order to use NoMachine?
https://www.nomachine.com/AR10K00723Britgirl
KeymasterThe nxservice.log is missing from the received logs, I’m not sure why.
From the logs you submitted we can see there are some issues with access rights issue related to log dir like:
Cannot change access rights: C:\NoMachine\logs\nxserver.log to Read-Write. Error is 2, No such file or directory.
Could it be that you changed the NoMachine log path some time and therefore you don’t have the correct permissions in place?
– Remove old installation of NoMachine
– Reboot Windows
– Install NoMachine again with default install and log location
– Reboot machineBritgirl
Keymaster@Zhiliang, if you’ve kept your NoMachine software up-to-date using automatic updates or manual installation, you should also be on 5.3.25 on the server. Or, are you referring to the update of your system OS?
Britgirl
KeymasterHi, very strange. Let’s start by seeing only the Player logs from the connecting client. Maybe that will shed some light.
Britgirl
KeymasterNoMachine shortcuts are handled in the Player GUI.
By default it’s set to Ctrl-Alt-T.
You can change this if you prefer a different combination.
See Fig 3 in the document here: https://www.nomachine.com/DT10O00154#2.1 for more details.
-
AuthorPosts