Forum Replies Created
-
Posts
-
Hi, what you need is the upcoming NoMachine Network service which will be released in version 9. This will let you connect to the remote machine without having to know the IP address of the remote machine. You’ll be able to publish your computer on Network, and then by logging in with your NoMachine account and provided you have a Network Subscription, you will be able to reach that computer. Read more about it here: https://www.nomachine.com/network 🙂
Can you send us your configuration of nginx/ openresty? We’ve checked on the fly and didn’t encounter any issues.
It would also be useful to have system logs(journal) to check why Gnome is playing up. You could try enabling virtualgl, or use an alternative desktop environment, lightweight as XFCE or LXDE.
How to enable VirtualGL support on Linux in NoMachine
https://kb.nomachine.com/AR05P00982
https://kb.nomachine.com/AR04Q01024Hi distearth, please provide details of your set up (Linux distribution, version, desktop environment etc etc), and steps to reproduce. This could be a different issue and in that case I will split your issue off from this one.
You should check if NoMachine Audio Adapter has been created – it should be visible as an audio device in the system. It should also be set as the default device during the session.
Are you using the latest NoMachine version from our website?
Are you connecting on LAN or over the Internet?
Logs would be useful. Please take a look at a similar topic here: https://forum.nomachine.com/topic/connection-time-out-trying-to-access-nomachine-ubuntu-desktop#post-45488. Can you provide that information?
Can you tell us what IP address is being used? I.e you are definitely using the LAN’s IP.
Is it a virtual machine perhaps?
The logs would also be useful from the server. To gather those up, please follow the instructions here:
https://kb.nomachine.com/DT07S00243
You can attach them here or submit to forum[at]nomachine[dot]com.
Hi, the image you tried to link to is not available, so the URL has been removed. Please attach the image here that you would like to show us. Also confirm the NoMachine version on client and server sides and the OS as well. If Linux, the distro and desktop environment is also useful.
What is the system and desktop environment?
Is this an installed Workstation out-of-the-box or did you change something (or someone else maybe changed something?) It looks as if custom sessions are disabled. More info about this here: https://kb.nomachine.com/AR07P00989
Can you tell us the output of:
sudo grep AvailableSessionTypes /usr/NX/etc/server.cfg?You could also try this command as well:
sudo /usr/NX/scripts/setup/nxnode --availablesessionsetupOn the machine you are connecting to, (the server), can you check that the NoMachine service is running? To do that, go to the Windows system tray and find the !M icon, right click and select ‘Show server status’. Submit a screenshot please.
Also, check the exact product and version you have installed by going to Updates. Please do this on both Windows computers.
In NoMachine version 8 (for new installations), UPnP/NAT-PMP is disabled by default in the Free Edition. To get access to your computer over the Internet, NoMachine’s UPnP/NAT-PMP port mapping must be enabled by hand (‘Server settings -> Ports’ -> Select the service and click on Configure); or alternatively, your router can be configured with the appropriate port-forwarding rule.
More about this here: https://www.nomachine.com/AR10T01175
Does this help?
Hi, check out the article here in our knowledge base:
How to connect to Windows with NoMachine and an empty password
https://www.nomachine.com/AR05L00802We were able to reproduce a similar issue and compared the logs which show the same error. It affects only the 64-bit package. A temporary workaround is to use the 32-bit version. Try it and let us know.
The logs from the arc 380 continue to show the MFX_ERR_UNSUPPORTED error which we print as:
Info: Intel Quick Sync H.264 acceleration is not supported.
Info: Please consider updating your Intel drivers.It would have been useful to know the outcome of installing/building mediasdk using the other ways we mentioned in the articles provided for comparison. As things stand, it is likely that the issue is with the Linux drivers.
We are aware of a similar behaviour and need to verify if your problem is the same. If it is, we suspect a problem caused by a Wacom driver. So that we can confirm it’s the same issue or indeed a different one, please tell us whether you have a Wacom pen/tablet connected to that Windows client. Are you running a service running called “Wacom ISD Service”?