Forum Replies Created
-
Posts
-
To completely remove NoMachine you can execute:
sudo dpkg --purge nomachine sudo rm -rf /usr/NX /etc/NXWe strongly recommend you update to the latest which is version 6.4.6, firstly because we no longer support v4 ; and secondly it’s better to use a more recent version for fixes and its new features etc
“NX> 161 Enabled service: nxserver”
This is not an error. It simply console output which tells you that NX is running on the host.
Make sure you are using the latest version of NoMachine on both the connecting client and remote server. Then tell us if you still have the same problem.
Hi.
We couldn’t reproduce problem on Ubuntu 13.10 in our labs, not even connecting to a headless machine. From the description, it seems like a crash of the xserver, not NoMachine.
After googling the error code, I found some similar reports in this forum.
Which error code? Can you tell what NoMachine version is installed there?
Can you create new user and log in to that user’s desktop locally? If you can, please also try connecting via NoMachine.
It is difficult to find a rational reason for which NoMachine would break display and make it irrecoverable. NoMachine options allow to choose one of the possible resolutions available by the hardware during connection to physical session.
We aren’t able to reproduce this problem. If you could show some screenshots of your system display settings, we can try to help further.
The connection file which is mentioned in this case – stores pre-session settings. The directory defined in the Connections field from the ‘Player environment panel of the GUI’ is by default located in the
~/Documents/NoMachine.So in this case it is better to create a new connection. Are you able to see the login prompt? If not, it looks like there is still a problem with the Security Groups configuration. Could it be that the wrong group was assigned?
It looks like you are connecting to a virtual desktop as the same user, which is the physical desktop owner on this Ubuntu. At the same time Chrome Browser is already running on this physical display. So there are two sessions logged in with the same credentials. Chrome doesn’t let you create two instances of the browser in two different sessions as the same user.
So to avoid the problem – just close Google Chrome on the physical display or create a virtual session as a different user.
It looks there is still problem with Security Groups configuration. Did you tried adding a rule with selected “Custom IP” as “Source”?
We have tried to reproduce on our Raspberry Pi set-ups without success. Everything works as it should.
So logs from your Kali would be welcome.
To create a new Security Group – find “Network & Security” on the left AWS panel. Choose “Security Groups” and launch “Create Security Group”. Then:
- Click ‘Add Rule’.
- In ‘Type’, set Custom TCP Rule.
- Protocol should be set to TCP.
- Set Port Range to 4000 (the default port used by NoMachine).
- In ‘Source’ select Anywhere or Custom IP.
To add Security group to existing instance – click right mouse button on the correct instance. Select “Networking” -> “Change Security Groups”. Now choose correct group and click “Assign Security Groups” to confirm. Then you’ll be able to connect via NX protocol.
Is it possible that you installed NoMachine Enterprise Desktop on the machine where your previously had NoMachine free installed? During installation the new package doesn’t overwrite old config and license files, so please try uninstalling NoMachine and removing the whole /usr/NX directory. Then install NoMachine Enterprise Desktop again.
Hi.
This is because macOS Mojave has in introduced a further layer of checks which require apps to get user’s approval before controlling the Mac from remote or accessing microphone and camera. Please refer to article “how to use with NoMachine on Mac Mojave”: https://www.nomachine.com/AR10P01001.
We couldn’t reproduce either of the issues on Raspberry Pi 3 with Kali. You’ve written that it worked earlier – are you sure you didn’t change something in the nxserver configuration files?
I would uninstall and completely remove any traces of the previous installation first before reinstalling.
Do that by running the following commands:
sudo /usr/NX/scripts/setup/nxserver --uninstall sudo rm -rf /usr/NXand install again. If the problem is still there, enable debug, reproduce again and send logs from the server side (instruction how to collect logs you can find there: https://www.nomachine.com/DT10O00163
If you have NoMachine version 6 you can use also NoMachine Monitor’s menu item “Close the NoMachine application” (https://www.nomachine.com/AR11P01005). After click it will show question: “Do you want to run the NoMachine application at the next startup?” to permit to start automatically the server at next reboot. The administrator will also have the option of not being asked that question again the next time the NoMachine application will be closed, with a “Do not ask this question anymore” box.
Is there a tutorial somewhere for setting up access to a remote disk drive (on both ends)?
Please refer https://www.nomachine.com/accessing-files-on-local-or-remote-disk-drives.
Is it possible you didn’t disable the automatic start-up of NoMachine at boot? To disable it:
– Click on the Monitor (the !M icon) in the system tray to open the menu
– Click on ‘Show the service status’
– Choose ‘Shut down the server’
– You will be asked whether you want to restart the server or not at the next boot
– Click on ‘No’.More information you can find there: https://www.nomachine.com/AR04L00800.
1. Which NoMachine version are you using?
2. Are you able to ping that machine using IP address?
3. Are you able to ping that machine using hostname?
4. During NoMachine connection are you using IP or hostname?
5. What exact error shows? Can you send a screenshot?
6. Can you send a screenshot of NoMachine processes on the server host? (Ctrl+Shift+Esc, choose “More details” and sort by name).Did you try
"C:\Program Files (x86)\NoMachine\bin\nxserver.exe" --upnpstatuscommand? If you have enabled UPnP, it should show External IP and Port.There are instructions how to enable UPnP here: https://www.nomachine.com/AR11L00827.
I’ve read this post https://forums.nomachine.com/topic/two-private-ips-no-public-ip and seems I might have the same issue.
If you have double NAT networking, NoMachine has to go through two routers and you need to set up manually separate port forwarding rules on each device (https://forums.nomachine.com/topic/public-ip-not-in-server-status).