Forum Replies Created
-
Posts
-
If you have an Enterprise Desktop Subscription, you can get access to the support team by logging in with the customer ID and password you received at the time of purchase 😉
Switching to the production version shouldn’t trigger such problems with logging in or multiple processes. These need to be investigated thoroughly: the support team will be able to assist you further.
Logs show that there’s a bug in the UDP code. A temporary workaround is to disable UDP in the connection preferences. Sign up to receive notification of the fix using ‘notify me.’
Some things you can check are that
EnableUPnP NXis uncommented in the server.cfg i.e you should make sure it’s without ‘#’ 🙂
And if you open a terminal window on the server (cmd) and runnxserver --upnpmap(it has to be executed once you’re in the %ProgramFiles(x86)%\NoMachine\bin directory) it should show the external IP and port.If that still doesn’t work we’ll need the logs (see my instructions from an earlier post) and
nxserver --upnpmapoutput.We’re not able to reproduce this behaviour at all. What’s the version of Chrome and Chromium you can reproduce this problem on?
Until NoMachine Network is available, users will have to know the IP or hostname of the remote computer.
If the router accepts UPnP or NAT-PMP commands, NoMachine (free) will attempt to retrieve the public or external IP of the host machine where it’s installed and configure the router to allow a NoMachine client to connect from outside of the private network (WAN).
In some cases, ports will have to be opened manually on the router and mapped to the public IP address of the server host. Please see the following article for more details:
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827If you want to be added to any beta-testing we make available, please submit a Contact Request (see footer -> Contact us -> General enquiries) and request to be added. We will be happy to add your email to the list 🙂
GTX 580 is a Geforce 500 series graphic card. That’s based on Fermi architecture, which is pre-Kepler. Nvenc was first introduced in Kepler architecture, therefore hardware encoding isn’t possible in your case. You might find this useful from Nvidia’s website: https://developer.nvidia.com/video-encode-decode-gpu-support-matrix
We’ve just sent you a link to the package you are meant to use 🙂 please install it and then follow Giorgi-G’s instructions.
Thanks for the feedback on the issues you’ve encountered with 18.04. They’ll be passed on to the testers 😉
Can you send us the complete logs and backtrace? Send everything to forum[at]nomachine[dot]com.
Instructions for extracting logs (server side) are here: https://www.nomachine.com/AR07K00677
Backtrace here: https://www.nomachine.com/AR09L00810Thanks!
Since the last exchange, a new version has been released, so we recommend you update the software and open a new topic if the problem persists.
Although we haven’t yet added it to our official list in the download section, NoMachine runs on Debian Stretch without any problems provided you are not using Wayland protocol. Wayland will be supported in an upcoming maintenance: https://www.nomachine.com/FR10N03221.
To check what’s being used in your session, you can look in the C-*/session logs.
If you get:
Info: Using H.264 software encoder.the encoding is done by the CPU, otherwise you’ll get “hardware encoder” if it is done by the GPU.
If there is no H.264 encoding available on the server, it will fall back to VP8 and in the panel you mention, you will see VP8, not H.264.
More info about H.264 is here:
Enabling the H.264 codec on the NoMachine client host https://www.nomachine.com/AR10K00696
What do I need to do to allow NoMachine software to use H.264? – https://www.nomachine.com/AR10K00696