Forum Replies Created
There is a server.cfg configuration key to configure UDP port.
You can specify a port range, in the form of minport-maxport, to use UDP communication for multimedia data. Alternatively, you may specify a comma-separated list of ports or a single port. In this last case, only one connection will be able to use UDP at any given time. As a note, the Internet Assigned Numbers Authority (IANA) suggests the range 49152 to 65535 for dynamic or private ports.
This article explains where you can find the configuration files: https://knowledgebase.nomachine.com/AR02N00877May 12, 2021 at 15:56 in reply to: Keyboard: wrong chars being type (keyboard encoding?) #33412
The log files failed to attach. Please try sending them directly to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. Thanks!
We took a look at the logs you sent us. However, in order for us to continue the investigation, we will need a complete set of logs.
Could you please send us also server-side logs from the user’s home (session logs)? The display session log files should be stored in the correspondent session directory created under the home directory of the session owner, e.g. the user’s home/.nx/node/C-display–sessionid directory.
You can follow the instructions on how to collect the session logs automatically explained in this article: https://knowledgebase.nomachine.com/DT11R00182
It doesn’t look like the problem is related to NoMachine.
Please check your security/firewall settings.
Despite our efforts, we couldn’t reproduce the problem. So, in order to proceed can you please collect and send us server-side logs? This article explains how to collect the logs: https://knowledgebase.nomachine.com/DT11R00181
Please submit them to forum[at]nomachine[dot]com making sure you add the title of your topic as the email subject. Thanks!
@junkhar, you may take a look at this article How to solve black screen and other possible problems on headless machines
@amigabill, in order to further investigate the issue can you please collect and send us server-side logs? You can follow the instructions explained in this article: https://knowledgebase.nomachine.com/DT11R00181#1.1. Please submit them to forum[at]nomachine[dot]com adding the title of the topic as the email subject. Thanks!
The log files failed to attach. Can you send them directly to forum[at]nomachine[dot]com? Please make sure you use the title of the topic as the subject of your email. Thanks!
@commandline The client with high CPU load issue will be handled in the topic here https://forums.nomachine.com/topic/nxclient-bin-high-cpu-load-100-ubuntu-20-04-lts
@bobnx What do you mean with “Potex are still investigating this problem” ?
not quite sure how NoMachine is related to your installation of [removed]. However, if you are asking about how to set the display number that NoMachine should use, you can do it by setting the appropriate key.
For physical desktops, specify the physical display or range of X server displays which are made available to NoMachine connections. It is possible to specify a # single display by display number, e.g. :0, or by port, e.g. 6000.
The range of displays can be specified as a dash-separated list, e.g. :0-:7 or, by port number, 6200-6204. By default all displays
detected as running will be made available for users.
For virtual desktops (if you are running for example Terminal Server) set the base display number for NX sessions.
If, on the other hand, you want to go into a detailed comparison of how NoMachine compares with the other product you are using, I suggest you contact our sales team 😉May 4, 2021 at 14:03 in reply to: No display shown on Linux Mint, system freeze up on Windows 10 #33228
We received the logs. Thank you!
The problem might be related to hardware decoding. Can you please try to disable the hardware acceleration as explained in this topic https://forums.nomachine.com/topic/disable-hardware-acceleration-on-the-client-side ?
To help us understand the problem, can you tell us the following:
– what is the OS version on the client and on the remote PC?
– which NoMachine version are you using on both client and server sides?
– what is the error that you’re seeing when trying to connect?
Please send us a screenshot. Thanks!April 30, 2021 at 08:47 in reply to: No display shown on Linux Mint, system freeze up on Windows 10 #33181
Client and server-side logs will be helpful to investigate the problem. Can you please gather them following the instructions in this article (https://knowledgebase.nomachine.com/DT11R00181) and send them as an attachment directly to forum[at]nomachine[dot]com? Please make sure you use the title of the topic as the subject of your email. Thanks!
Supporting M1 is one of our top priorities, although it is likely it will be supported after the initial release of version 8 which is in its final stages I am unable to give you an ETA.
Here is the feature request which you can all sign up to receive a notification if you are interested in knowing when it has been implemented. FR12R04054 – Offering NoMachine packages natively built for Apple M1 Chip
Our product team will evaluate your suggestion. Thank you again for taking the time to share your feedback with us.
Thank you very much for taking the time to provide this feedback. I can understand your point-of-view and I am sorry that you aren’t comfortable with the new design of the UI. In version 7 we redesigned the interface in order to make the opening of, and access to, multiple sessions faster because this is the most common use we have found amongst our users and what our users asked us for more frequently. A possible solution for you could be to place multiple NXS files on your desktop that you can double-click to open the session directly. Alternatively, you can stick with version 6 on your client.