Forum Replies Created
-
Posts
-
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.
On versions of macOS prior to Catalina, NoMachine installs without having to manually set permissions in the Accessibility section of the OS. You can read more about this here, but it should not affect you because you are running High Sierra.
https://kb.nomachine.com/AR11Q01061
The fact that you can start a connection is proof that NoMachine is installed correctly on at least one of the Macs 🙂
So, to connect, in your Add panel, you must put the IP address of the Mac (the NoMachine server) you want to reach. This is obtained by checking what NoMachine prints in the Server status panel for that machine. If the two computers are on the same network, perhaps on your home network(?), you should use the IP address that generally starts with 192.xx, like in the example in our Getting Started Guide, Fig. 2 https://www.nomachine.com/getting-started-with-nomachine.
The error you are receiving generally appears when you are connecting over the Internet (so the two computers are not on the same LAN). If that’s the case, you need to enable UPnP to allow NoMachine to automatically configure port-mapping. It might also be necessary to enable port-forwarding on your router. Please consult this article and follow the instructions there: https://kb.nomachine.com/AR04S01122.
I’m using the current consumer Linux products, but this has happened to me under Windows as well.
Do you mean that you can also reproduce it when connecting to Windows ? Or are you always connecting to Linux hosts and you reproduce it regardless of what OS you are connecting from?
If the server side is always Linux, do you have Wayland or X.org running there?
Hi, NoMachine uses a system user that is already created on the server side (System username and password). While it is common on Windows not to set a password, one must be set if someone wants to use NoMachine. This is due to Windows policies. A local system account is limited to using an empty password to console logon only.
You can find more about this subject in the following article : https://knowledgebase.nomachine.com/AR05L00802
“Due to Windows policies, a local system account is limited to using an empty password to console logon only. This is a security setting within the Windows OS and determines whether local accounts that are not password protected can be used to log on from locations other than the physical computer console. If enabled, local accounts that are not password protected will only be able to log on at the computer’s keyboard. This implies that connecting by NoMachine with an account having a blank password is not possible unless you configure your Windows to open the appropriate policy.”
NoMachine offers the possibility to connect without a username and password in Guest Desktop Sharing mode. This requires a user to be present on the computer you are connecting to because the connection must be authorised. I’m not sure if this is of interest to you, but you can read more about it here: https://www.nomachine.com/guest-desktop-sharing.
Yes, NoMachine installs correctly and works out-of-the-box on macOS 10.13. Are you using the latest version? It is not necessary to have to manually enable/set permissions on earlier versions of macOS.
If you have installed and not been able to connect or are seeing an error of some sort, please provide steps to reproduce and possibly a screenshot of what you are seeing. Thanks!
get output audio working by disabling autospawn in my local pulseaudio.conf
Good. Sorry for not mentioning that last time. This is what we also suggested in other topics, for example in
https://forums.nomachine.com/topic/message-cannot-find-the-default-environment-please-contact-your-system-administrator-on-latest-slackwareWith regards to the microphone, by default microphone is always disabled, so users connected to the desktop can forward their own microphone to the session by activating it from the NoMachine menu panel inside the session. Click on the right upper corner of the session window or press Ctrl+Alt+0 to open the menu.
Choose ‘Mic in’ icon button and click ‘Enable mic’. Sections 6.1 and 7 (Fig 18 and 19) in the following guide:
https://kb.nomachine.com/DT09T00266#7
Now users are able to use default microphone from the client machine in the session. To swap input device just click on ‘Change settings’ and choose other device in the ‘Microphone input’ section.
To use input device from server machine in the session – users need only to play sound from microphone by using some application like system voice recorder.
Does this help?