Forum Replies Created
-
Posts
-
You don’t mention the NoMachine product, this would allow me to understand better if you are possibly connecting to a virtual desktop session or to the physical display of the Linux host.
Anyway, if you are connecting to the physical display of the remote machine with NoMachine and the apps/utils are not starting on the physical display itself, it would indicate that it’s not a problem with NoMachine but with your system.
Jeser, the Free Edition, for access to the physical display, can be configured to show the dialog if you are logged in or not show the dialog at all. If you configure it to show the dialog, in your case when sharing the same username, it will always show. That means if no one is logged in already, when you try to connect, no one can accept the request to connect.
With regards to the Workstation, which is for virtual desktops on Linux, we’re checking for a possible problem with web sessions and will come back to you.
You previously wrote: I want anyone with access to the URL to be able to open the remote desktop directly from the URL.
I explained that it is not possible highlighting the security reasons.
Can you tell me how to save the password in the .nxs file or include the password into the URL?
Including the password is not possible as I already mentioned. To save the password, you can use the checkbox to save the username and password during the first connection. The next time you use that link in your same browser, you won’t be asked for the password. But, if you pass that URL to a friend and they use it in their browser, the first time they connect, they will require the username and password. They can tick the same checkbox to save and from the successive login, they won’t be prompted to input the password.
But when I visit the site (https://SERVER:PORT/?default), I still need to enter a password, which means there is no automatic login.
Can you provide the exact steps you are taking to connect? Also, knowing what OS you installed which NoMachine product and what browser you are using would be useful for us to check.
I forgot to ask what NoMachine product you have installed on the Red Hat server. Is it the free version, something else? Is it the latest version?
What do you mean when you mention “I removed all those terminal sessions” in NoMachine? How did you remove them?
Can you start a normal NoMachine session to the RH server at all?
Is this a headless Linux machine? I.e is it without a monitor or do you have a monitor attached? Are you able to physically go to it and see if the desktop is running without problems?
Hi,
USB tablet forwarding not working with Windows 10 pro
was there an error shown? If so, what message?
Can you give details of what is not working exactly?
Logs of both sides would be useful in this case. Please take a look at the following document and follow the instructions on how to get the logs of the server and the player device:
https://kb.nomachine.com/documents
Please send any attachments via email to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
It’s not clear what the problem is that you have. Please confirm:
1) what OS version you are connecting from? Windows, but which version?
2) what NoMachine product & version is installed on the client device you are connecting from?
3) what OS is on the server you are connecting to (it looks like Red Hat from the image, but what version)
4) what is the desktop environment on the Red Hat server ?
NoMachine was working initially but when I removed all my terminal windows it doesn’t launch a new terminal windows any longer.
What do you mean that you removed all your terminal windows. What are the steps you took?
NoMachine should support the native MacOS full screen mode so it can follow the standard system settings.
Yes, that’s right, hiding the menu bar is a workaround. Supporting native macOS full screen mode is planned however. We have had other development priorities recently, and that’s why we’ve not been able to dedicate time on implementing support for it, but we’re working on making it available as soon as we can, in line with our other development commitments.
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???