Forum Replies Created
-
Posts
-
Hi ethanee, can you contact us via issues[at]nomachine.com? We’ve fixed this bug and have a webclient binary available for testing.
You need to open port 4000 TCP (or the port you decided to use for the NX service) on your firewall configuration. The ports are added automatically to the firewall configuration on Windows. Not so on Mac and Linux. This is going to change in the future.
Can you send us the logs? Follow the instructions here:
https://www.nomachine.com/AR07K00677
Either attach them here or submit them to issues[at]nomachine.com
@aellus download the latest 4.1. One of the fixes was specifically “Excessive X server CPU load on the client when connected to a server 3”.
The release announcement is here:https://www.nomachine.com/SU02L00100
Slackware is not supported but we will fix it. Check out the TR here: https://www.nomachine.com/TR02L04284
Can you provide details of OS client side and application and their respective versions? What application is it on the server side, OS and desktop environment and version? That way we can investigate.
Hi ramkiller1, we will still need logs. Follow the instructions here and send to issues[at]nomachine.com
It’s a bug and a TR has been opened.
Hi Zia,
Did you log in with the customer ID and password that was created for your, and download the AVC package?
Hi DarkNova, to better understand what the issue is, can you please send three screenshots, in PNG format, taken 1:1 of the display as rendered by NoMachine, TeamViewer and UltraVNC?
It would also be nice if you could send the screenshot while the display is in “Keep aspect ratio” and “Fit to window” mode, so that we can understand if it’s only a problem with the scaling algorithm.
Attach images to your reply or send to issues[at]nomachine.com.
Doc, check this article…
The correct command to update RPM packages is:
rpm -U <package_name>
and in the case of DEB
dpkg -i <package_name>So using this command when upgrading to Terminal Server from NX Enterprise Server 3. Did you use either of these? We’ve checked to make sure, and if everything is working ok. If you did, we appreciate seeing the installation logs so we can see what happened and fix it. Just zip up the VAR logs and send them to us http://https//www.nomachine.com/AR07K00677
To fix the problem, you should copy the lic files to /usr/NX/etc/. If that doesn’t help, do a reinstall.
Can you try the latest release, NoMachine 4.1? If you are getting the same issue, we will then require the full set of logs.
https://www.nomachine.com/AR07K00677