Forum Replies Created
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.
Is this happening when connecting to Enterprise Server on Suse?
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.February 13, 2014 at 12:16 in reply to: Clipboard not working upon initial virtual desktop creation #2291
Please check if this is due to some antivirus running on your machine. In particular try to shut down BitDefender or make an exception for the NoMachine client.
NoMachine Terminal Server v.4 = NX Enterprise Server 3.5.0. See this article here which explains what you need to use in version 4 based on what you were using in 3.x. https://www.nomachine.com/AR09K00689
Could you please submit your full set logs to issues[at]nomachine.com as they didn’t attach (perhaps they were too large)?
Hi, it’s not clear what the problem is. In version 4, the commands are exactly the same nxserver –list and so on. Are you getting errors? If so, can you tell us what they are?February 11, 2014 at 11:23 in reply to: Could not connect to the server. Error is 138: Connection timed out #2248
Please try the advice here first: https://www.nomachine.com/forums/forums/topic/cannot-connect-to-server
If the modem doesn’t work in ‘bridge’ mode but you have NAT on both modem and router then yes, you will have to set forwarding on both.
Sorry, I didn’t point you to the link on our website: https://www.nomachine.com/AR07K00677. This explains how to get the full set of logs.