Forum Replies Created
-
Posts
-
Hello,
-
Do you have Windows XP SP3 32bit or 64bit version?
Reproduce problem, collect logs and send them to forum[at]nomachine[dot]com? Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT10O00163#1.4Hello,
Please can you try with following information:
- Check with terminal SSH.
- Check with nxplayer + SSH.
- Check what happens when /etc/pam.d/sshd is reused for /etc/pam.d/nx (backup of nx file first).
- What’s inside /var/log/auth.log (run as root
grep -r "nxexec" /var/log/auth.logand share the output). - If nothing helps, send us new set of NoMachine server logs with debug enabled, /var/log/auth.log (or at least nxexec lines), and content of /etc/pam.d
Hello,
you are installing 32bit packages on 64bit OS.
Please remove current installation using following document: https://www.nomachine.com/DT09K00056#4.2.
After uninstall, please install this package https://www.nomachine.com/de/download/download&id=6.
Please execute following commands to unload and remove kext file
sudo kextunload /Library/StagedExtensions/Library/Extensions/nxaudio.kext sudo rm -rf /Library/StagedExtensions/Library/Extensions/nxaudio.kextHi,
I understood your corporate computer was at your company’s location (ie. in the office), when in fact they are both at home.
Is connecting from A to B possible? Is connecting from B to A possible?
To be able to connect from A to B or vice-versa when both are at the same location, it is strongly recommend you:
– Connect both machines to the same wifi
An alternative solution if connecting both machines to the same wifi is not possible is to configure “Connect a network port” in NoMachine described here: https://www.nomachine.com/DT10O00157#4.4.
When port is forwarded then connect from Machine A to machine B using the IP shown like on the uploaded image.Attachments:
Hello,
We will need debug NoMachine server logs to investigate the issue. Please follow the instructions here:
https://www.nomachine.com/AR07K00677After enable debug logs on problematic machine please execute:
/etc/NX/nxserver --restartPlease after that try to reproduce the issue
Send logs to forum[at]nomachine[dot]comWhat I have understood is that you are trying to connect from your home to your corporate Windows machine.
Would recommend that you check with your IT department if they can provide you vpn access or port forwarding from your office public IP to the local machine NoMachine port.
Can you try to add user nx to the following groups aid_sdcard_rw,aid_inet and then restart nxserver
usermod -a -G aid_sdcard_rw,aid_inet nx/etc/NX/nxserver --restartHi uncled,
I verified download few times and everything is OK, so to avoid using the old corrupted installation file, please do as following
curl https://download.nomachine.com/download/6.9/Linux/nomachine_6.9.2_1_amd64.deb -o nomachine_6.9.2_1_amd64-new.debmd5sum nomachine_6.9.2_1_amd64-new.deb dpkg -i nomachine_6.9.2_1_amd64-new.debHi uncled,
Based on the output it looks that your package is broken during download. Please can you verify MD5 signature by using command
md5sum nomachine_6.9.2_1_amd64.debCorrect MD5 signature you can find here https://www.nomachine.com/download/download&id=6
Additionally, can you show output of the command
uname -aYou can disable Client hw acceleration per session, by changing the Display settings in the NoMachine Menu Panel. See the following image.
You can change default settings for the specific user by editing $HOME/.nx/config/player.cfg file and changing default value <option key=”Enable hardware accelerated decoding” value=”false” />
Please note that for editing the player.cfg file NoMachine player should be closed.
Attachments:
You can use following command to display related client information:
sudo /etc/NX/nxserver –history –client-platform –client-type –client-version
Additionally, to display list of all nxserver commands you can use sudo /etc/NX/nxserver –help.
We can confirm that the behaviour has not changed between releases.
If that was the case, it would mean that the owner of the desktop would have to physically get up, go to the remote computer and click accept for his own connection request.
Maybe you are confusing the authorization dialog (when it’s a different user connecting) with the notification pop-up telling you that “user xxxx connected” ?
I could not reproduce reported problem, update does not change any settings.
Please can you provide following information:
- Is it possible that you added the user as trusted or administrator on the server?
- Is it possible that your server was displaying login window?
- Is it possible that windows user accessing desktop is administrator?
- What was the version number you were updating from?
As well please can you provide result from the command:
grep PhysicalDesktopAuthorization /usr/NX/etc/server.cfg
