Forum Replies Created
-
Posts
-
Hello iainhallam
When you installed package nomachine_5.2.11_1_x86_64.rpm you
shouldn’t install nomachine-enterprise-client because nomachine
‘server’ package also includes ‘client’ part. If you need on
your machine only NoMachine client, please just run as root:/usr/NX/scripts/setup/nxplayer --updateThis fixes the problem with ‘Applications’ menu entry.
If you need installed server and client parts on your machine,
please remove existing package:rpm -e nomachine-enterprise-clientand install again:
rpm -i nomachine_5.2.11_1_x86_64.rpmLooks like you are trying to connect by SSH protocol to the port 4000.
To fix this you can create a new connection in nxplayer and use
default settings or you can change your current connection:1. Open nxplayer and find icon of your current connection.
2. Click right mouse button on the connection.
3. From a context menu choose ‘Edit connection’.
4. In ‘Protocol’ field choose NX.
5. In ‘Port’ field set 4000.
6. Accept your changes by clicking ‘OK’ button.
After the fix if you still have problem, please try connect again.
Wait until error shows up in nxplayer and then click ‘Save logs’
button. Please save and send the log file to us.Hello,
I can see that you use package for 32 bit OS. Could you confirm that you have x32 Ubuntu?
Please run in terminal:uname -auname -por in Unity Search:
System Settings -> Details -> Overview -> OS type
if in output you find i686 or 32-bit, please send to forum[at]nomachine[dot]com
output from installation and a packed log directory:/usr/NX/var/logIf you have 64 bit OS, please try:
https://www.nomachine.com/download/download&id=1
sudo dpkg -i nomachine_5.1.44_1_amd64.debHello Hugga,
Do you use on your PCs Active Directory or similar technology?
Is ‘nx’ a domain user?Could you zip whole log dir on both machines (PC1,PC2):
C:\ProgramData\NoMachine\var\logand sent to forum[at]nomachine[dot]com, please.
Hello Greenrose,
Could you zip whole log dir:
C:\ProgramData\NoMachine\var\log
and sent to forum[at]nomachine[dot]com, please.
Is it something unusual in settings of your PC?
Is the OS installed on a USB drive? Is it a virtual machine?Hello Canufrank
Looks like your computer processor is 32-bit. NoMachine needs 64-bit CPU.
You can check this by run in terminal:
1. CPU name:
sysctl -n machdep.cpu.brand_string“Core Solo” or “Core Duo” CPU it’s 32-bit only
2. Check if your CPU supports 64-bit:
sysctl hw.cpu64bit_capableHi,
open a terminal and tell me the output of this command:
sw_versuname -aIf the output of ‘uname’ includes i386 or x86please send also this packed dir:
tar czf log.tar.gz /Library/Application\ Support/NoMachine/var/log/Please use this e-mail:
forum[at]nomachine[dot]com
if they are too large to attach in the forums.
Hello,
We have prepared a debug package and can send you the link.
Please send logs from the installation, even when everything will be ok:
forum[at]nomachine[dot]com
Hello,
You can use this command as a workaround:
sudo bash -c "echo \"manual\" > /etc/init/nxserver.override"This will be fixed in the next release.
You can track this issue by enabling “Notify me when the TR is closed.”:
https://www.nomachine.com/TR01N06343Hello,
Looks like you uninstalled partially your previous version of NoMachine.
The right uninstall command is:sudo dpkg -r nomachineWhen you do update, uninstallation isn’t necessary.
In your situation you can do this:
1)
sudo dpkg -r nomachine2)
sudo rm -rf /usr/NX /etc/NX /var/NX3)
sudo dpkg -i nomachine_5.0.63_1_amd64.debHello Jenefa
You most likely used ‘sudo’ a few commands earlier. Remember that
usually ‘sudo’ doesn’t prompt for password again if you’ve already
entered it. Password prompts depend of your OS configuration.
Are you sure that you use appropriate package for your OS architecture?
Packages ‘amd64’ for 64 bits and packages ‘i386’ for 32 bits.The right command to install NoMachine Free on Ubuntu x64 is:
sudo dpkg -i nomachine_5.0.53_1_amd64.debMore about NoMachine’s installation you can find in:
https://www.nomachine.com/DT07M00078&dn=
Are you sure that nxserver isn’t running? Do you see NoMachine Monitor
in your system tray? It’s a white-grey icon with ‘!M’ near system’s
clock.
If you don’t see it, could you check OS processes by run this command
in terminal:ps aux | grep nxBasics of NoMachine you can find here:
Hello,
Unfortunately it’s a bug. It’ll be fixed in a next release.
Old kext wasn’t replaced during update.As a workaround you can do this:
1. Uninstall NoMachine:
sudo rm -rf /Applications/NoMachine.app2. Install again the newest package.
Hello,
In your case you shouldn’t get information about update blockade.
In the next release this bug will be fixed. Thank you for reporting it.
To do update you need:1. Create file:
sudo touch /usr/NX/etc/DisableBlockingScript2. Do the update again (NoMachine Free):
rpm -Uvh nomachine_5.0.43_1_x86_64.rpm3. Remove the file:
sudo rm /usr/NX/etc/DisableBlockingScriptHello,
We aren’t able to reproduce your problem in our lab. We need more
details. Could you run below commands and send output to
forum[at]nomachine[dot]com, please?1)
/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --version2)
system_profiler SPSoftwareDataType3)
codesign -vvv /System/Library/Extensions/nxaudio.kext/4)
find /System/Library/Extensions/nxaudio.kext/ -type f -exec md5 {} \;Hello,
As is mentioned in dnf’s manual, distro-sync command searches enabled repositories.
NoMachine’s package isn’t in any repository so the command try to remove it. You
can try to run distro-sync without ‘–allowerasing’ option or in some way exclude
NM’s package from the operation. To do update Fedora’s manual recommend a command:dnf upgrade