Forum Replies Created
-
Posts
-
It looks that your firewall is somehow blocking incoming connection to the port 4000. If you are using Windows default firewall please can you check if firewall rules for NoMachine server are enabled, or please add new firewall rule to accept incoming connection to the TCP port 4000. See screenshot.
Attachments:
Hello,
At the moment audio and usb devices are not working on M1 processor running as NoMachine server. Audio will be supported on Apple M1 processor with implementation of the following feature FR12R04054 – Offering NoMachine packages natively built for Apple M1 Chip
Related problem will be tracked here TR10S10392 – Starting a connection with a URL scheme on Mac doesn’t work as expected
Hello,
I have similar configuration and do not have problem with video.
Can you provide server and client side logs in the moment of the problem, here are instruction how to get them DT11R00181 – Collect server and client logs manually.Additionally, please collect statistics, you can get them from Connection tab of the NoMachine menu panel. More info see here DT10R00168 – Guide to the Functionality in the Menu Panel on Linux.
When you collect needed logs and statistics, please send it to the forum[at]nomachine[dot]come with mentioning forum topic.
There is no drop-down menu in the NoMachine, but you can use easy way to open NoMachine menu by going with the mouse in the right upper corner.
Additionally, you can use keyboard shortcuts for example for the Full Screen press
Ctrl+Alt+F.Hello,
Please check following document, I think you can find all needed information there: https://knowledgebase.nomachine.com/DT10R00171#10.
This issue does not look like NoMachine problem, but firewall configuration that is blocking connection. Possibly would be good to enable firewall logs and get information what is dropping connection. you can change Log dropped packets to yes.
Attachments:
Hi,
If I understood well your request, it is possible for the Administrator to disable unneeded session types in NoMachine terminal server. Please check following article AR07P00989 – How to disable specific session types (e.g. custom sessions) on Linux.
Crash is dumped by the OS, and depending on your configuration core file can be located in your home folder or /var/crash/ folder.
I noticed that uploaded logs exceeded upload size, so please can you email them at forum[at]nomachine[dot]com.
From the logs we noticed that there is a problem that one process is hanging. With logs provided, the problem is hard to debug, to handle it we would require more data.
Please set in the /usr/NX/etc/node.cfg:
SessionLogClean 0Also it seems, that master agent hangs in this case, so please add this line at the bottom of the /usr/NX/etc/node.cfg:
dumpCoreOnHang 1or useecho "dumpCoreOnHang 1" >> /usr/NX/etc/node.cfgThis will cause the server to kill node with signal 11 instead of 9, so please make sure the system can handle core dumps. After this please restart the nomachine server:
/etc/NX/nxserver –restartIf the Agent hangs, the system produce core report for nxnode process. We would require the backtrace of all threads. The instruction is available here:
AR09L00810 – Using GDB to debug a core file on LinuxMake sure that debug, is enabled as per instruction Reproduce the problem and send the server and node logs as mentioned in the previous post as well as the debug traces from the core dump.
I can only think about one possible case that you have enabled “Block all incoming connections, including those in the list of allowed apps” see screenshot.
If that is disabled please try enabling NoMachine port 4000.
Attachments:
Collect server side logs automatically
More info is written under paragraph “Fourth Step: Collect Client Side Logs (if requested)”
On Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx
