Forum Replies Created
-
Posts
-
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?
Hi, this is a known issue. You can track it using the following link:
Right mouse button behaves like left button if Control key is pressed down
https://knowledgebase.nomachine.com/TR05S10246Sorry for updating this topic late, I thought one of us had followed up already. I checked just to make sure with the latest version of NoMachine. Even though your topic is more of a copy and paste issue, not a shortcuts-not-working issue which is what we originally thought, we don’t have any problems with shortcuts, nor with pasting between Mac and Windows VM.
“I get no message when doing copy/paste.” – this is what VMware shows maybe? It’s not one of NoMachine’s own messages.
If there is a problem with NoMachine not recognizing commands or clipboard not working properly, please state the steps for us to reproduce. Also confirm if this is a traditional NoMachine player session or a web session. Thanks.
A quick update on this topic. We continue to track this report even though we have been unable to reproduce it so far. It seems to be affecting this particular user’s set up which is strange. In the meantime, the topic has been closed but users can submit new topics if this behaviour continues on later versions of NoMachine.