Forum Replies Created
-
Posts
-
Hi, thanks for your appreciation of our software 🙂
The NoMachine client doesn’t start automatically, it can only be launched from the tray icon or from the Applications menu.
However we would like to understand what made you consider the client launched at system startup. Did you maybe think the NoMachine tray icon is only visible while a client is running?
Hi, if you are using Wayland you can try the advice in the following article
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://knowledgebase.nomachine.com/AR04R01083or disable Wayland.
Are you sure that you are using the correct IP address in the connection configuration? The IP address you pasted is one to use on the local network.
What OS are on the computers?
Are the two computers on the same network? Can you see the “other computer” (the one you want to connect to) in your Machines panel?
The error message is “68206 68206 11:21:25 236.896 ClientSession: Failing reason is ‘A connection timeout has occurred while trying to connect to ‘192.168.0.12’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.'”
The article I linked before describes what’s needed. If it’s impossible for you to enable port-forwarding on your router (please follow the instructions of the router’s manufacturer to do that), the better option is to wait for NoMachine Network.
https://knowledgebase.nomachine.com/FR07J02731
Once it is released it will remove the need to know the IP address of the remote computer you want to access as well remove the need for port-forwarding.
Treating multi-monitors on the client as separate monitors in NoMachine sessions is possible when the server-side is Linux and there are virtual displays running there. It is a feature which is not supported in the free version of NoMachine. You must install one of the products from our Terminal Server for Linux range on your Ubuntu server.
Try NoMachine Workstation.
Please check the following article:
How to connect to NoMachine when the server is behind a NAT router or a firewall
Similar topics are:
<https://forums.nomachine.com/topic/remote-access-over-internet-to-ubuntu-desktop-20-04-using-nomachine >
<https://forums.nomachine.com/topic/cannot-connect-over-the-internet-2 >I’ve deleted these attachments for your own security – it’s always best to remove saved credentials when sharing such files in a public forum. We’ll get back to you soon on what the problem could be.
Hi, can you send us the logs that you gathered to forum[at]nomachine[dot]com. Ideally, we’d also need the stackdump from the core file that you have. Put the title of the topic as the subject of your email. Thanks!
Try going to Microphone permissions (both client and server sides), uncheck and check NoMachine but on both hosts
– restart player on client side
– restart NoMachine server on server sideDoes this help?
From the logs everything in NoMachine appears to be working fine. If the problem in connecting was with NoMachine, you would in theory be getting time-outs every time, not sporadically. It could be a networking issue, between the host and the guest?
The link was meant to be:
https://knowledgebase.nomachine.com/DT11R00174#7.2
Sorry about that. I’ve also corrected the embedded link within Carin’s reply so it points to the right anchored section of the Workstation Guide (https://knowledgebase.nomachine.com/DT11R00174)
Please try the suggestions in 7.2 and let us know.
Some updates. Regarding Point 6, we didn’t find a way to reproduce it, but we’ve found some old Windows users reports about similar issues occurring with other software (not NoMachine). Sometimes killing the explorer.exe process and restarting it works around the issue, but usually the solution consists in understanding the tool or process that is causing such taskbar behaviour and uninstalling it.
For us to investigate the remaining points, can you confirm what the specific OS version is on the 2018 macbook you mention? (On the Macbook 2014 you say you’ve installed Big Sur but didn’t mention what’s on the other computer 🙂 ).
Regarding point 2 specifically, is the behaviour there regardless of the application you are using? Can you check whether without oldeventapi set the problem persists on both machines?
Hi,
regarding point 1 in your last reply, you should take a look at https://knowledgebase.nomachine.com/FR11R04044, which is under review, although function keys for changing brightness (which you mentioned in the first post) have not been considered. May I ask why you would need to control brightness?
Point 2 – We’re checking this.
Point 3 – We’re checking this.
Point 4 – For 4k displays we have the following planned, https://knowledgebase.nomachine.com/FR02M02864 and also https://knowledgebase.nomachine.com/FR12R04056.
Point 5 – Another FR in our roadmap. This looks like https://knowledgebase.nomachine.com/FR10M02977
Point 6 – We’re checking this as well and will come back to you 🙂
Hi,
ServerRoot = “C:\Program Files (x86)\NoMachine”
This can be ignored, it’s nothing to worry about.
Are you sure you’ve approved the changes to configure port-forwarding? You seem to have done everything correctly, including adding the rules in your firewall, but the online tool shows the port is closed…are you sure you are using the right IP address as the target computer?