Forum Replies Created
-
Posts
-
From the excerpts you sent it seems that you some old files in the install directory. Uninstall, remove any traces of the installation directory completely and install again.
Reporting on behalf of the NNois:
You saysWhat do you mean with ‘physical display session’? In your previous post you were saying that the option solved the problem when connecting to the Physical display.
I have two types of nodes where i’m connecting, ones with no displays attached so NoMachine create one, the other (the majority) are one with a physical display attached where I need to connect.At first I thought the switch DisplayServerExtraOptions “-nodamage” soled the problem but I was connecting on a node where there was no physical display.The problem explained:As soon as I use the switch “no damage” on nodes with a physical display, I’m not able to connect to it, with the error <No available sessions on this server>on the client. If I disable the option, that’s workingIn a next message, as I have time to help you to track this I’ll send you my logs files.Can you tell us the exact Linux distribution you are using both sides and the products you have installed?
As the message suggests, USB devices are not supported with the version you are using. You should consider updating your remote server software to the latest version (5). File transfer can be executed either by sharing a device (folder, usb etc) or directly via the Monitor (!M icon). See here for more details:
https://www.nomachine.com/sharing-files-between-computers
If you need some tips setting up file-sharing for the legacy 3.5.0 software, I suggest you contact the team via the website (Contact us -> General Enquiries). The forums are dedicated entirely to the latest NoMachine software (version 5 or version 4).
Hi, we’ve sent you a debug package to allow us to extract more details about what could be provoking this issue. Please check your email and the instructions within.
A Trouble Report has been opened and you are invited to sign up to the ‘notify me’ tool in order to receive notification of when a patch has been released. This thread will eventually be closed.
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.