Forum Replies Created
-
Posts
-
Hi, apologies for the delay. We are investigating a possible problem that occurs when switching to “Resize remote display” from “Scale to window” mode. In the meantime, can you do the following quick test?
1) start a brand new connection
2) once connected, open the menu (Ctrl-Alt-0)
3) enable “viewport mode” followed by “resize remote display” (so click icon 1, then click icon 3). Close the menu.
4) is the text still blurred?I believe it’s a per-user setting, but it’s something you could also check with macOS’s own instructions.
Sorry for the delay. We’ve tried reproducing without success.
Could you send us the logs of the server? Send us also the player for safe measure. Please follow the instructions here: https://kb.nomachine.com/DT07S00243, it includes the instructions for both server and client sides. Then submit them all to forum[at]nomachine[dot]com. You can use the topic’s title as the subject of your email. Thank you.
You could use Custom Scripts maybe?
#
# Specify absolute path of the custom script to be executed before
# the user logs in. The script can accept remote IP of the user’s
# machine as its input.
#
# E.g. UserScriptBeforeLogin /tmp/nxscript/script.sh
#
UserScriptBeforeLogin “/usr/NX/script.sh”So you would implement a script which compares the remote IP to what’s on the ‘white or black list’ and then exit 0 or 1 depending on the result.
You can find information about custom scripts in the installation and configuration guides of the product you are using, for example: https://kb.nomachine.com/DT07S00246
Hi,
25510 25510 2023-04-03 13:36:24 398.414 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –isadmin myuser’ with pid ‘25543/25543’ finished with exit code 1 after 0,006 seconds.
‘nxexec’ is checking who the user is, in this case, its
--isadmin myuser, and reports a value on the basis of who that user is: ‘0’ for admin, ‘1’ if it is not admin. By the way, this will be “silenced” in version 9 in the NoMachine standard logs.Your second question…it seems to be a scanning attempt on a non-standard port 62221. NoMachine does not use this port by default. Could it be that this port was previously used by some other service, previously reported as a security issue, and your scanners are checking it?
It looks similar to:
USB devices stop working updating from v7 to v8 on Windows
https://kb.nomachine.com/TR12T10708.For now, what you can do is disable the drivers on Windows. Please follow the instructions here:
How to disable or uninstall NoMachine USB drivers on Windows
https://kb.nomachine.com/AR12O00955Doing so would require that we include the password into the URL, the URL that you need to hand over to permit others to connect to the same server. The password would be then visible to others, for example in the URL bar of the browser or in the “URL file”. We chose to not do so for security concerns. You also say: “I want anyone with access to the URL to be able to open the remote desktop directly from the URL”. But this would also allow anyone with access to the URL to see your password! We are working at this. The simplest solution is to use, for the password, the same “scrambling” algorithm that the Player is using to save the password in the .nxs file, but still the password could be easily “reversed”. I don’t know, we don’t know. This is still to be decided, what do you all in the forums think???
Hi, did you also try “Resize remote display” from the menu? Can you send us a screenshot of what you see, and what display modes are selected?
NoMachine uses Xwayland to get the cursor shape, but what you are seeing doesn’t depend on us. This is not related to a bug in NoMachine, but the fact that Wayland doesn’t provide a native API. Please see the article we have about using NoMachine with Wayland here:
Notes for connections to Linux physical desktops running Wayland
https://kb.nomachine.com/AR02P00969in particular section 4).
Hi timo, sorry for not following up sooner. The logs did not show anything conclusive, so what we would like to do is send you a debug version (which we’re preparing). Would you be willing to try it and extract the logs again?
Hi, I don’t see a reply from you with images. Did you see the “moderation dialog” when submitting your follow-up? In any case, please submit again.
I am a bit surprised that is the case as I would have assumed that you always can login as long as no one else created a session with the same credentials.
Let’s try and understand better what is not happening/not happening in your case.
Please attach a screenshot of the “User acceptance” section in Security of Server settings of the computer you are connecting to.
Also, tell us what OS and OS version is on that server side, and what NoMachine product you installed there. Thanks.
Hi, sorry for taking so long to get back to you. Your need is of course a valid one in the light of how you are using NoMachine (thanks for explaining by the way). We could come up with a “special mode” for your case. But it needs careful thought, also because there are no doubt more of these special cases like yours that we should consider as well.
The main problem is that we don’t know how to “plug”, to “fit” this particular use mode in the normal functioning of NoMachine. If the special mode was activated (like I explained earlier) you may end up using this computer, configured in this “special mode”, and so be unaware that somebody is “controlling” what you are doing, is watching you working whilst you’re doing your stuff, accessing your private data etc.
A possible way could be to distinguish between players and viewers. Those who are just viewing don’t need to see the notifications, after all they’ve connected to view the game, or they are watching the monitor content, not interacting with it.
Anyway, you’ve certainly given us food for thought and we’ve taken it on board.