Forum Replies Created
-
AuthorPosts
-
BilbotineParticipant
Hello fleure,
The logs would indeed be helpful to understand what went wrong.
Can you please send them by email to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email?
Thank you!
December 21, 2022 at 11:15 in reply to: Live user migration between servers for Linux desktops #42066BilbotineParticipantHi Dmitry,
Unfortunately, live user migration between servers for Linux desktops cannot be done by NoMachine. But you can check lower layer solutions, by example by some kind of virtualization solution.
Best regards,
BilbotineParticipantHi Piter,
The files you added to your post were unfortunately not uploaded correctly.
In order to investigate, we need to check them; can you please resend them by email to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email?
Thank you!
BilbotineParticipantHi jdslavin,
You can modify the global setting in the file – server.cfg .
The command
nxserver --useredit USERNAME --screensharing yes
stores this settings in the redis DB, that cannot be modified manually.As for uploading files, some types of documents cannot be uploaded because it has been restricted for security reasons. This is why w always recommend to send us logs via email
BilbotineParticipantHi BlueNGray,
One of your files was too big and couldn’t be uploaded (“CPU-Usage-hw-decode-disabled.png”).
Can you please send it by email to forum[at]nomachine[dot]com, making sure to reference the topic in subject ?
Thank you!
BilbotineParticipantHi Frank,
Thank you for your feedback.
Can you please enable logs, reproduce and send us by email to forum[at]nomachine[dot]com, making sure to reference the topic in subject ?
Furthermore, can you show us these keys
PhysicalDesktopAccess PhysicalDesktopMode PhysicalDesktopAccessNoAcceptance
BilbotineParticipantHi khawkins.sfdc,
Thanks for your post, we tested and reproduced a similar problem with version 7.10.1.
That said, upgrading to the freshly released version 8 seems to fix the problem.
The universal package for Mac is suitable for both Intel and M1 processor, please try it.
Your feedback will be appreciated!
BilbotineParticipantHi jdslavin,
From a terminal you can check with nxserver –useredit USERNAME –screensharing yes. This applies to a specific user.
Also, in the server.cfg check that PhysicalDesktopSharing is set to β1β. This key applies to the whole server.
Does this help?
BilbotineParticipantHi MastaG,
Thank you for the logs, we’ll have a look and come back to you soon.
September 15, 2022 at 07:42 in reply to: Unable to connect my Windows PC using different network #40136BilbotineParticipantHi Yuan,
Please check our article “How to connect over the internet to NoMachine behind a NAT router” for such a connection problem: https://kb.nomachine.com/AR10R01099
Let us know if it does not solve your problem π
BilbotineParticipantHi BlueNGray,
You can check the following link to find out more about collecting usage on Windows:
Is that what you are looking for, or did I misunderstand you ?
We look forward to your update on the CPU usage π
Best regards,
September 14, 2022 at 07:37 in reply to: “Server capacity: reached for user” error when user is already logged in #40124BilbotineParticipantHello lavadrop,
To make sure this is the same issue, can you please send us server logs to forum[at]nomachine[dot]com, making sure to reference the topic in subject ?
If needed, hereβs the procedure to collect NoMachine logs: https://knowledgebase.nomachine.com/DT11R00181
PS: if you tried to attach logs or a screenshot in your post, it unfortunately failed – you can share them by e-mail.
BilbotineParticipantHi Paul,
Thank you for the screenshot. Can you please confirm what is the OS on server and client sides ?
BilbotineParticipantHello sloke123,
We are trying to reproduce your problem with that VPN. We will come back to you soon if we need more information or if we have a solution.
If you have an update on your side, please let us know.
BilbotineParticipantHello MastaG,
Thank you for the logs; having reviewed them, we would like you to:
enable the logs in node configuration file (node.cfg),
restart the nxserver,
reproduce the problem,
and then share .nx from home dir of user on server side.
using nxserver –debug enable, nxserver –debug –collect should help to create the package with logs.
As previously, please send us the logs by email.
Thank you!
-
AuthorPosts