Forum Replies Created
-
Posts
-
Hi, we are not aware of issues with sharing remote drives from Debian to Windows.
You say you updated. Was disk sharing working for you in the earlier version?
Logs from the server side would be useful. Enable debug on the Debian machine, reproduce the problem and then gather up the logs. You can send them to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email.
$ sudo /etc/NX/nxserver –debug –enable all
$ sudo /etc/NX/nxserver –debug –collect(from the following guide https://kb.nomachine.com/DT07S00243, Collect server side logs automatically)
By default all desktop sharing connections must be explicitly accepted to proceed, but I don’t know if you perhaps changed something on the server side.
How are those users authenticating? With different system accounts or are they all sharing the same login as the owner of the desktop who is already logged in?
On the server machine, go to Server settings -> Security -> User acceptance and check which boxes are enabled. You will see:
1) Don’t require acceptance if the user logged in as system user (by default the box is empty)
By enabling/ticking that box, users with a valid account on this host can connect without the need of the desktop owner’s approval. This configuration is suitable for unattended computers.
2) Don’t require acceptance if the user logged in as the owner of the desktop (by default the box is ticked)
If all users connecting are using the same account as the owner (e.g everyone connects using the name “myteam”) and you want everyone connecting to be authorised by the owner already connected, you must leave this box empty.
If you have Workstation installed (so NoMachine virtual Linux desktops are supported), there will also be a section for virtual desktops in the same panel:
Virtual desktops
Don’t require acceptance if the user logged in as a system user(empty/disabled by default)Don’t require acceptance if the user logged in as the owner of the desktop (enabled by default)
More about this is available in the relative guide:
https://kb.nomachine.com/DT07S00237#2.5
Perhaps you can attach a screenshot of of the “User acceptance” section in the Security settings panel of the server?
behaviour witnessed between 6.18.1 and 6.9.2 as I already mentioned.
It is not clear what behaviour you witnessed which is different. In theory, if your subscription expired just after the release of v6.9.2 you would be able to install 6.9.2 updates but not 6.18.1. If your subscription expired just after the 6.14 release, the same concept applies. You would be able to install 6.14 but not 6.18. However, I don’t know the details of your subscription, so can only give you examples.
If I only had a copy of 6.14.1 to test that theory, but it seems it is gone…But 6.18.1 is still up…
The customer area shows customers the current version available for download. It is not a repository of all releases. So if your subscription is valid for v6, you will see the latest release, which is indeed 6.18.
I suggest that you contact the team via the website if you are having problems with downloading or you think your customer area is showing you the wrong information.
If we know your subscription expiry date, we can tell you what updates you were entitled to access and install, and provide a private link if you did not download them when your subscription was valid. A subscription must be kept valid to maintain access to the support sections of your customer area, namely the updates and technical assistance sections.
/Britgirl
Hi,
please clarify:
what OS version do you have on the client and on the server side?
what NoMachine products and version do you have installed both sides?
Thanks.
Hi Majkl, thanks for the additional info. We’ll wait for the logs. Once you’ve got debug enabled, reproduce the problem(s) and then
%ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collect🙂 Submit everything to forum[at]nomachine[dot]com.It’s not clear what your question is 🙂
There are two proxy configurations, one global (in Player Settings) and one per-connection (in Connection configuration). You can configure a proxy per session by editing the connection. Select Configuration, check “Use custom proxy configuration for this session”, click Modify and configure it according to your requirements 🙂 This does not overwrite what you already set in the general configuration in Player settings -> Security -> Proxy.
Hi, thanks for noticing and alerting us 🙂
The features tables have been corrected.
Client redirection per-user and per-IP is available in all products with the exception of the Free Edition. RDP support is not available in the Workstation and Small Business Terminal Server.
Majkl, we will need the same logs that we requested also from you from the affected Windows NoMachine server 🙂 Enable debug, reproduce the problem and zip up the logs. See my earlier reply for the commands.
Please also confirm the following because it’s not clear from what you wrote:
NM7 ED on Windows showed no issues
NM8 ED on Windows 32bit – did this show the issue or not?
NM8 ED on Windows 64bit – did this show the issue or not?To be honest, both of these worked for us:
unlock-session [ID...]-> Screen unlock one or more sessions
unlock-sessions-> Screen unlock all current sessionsAnyway, thanks for following up. You can maybe disable automatic screen lock to avoid this from happening in the future.
Unfortunately, we cannot give a definitive ETA. Development priorities are currently on NoMachine Network (www.nomachine.com/network) and v9. Work on the feature you are interested in will start after that.
The logs do not show the problem and the .nx folder is missing from users home.
So let’s do it this way:
Follow the instructions here: https://kb.nomachine.com/DT07S00243
To enable debug on Windows, open a CMD console as administrator:
> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --enable allReproduce the problem and then:
> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collectSend as before. Thanks!
Hi, it’s possible to use the format “192.168.1.180:4000” in its entire form in the Search field if you want to start a connection without going into “Add”. Typing or pasting in the Search field of the Machines roster will 1) find your connection if you have configured a similar one already or 2) ask you to connect to new host or configure connection to new host.
If you are in the Add section, then you must separate the URL from the port 🙂
Hi, working direction logs were empty. The first set show that sessions start ok. However, it’s possible that you have the same issue that was discussed in another topic, in that the IP address you are using to connect is not correct.
Please take a look at my answer here: https://forums.nomachine.com/topic/how-to-make-nomachine-update-target-computer-ips#post-39467. Go to the Player’s Configuration panel of the connection and check if there are multiple entries in the Host field. Do you see multiple entries? Select another item from the list for the connection and then try to connect.
To Doug, we’re analyzing all the information you sent us and will come back to you soon.
To MasterOfus, your issue could be a different issue and so we will need the full set of logs from the Mac server. Check here for details: https://kb.nomachine.com/DT07S00244 and submit to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.
To raleighr3, the logs from your Mac server would also be useful as per my request to MasterOfus. Thanks everyone.