Forum Replies Created
You should run this command on the server as well. The output should be similar. Did you make some changes in configuration files? According to the logs, some device features are disabled. Make sure that those files are edited correctly or try to move back to the default values. The file connected to the disk is placed in %InstallDir%/etc/node.cfg. If this problem is still present, please send us Windows Event logs after repeating the problem (instruction how to collect them are below). NoMachine installation logs will be also helpful. You may find them in “C:\Users\<username>\AppData\Local\Temp” saved as “Setup Log <date>.txt”.
1. Export Event Viewer logs:
– Open Control Panel -> System and Security -> Administrative Tools -> Event Viewer
– To export events, select the type of logs you want to export, click on Action menu and pick Save All Events As.
We’re interested in ‘Windows Logs/System’, ‘Windows Logs/Application’ and ‘Application and Services Logs/Hardware Events’ logs.
According to logs, there is a problem with performing a disk mount operation directly by our driver. This is why I asked about output. In this case, it looks like driver is available for the system. We got this information from line: ‘Received output from the nxfs: ‘DEBUG: DokanMain failed.’. Still, we’re not able to reproduce your problem.
To solve your problem make sure that nxnode is added to Accessibility card in Security & Privacy (see attachment). Audio output on the server should be set to NoMachine Audio Adapter. On the client side you should choose device that you want to use (headphones \ Bluetooth device \ speakers).
If the solution above doesn’t work, try to uncheck nxnode app – reboot machine – check nxnode again. If this also did not help, you can add whole NoMachine application to Accessibility.
Let us know if you have further problems.
Logs we’ve received from you, helped us to locate the problem, but still we don’t know the exact reason and were not able to reproduce this situation. Can you tell something more about Noah software and also about Noah Device Server? What this server does? How do you create it?
Can you check if disk driver is mounted properly? You can do this by opening CMD and running:
driverquery /nh | find "nxfs"
Output should look like this:
nxfs NoMachine FileSystem A File System "date"
Thanks for logs and for help.
More detailed information how to gather logs you can find here:
under ‘Gather server side logs on Windows’. Please send files to this email address:
forum at nomachine dot com
To resolve this problem we would need more information.
Can you send us server’s logs after failed mapping? You can find them under this path:
What is the type of disk forwarding (Private/Public)?
Can you tell us what happens if you change the name of mount point? You may do this in the editable field described as Export as when choosing Public or Private mapping type. By default, it’s C.
Is the directory then created? If yes, what are its permissions? Is it empty? If yes, try to remove it then forward disk again.
This situation is related to crash of PulseAudio that has been caused by unloading of some modules manually. For example unloading of module-suspend-on-idle. These causes NoMachine to lose sink and sources.
If this situation happened and you’re not able to use microphone properly try to kill PulseAudio
pulseaudio -kthat will restore automatically and then restart NoMachine’s server
/usr/NX/bin/nxserver --restartwhich will recreate new sinks and sources.
Probably you have some problems with permissions. First of all you should check permissions of /Library/Application\ Support/NoMachine/Extensions by:
ls -l /Library/Application\ Support/NoMachine/
the result should be as follows:
drwxr-xr-x 9 root admin 288 Oct 31 14:26 Extensions.
If your result is different, then set permissions with:
sudo chown root:admin /Library/Application\ Support/NoMachine/Extension
sudo chmod 755 /Library/Application\ Support/NoMachine/Extension
Then check permissions of /Library/StagedExtensions/Library/Application\ Support/NoMachine/Extensions.
ls -laO /Library/StagedExtensions/Library/Application\ Support/NoMachine/
your result should looks like this:
drwxr-xr-x 4 root wheel restricted 128 Nov 5 17:26 Extensions
Make sure that you have restricted flag set. If not, then set it. The same for nxfs.kext inside this directory.
ls -laO /Library/StagedExtensions/Library/Application\ Support/NoMachine/Extensions
drwxr-xr-x 3 root wheel restricted 96 Dec 21 2016 nxfs.kext
Then try to test the feature.
If this doesn’t solve the problem, you should check if it is possible to remove the directory /Library/StagedExtensions/Library/Application\ Support/NoMachine or just file /Library/StagedExtensions/Library/Application\ Support/NoMachine/nxfs.kext.
sudo kextutil -t /Library/Application\ Support/NoMachine/Extensions/nxfs.kext
should create the directory and the file automatically with proper permissions.
One more thing, you should make sure that your SIP has been enabled. You can do this with command
Please send us installation/update logs.
I hope that this helps to solve your problem.
Did sinks and sources disappear when NoMachine audio features were turned on? Did you switch their state a few times before, what were the steps to reproduce the behaviour? Can you send us output of
pactl list sinksand
pactl list sourcesafter this happened?