Forum Replies Created
-
AuthorPosts
-
CarinParticipant
Hi Marcelo,
It looks like as you were evaluating NoMachine before, when you did the new install, the software took expired license already present in the /usr/NX/etc folder.
We suggest you do a new clean install:
– Remove currently installed NoMachine product
– Remove /usr/NX/ folder
– Install NoMachine product you need.You can also contact the NoMachine sales team here: https://www.nomachine.com/contact-request.
CarinParticipantHi Manuel,
We have never encountered such a problem that attempts to NoMachine session could disconnect the VPN client. Can you tell us which VPN you’re using? Is there some antivirus on the client machine? Are you sure that you didn’t change any other configuration except for the NoMachine upgrade?
Can you please send us VPN logs showing the problem? You can send them directly to forum[at]nomahcine[dot]com, adding the title of the topic to the email subject. Thanks!
CarinParticipantHi mkirkove,
Thank you for sending the new recording.
We noticed that some keys are pressed constantly on the server-side. Does pressing those keys inside the session releases them and does after that the clipboard start working?
Also, can you tell us which keyboard layouts you’re using on both the client and server sides? Thanks 😉CarinParticipantHi lcbbcl,
I suggest you try the workaround in this Trouble Report, it should help to fix the issue you’re facing: https://knowledgebase.nomachine.com/TR02Q09140
October 15, 2021 at 18:10 in reply to: Can’t control mouse and keyboard (Windows server, multiple clients) #35770CarinParticipantHi, aaccioly,
Sorry for the delay.
We received your logs. However, we could not see the debug messages in the logs.
Could you please try again, this time completely removing the existing installation prior to installing the debug package? Thank you!CarinParticipantHi mkirkove,
Thank you for sending the recording. 🙂
However, would it be possible to send us a new one showing the onscreen keyboard? What we need to see this time is a recording of the whole screen on the client-side (your Linux Mint), including the NoMachine window and also showing the onscreen keyboard visible while recording.You should enable onscreen keyboard on the client-side (Linux) and then enable the same on the server-side (MacOS) and do a recording so that both keyboards are visible.
Many thanks!
CarinParticipantHi tamkir,
I believe you’re using NM free version, with which you can have one concurrent connection.
Here you can see a feature comparison between the free version (for personal use) and the Enterprise Desktop subscription: https://www.nomachine.com/remote-access-for-everyoneCarinParticipantHi esdpante,
No problem! 🙂
Error 108 usually means that something forced the connection to shut down.First check that you have followed our tips here:
https://knowledgebase.nomachine.com/AR07N00896Then, so that we can queue up for investigation, can you send us client and server-side logs? You can follow the instructions in this article: https://knowledgebase.nomachine.com/DT11R00181
Please send the logs directly to forum[at]nomachine[dot]com adding the title of the topic to the email subject. Thanks!
CarinParticipantHi mkirkove,
Sorry, the file failed to attach again. Can you send it directly to forum[at]nomachine[dot]com adding the title of the topic in the email subject? Thank you 🙂
CarinParticipantHi bradbulger,
So that we can queue up for investigation, can you please send us server-side logs? You can follow the instructions in this article: https://knowledgebase.nomachine.com/DT11R00181#1.4
You can send the logs directly to forum[at]nomachine[dot]com, adding the title of the topic in the email subject. Thanks!
CarinParticipantHi roberto16900,
sorry for the delay. We checked your log file and we could not figure out what is happening.
To help us investigate, can you please collect debug logs following the steps described in the article below?
https://knowledgebase.nomachine.com/DT10O00163#1.4You can send the logs directly to forum[at]nomachine[dot]com, adding the title of this topic to the email subject.
Thank you!
October 11, 2021 at 18:30 in reply to: SELinux is preventing systemd from ioctl access on the file nxserver.service #35689CarinParticipantHi maxim-nomachine,
thank you for reporting this. We were able to reproduce the problem in our labs and opened a Trouble Report: https://knowledgebase.nomachine.com/TR10S10384
CarinParticipantHi EddieA,
Thank you for the update.
Those logs are not produced by NoMachine’s software. They are produced by the applications or the desktop environment that are launched in the NX session.
In order to understand which application is producing them, you have to examine those logs.CarinParticipantHi mybigslash,
We have an open request for this feature: https://knowledgebase.nomachine.com/FR10P03723
In the meantime, you can work around the problem by importing the private key on a connection created with a NoMachine client for desktop, and by uploading it to the iPad through iTunes (download the NoMachine folder with File Sharing, copy inside it the new connection file, upload the folder).
Thank you for reporting.CarinParticipantHi mkirkove,
You can take a look at this article about recording sessions with NoMachine: https://www.nomachine.com/recording-the-remote-or-local-desktop-with-nomachine
-
AuthorPosts