Forum Replies Created
-
AuthorPosts
-
BritgirlKeymasterOn the server side, for example with Cloud Server (and then adding your node machines such as Enterprise Desktop or Workstation hosts) as your users’ single entry point, you disable direct access to node and configure the Cloud Server to allow specific access for specific users.
You can also use custom scripts which are run on the server upon a given event. I’m not sure what server product you are using, but all the guides in the documents section have a chapter about custom scripts (Server Automation Interface).
Alternatively, you could block specific client-side IP addresses on the corporate firewall and allow only those that you want to come through.
February 5, 2024 at 10:29 in reply to: Could not update ICEauthority file /run/user/1000/ICEauthority #46932
BritgirlKeymasterIt seems to be a problem of permissions on the /run/user/1000 directory?
BritgirlKeymasterWe would need to see the complete server-side logs so we can check to see why you are encountering this issue. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.
Steps to reproduce and some additional details about your set-up (OS and version, for example) would also be useful.
BritgirlKeymasterHi, are you able to send us the complete server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
BritgirlKeymasterSounds like a video driver issue, something in the update you said you just did. Can you try disabling hardware decoding in NoMachine on the client side (the machine you are connecting from)?
First exit the Player on the machine you are connecting from by right clicking on the !M icon in the sytem tray and clicking Exit Player.
Edit %USERPROFILE%\.nx\config\player.cfg and set:
<option key=”Enable hardware accelerated decoding” value=”false” />
Then create a new session and check if you still have the same issue.
If you do, set the same key to:
<option key=”Enable hardware accelerated decoding” value=”disabled” />
and create a new session. The first setting disables the use of HW decoding but the codec library is still loaded, while the second settings disables completely the HW decoding. Let us know the results.
BritgirlKeymasterNoMachine doesn’t yet use native retina resolution as explained in the topic that you mention. Support for retina is in the development roadmap, however. What we would expect is that the remote session does not have the same resolution as the local desktop of the mac i.e what you see in the session would be of a lower resolution.
BritgirlKeymasterHi, thanks for submitting your report. This is a known issue. You can track the Trouble Report’s status using the following link:
The Apple menu covers the NoMachine sessions when it’s at fullscreen
https://kb.nomachine.com/TR03U10808
BritgirlKeymasterAlso, I have read a little about NoMachine Network (or some such thing) that is supposed to do away with depending on IP addresses to connect. Where can I find more info on this and how to apply this, if it even applies in my free setup?
Network will be available in version 9, and will remove the requirement of having to know the public IP address of the NoMachine host when connecting over the Internet. Network will also remove the need to map ports and configure your router. Network will be compatible with the free version as well. The only requirement to connect over Network instead of TCP/IP will be to have a Network Subscription.
BritgirlKeymasterCan you submit the screenshot of the Updates section of the Settings you have on your macOS?
If you prefer not to do that, I suggest you uninstall and reinstall using the latest version from our website.
January 30, 2024 at 17:45 in reply to: Fedora 39 + Wayland + Nvidia RTX 4090, gray screen with Wayland #46870
BritgirlKeymasterHi, the logs were helpful thanks and we were able to pinpoint the problem – an error related to the EGL library. The fix didn’t make today’s software update, verison 8.11.3, but will be in the next one 😉
January 30, 2024 at 17:19 in reply to: Cannot connect Windows network drives to NoMachine Terminal Server session #46868
BritgirlKeymasterIs not currently possible to share Network drives within the session and so you should not be able to see, in your case, Z:. So it can be considered a bug. Not supporting them was a design choice a few years back due to complexities of handling the mountpoints. That said, we’re investigating whether it’s possible to add support for Network drives for a future version.
BritgirlKeymasterWe can’t reproduce this. Is disabling xscreensaver an option?
Are these physical machines?
With toolbar at bottom of display works normally
With toolbar at top of screen mouse <clicks> are not seen, even mouse-hover not seen.
Can you submit a couple of images showing this?
We released an update today, 8.11. Install that and then reproduce the problem.
BritgirlKeymasterIt’s strange that Server settings just suddenly disappeared. That would only happen if you removed the software and then made a new installation with Enterprise Client package. For example, you uninstalled NoMachine and then downloaded the Enterprise Client (no server included) and installed that?
From the system tray, click on the !M icon and select ‘Main window’ and go to Settings. You say you don’t have the Server component there, so click on Player and go to Updates. What is written there? If you don’t have any icon in the system tray, open NoMachine from your programs menu. You can also take a screenshot and submit here.
By the way, we also released 8.11.3 today, so you could uninstall your current NoMachine package and make a fresh installation using the NoMachine package for Mac.
BritgirlKeymasterHi,
thanks for your suggestion. Indeed it’s not currently possible to copy and paste non-text. At the moment, what you can do is either use drag and drop (drag from any folder whichever side will drop the file on the desktop), or the file transfer tool from the NoMachine icon in the system tray. The downside, as you wrote, is you have to have the image physically on the system to be able to transfer it and then you have to remove it by hand. Good news is that we are re-evaluating adding support for copy/paste of content such as images, with the possibility of adding it in an upcoming version. Current development priorities mean that it’s not something for an imminent version, but we’ve taken note of your request 😉
January 24, 2024 at 09:19 in reply to: Not able to click on tabs on remote system after recovering from sleep on local #46828
BritgirlKeymasterCan you submit a brief recording of the behaviour?
-
AuthorPosts
