Forum Replies Created
-
Posts
-
A look at the logs indicates that this is not the same problem. It looks like a server problem. I suggest you open a new topic with the details so we keep investigations separate. We’ll most likely need logs, but they must be full set of logs from the affected Mac, along with the crash report (those logs that you sent us indicate the path where the crash report is located).
Instructions for debug logs are here: https://www.nomachine.com/DT07M00098
First, please submit a new topic.
Are they trying to share the physical display of the virtual host (VM) or are they sharing the desktop which is running in a virtual NoMachine session? NoMachine provides custom scripts, see here for more details: https://www.nomachine.com/DT07M00090#9
There are no further comments awaiting moderation from you. I double checked to make sure. That last one in the thread was from Kroy (above) and now the new one from you today.
we could not reproduce this issue with our environment, so we need to know if you have any customized settings in your environment or are using the standard one?
Please send us these files:
/etc/pam.d/su
/etc/pam.d/nx
/etc/pam.d/centrifydc
/etc/pam.d/centrifypamHave you perhaps made some changes in the default Centrify configuration?
Can you submit everything to forum[at]nomachine[dot]com? The output of ‘ls -ltr /usr/NX/ /etc/NX/ /var/NX/’ would also be helpful.
Also, it would be very useful if you could enable logs as per the instructions suggested by Hawk above.
We’re going to send you a debug package because we need further information.
This package will produce additional nxlsa logs in ‘C:\tmp’ (you need to create this directory). Send us the NoMachine logs including content of ‘C:\tmp’ after reproducing the problem like you did before.
@norbert, send them to forum[at]nomachine[dot]com. Thanks.
I think you are referring to this https://www.nomachine.com/FR12K02799
I can’t say as yet when it will be available, but it has been added to the roadmap of version 5.
This could well be an error from something different. We would need to see the logs from nxerrors which is here: /Library/Application Support/NoMachine/var/log/. Can you send them to forum[at]nomachine[dot]com or attach them here if they are not too big.
I will close this forum post now. Users can follow the link to the Trouble Report and use the ‘notify me’ feature to know when a patch has been released. https://www.nomachine.com/TR01N06360
This thread will now be closed. You can sign up to receive notification about when the patch is available.
You will need NoMachine or Enterprise Client installed on the computer you are connecting from, and then to get to the server, yes, you will need to install a NoMachine server. See here for more details: https://www.nomachine.com/getting-started-with-nomachine
Choices of server are: the free version or one of the products from the enterprise-oriented range. Note that installing NoMachine on your Dell server will get you access to the physical desktop. If you would like to be able to run multiple Linux desktops (in your case, CentOS), then you will need a NoMachine server with the terminal server functionality: Workstation, Terminal Server, Enterprise Server or Cloud Server. What you download and try depends on your specific needs.
Hi, we’re able to reproduce this and have opened a Trouble Report so that you can track it. Check the Notify me box, https://www.nomachine.com/TR03N06589, so you can receive an alert when a fix is available.