Forum Replies Created
-
Posts
-
We have open a Trouble Report: TR04S10221 – Authentication fails in NIS environment on Fedora 33 and RHEL 8.
Please follow the link and select “notify me” at the side of the Trouble Report to receive notification of the fix.
Thanks!Please can you check this article AR11L00827 – How to connect to NoMachine when the server is behind a NAT router or a firewall.
Please can you send nsswitch.conf file to forum[at]nomachine[dot]com mentioning forum title in the subject?
The product that would fit your needs is multi node environment with the NoMachine Cloud Server + Enterpirse Desktops or other NoMachine products.
It will allow to select the machines visible to the users and allow to assign a server to every user. Please check https://knowledgebase.nomachine.com/DT11R00172#3.6.I reproduced similar problem when doing the following:
- Player maximize
- Drag taskbar to get out of maximize mode
- Use Ctrl to resize
I did not reproduce it when using the button to exit maximize mode, Can you confirm it is same for you.
It’s not quite clear what your question is but when connecting with NM you are connecting to the physical display.
You can close the session in two ways:
- Click X of the NoMachine window and you will close the session but still be logged in locally, and you can enable session lock on disconnect. You can find more information here FR05N03110 – Locking the screen automatically when the NoMachine session is disconnected – Locking the screen automatically when the NoMachine session is disconnected
- Log out from Windows and then close the session, in that case you will need to log back in.
If you are using Enterprise Desktop, you can force the system log out if this is your preference, see here for details FR08R04011 – Forcing a system logout when the user disconnects from the physical display
It looks for me from the nxserver –restart command that NoMachine does not detect physical desktop on that host. Can you tell me your OS and Desktop environment you have on that host?
Based on the command output it looks some of NoMachine service are not running. you can confirm it by running command
sudo /etc/NX/nxserver --statusTo be able to debug specific problem we would need to collect debug logs. You can enable them by:
sudo /etc/NX/nxserver --debug --enable all sudo /etc/NX/nxserver --restartReproduce the problem.
sudo /etc/NX/nxserver --debug --collect sudo /etc/NX/nxserver --debug --disable allPlease attach logs to your reply here or you can send them to forum[at]nomachine[dot]com making sure to use the topic’s title in the subject.
about authentication please can you check this article AR03S01118 – Username formats supported to log-in to NoMachine by password authentication.
I tried and feature worked correctly for me. Can you tell me what is the OS and NoMachine version you are using on client and server side.
Additionally please can you make sure that when you are using the mentioned feature that “Scale to window” is enabled in player as shown on the screenshot.
Attachments:
What I can say that currently serveradd needs to pass mentioned steps in order to add server to the CS. You can easy eliminate one by using –strict-host-key-checking no in the –server add command
/etc/NX/nxserver --serveradd newserver.domain.com --strict-host-key-checking noThere is an easy possibility that for the to automate multiple serverad using expect script.
Please check this article https://www.nomachine.com/AR04M00845.
Latency as mentioned in the article can impact responsiveness of the session. I would recommend that you try NoMachine software.
We do not reproduce similar issue.
Please collect NoMachine logs following document https://www.nomachine.com/DT11R00182.
Additionally get node.cfg file located in /usr/NX/etc and output of the following command
ls /usr/share/xsessionsCan you please send them directly to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email?
If you want to disable file transfer, you can do this by editing the cfg files as explained in that article I mentioned in my earlier reply. I don’t know what permissions your users have. If they don’t have administrator rights on the server, then they won’t be able to re-enable it.
Or you can do it in the server UI itself. Again, this depends on what permissions your users have on the server host. If the connecting user is an admin user, it’s impossible to prevent them from accessing the server preferences.
Regarding the ports, you must have port 4000 open in order to accept connections in general. If you disable it, you won’t be able to connect at all. Ports 22 are for SSH connection on Mac/Linux and 4022 on Windows.
