Forum Replies Created
-
AuthorPosts
-
May 21, 2021 at 14:53 in reply to: NoMachine wont connect to over different wifi networks for me #33583CarinParticipant
Hi Jonneal3,
Maybe you can have a look at this article How to connect over the internet to NoMachine behind a NAT router, if you haven’t done so yet.
CarinParticipantHi FastThenLeft,
You can take a look at this topic that dealt with a similar problem: https://forums.nomachine.com/topic/how-to-use-microphone
CarinParticipantHi almnofie,
We aware of this issue and have a Trouble Report open: https://knowledgebase.nomachine.com/TR10R09864
Our development team is working on an alternative implementation.
Thank you for reporting.May 19, 2021 at 16:24 in reply to: No printer access for NoMachine Linux 7.1.3 on Centos Stream? #33535CarinParticipantThe issue has been fixed in NoMachine 7.4.1 release. Please update 🙂
May 19, 2021 at 11:02 in reply to: Accessing Gnome running on RHEL in Windows Subsystem for Linux #33529CarinParticipantHi noknok0479,
You have created a very special setup. So far, we haven’t created a similar setup in our labs.
If you do manage to make it work, it would be very interesting if you could share more about your experience with us.CarinParticipantHi kleinfelter,
We are glad your solution works. Thank you again for sharing it.
i.e. one Hdmi Edid Emulator on the monitor end of your cable will fix the issue where NoMachine doesn’t work well without a connected monitor. It will work with or without a monitor.
Just adding a small note here, the problem is not that NoMachine doesn’t work well with headless machines, it’s rather related with the machine video out, that has limited functionality when running headless.
May 19, 2021 at 10:42 in reply to: NX clients should be able to relay location (GPS) and compass data. #33544CarinParticipantHi brigman,
It is a very interesting idea, indeed. However, our product roadmap priorities are focused elsewhere and to relay location (GPS) and compass data to the server as part of the NX protocol is not foreseen for the moment.
Many thanks for sharing your suggestion.
CarinParticipantHi kleinfelter,
We are glad you found a valid hardware solution.
Is there a way to just tell NoMachine to always launch its X server in addition to the one for the physical monitor? I don’t need to ‘share’ the physical session — I just need to connect remotely to *an* X session.
Actually, with a NoMachine Workstation license, you could enjoy the virtual desktop sessions, effortlessly.
A possible way to prevent the physical display from turning off when the monitor is disconnected would be to create a custom EDID file and reconfigure Xorg to use it.
CarinParticipantHi frpandore,
We investigated the logs you sent us, but we couldn’t find any problem related to the NoMachine software.
Can you please check the stability of your network connection? Which type of networking connection are you using? Is it a VPN?CarinParticipantHi ehammer99,
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.
UDPPort 4011-4999This article explains where you can find the configuration files: https://knowledgebase.nomachine.com/AR02N00877
CarinParticipantHi js,
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!
CarinParticipantHi frpandore,
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
Thanks!CarinParticipantHi tranhuy,
It doesn’t look like the problem is related to NoMachine.
Please check your security/firewall settings.
CarinParticipantHi glevner,
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!
CarinParticipant@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! -
AuthorPosts