Forum Replies Created
-
Posts
-
You cannot force a remote connection to the physical display whilst the checkbox for “Require permission to let remote users connect” is checked in the Security settings of the server (the PC you want to connec to). Take a look at the tutorial I passed to you in your other topic, and you should also look at the Guide here: https://www.nomachine.com/DT10O00155#2.2. If that checkbox is ticked, it is assumed the owner is physically sitting in front of the computer (server) and can accept the incoming connection when prompted.
The first checkbox you see in the Security tab lets you decide whether the server can accept the incoming connection automatically or ask for the desktop owner’s authorization. Quoting the guide:“Select Require permission to let remote users connect when the explicit approval of the desktop owner is necessary. This option applies only to connections to the physical desktop when the connecting user is not the desktop owner. If the incoming user is the desktop owner, he/she will always connect and no request for authorization is issued.”
The request for desktop owner’s authorization is enabled by default. If the owner of the desktop has left their desk, then you should ask them to configure NoMachine access accordingly in order to share their computer with you.
@Acki, please refer to https://www.nomachine.com/protecting-the-host-screen-during-a-remote-control-session
Section “Enabling automatic screen lock when disconnecting”. By default, it is disabled.
The display of a remote computer can be protected further by enabling the system’s own screen lock which will be activated automatically as soon as the last NoMachine user disconnects.
- Select the ‘Security’ tab of the Server preferences UI.
- Check the box ‘Lock the physical screen on disconnect’ (Fig. 4).
You can turn this feature on or off at any time. You will need to provide the administrator’s username and password in order to enable it or disable it. Is the screen locked when you disconnect once you’ve checked the box?
2019-01-07 21:24:17 597.201 36547 NXNODE ERROR! Application terminated too early.
This means that the application run by NoMachine node (i.e. the desktop environment or a custom application) terminated immediately after being started. This can happen when the command specified for launching the desktop or the custom application is not appropriate. So you need to check this. Please refer to the article here:
How to solve ‘session negotiation failed, application terminated prematurely’
https://www.nomachine.com/AR08N00898We opened a Trouble Report for this particular issue.
Improve retina support for NoMachine graphical user interfaces
https://www.nomachine.com/TR12P09056NoMachine Network is in the last phase of development. I can’t give you an exact ETA. We are happy to add you to a beta or testing program – you can also sign up to receive notifications/updates regarding this functionality using the ‘notify me’ check box on the Feature Request page.
Hi Mitof,
sorry you couldn’t find the information that you were looking for. Submitting some feedback to the webmaster (contact us form in the footer) would be of help so we can make some improvements to the right pages 😉
I would suggest that what you’d need is Enterprise Desktop. This will give you access to the physical Linux desktops you mention.
From what you’ve described, what would be a better fit is the Network service we are creating. More about this is available here: https://www.nomachine.com/FR07J02731. With Network, you will be able to access your remote computer without needing to know its IP address. So once installed on the remote host, you won’t have to worry about whether the computer is sitting behind a firewall, or whether certain ports are open, and so forth.
Hi ratata,
we’ll definitely look at how to improve tips and documentation (and make it easier to find), but we’re glad to know NoMachine is now working correctly in your set-up.
p.s. In your original post you asked “where to look to see what codec that was used in a current session.” Apologies for not answering earlier. When you connect, open the menu, select Display and then ‘Change settings’. See section 5.7 of the guide here: https://www.nomachine.com/DT07M00087.
Keep using NoMachine! 🙂
Hi, we’re reproduced the problem and are investigating further to find a suitable fix.
At this point, it might be an idea to open a support ticket in your customer area (you mention that you’ve purchased a subscription), that way you’ll also be able to submit more information without worrying about it being made public as well as get access to any hot fix we make.
Hi,
Can you tell me which topic thread you are referring to?
Automatic disconnect has been available since version 4. Check out the instructions on how to set it here:
– How to enable the auto-disconnect feature in NoMachine 4 or later
https://www.nomachine.com/AR01H00551Hi,
UPnP or NAT-PMP is required for automatic port-mapping. Without UPnp, it will be necessary to configure the router manually and open the requested port. For example if you use NoMachine, the free version, you will need to open port 4000 on your router and map it to the public IP address of your NoMachine (server) host.
Only on client side we use other vendors’ libraries. More info here: https://www.nomachine.com/AR10K00696
Does NoMachine make use of H264 codecs made by other vendors when present in Windows and therefore also globally registered or is it just the H264 codec made exclusively for NoMachine that will work? I’m asking because I couldn’t find where to look to see what codec that was used in a current session.
We use other vendors’ libraries only on the client side. More info here: https://www.nomachine.com/AR10K00696.
On the server side it must be the library we ship or compiled from our sources, as explained here: https://www.nomachine.com/AR09M00863.Yes, that’s right. I was about to reply but you beat me to it 🙂
You need a rule like this
All UDP UDP 0 – 65535 {Client_Public_IP}Attachments:
Something to remember is that WebRTC uses 80 or 443 for signaling if using websockets or not. 3478 is the default port for communicating with STUN/TURN servers but some might be configured to listen to 19302-19307 (Google’s STUN), 5349 (TLS), 80 or 443. And a WebRTC P2P connection will use random port in range 0-65535 for sending data.
Hi, Mojave needs you to grant special access to external programs in order to control the Mac from remote as well as access its microphone and camera. (more about this is here if you’re interested: https://www.nomachine.com/AR10P01001)
It could be that you didn’t enable NoMachine correctly during installation? You should see something like this (see attached image) if you go to your Security & Privacy settings. Check that nxnode and NoMachine programs are in the list and that they are enabled.
If this doesn’t help, let us know.
Attachments:
Hi, just for clarity: Windows ‘A’ (don’t know the version), Windows 7 (‘B’ ) and RedHat computer we’ll call ‘C’.
Am I right in assuming that when you connect from B to C the performance is fast, i.e they are the same hosts you mention in Set-up 1?
If so, that would mean that the problem is WRD, not NoMachine. A possible assumption about any slowness being caused by WRD could possibly be because it intercepts primitive graphics and not images in order to draw the content of Windows applications (?) Nxplayer draws the remote desktop as images which Windows Remote Desktop Protocol can’t compress optimally.
Out of curiosity, what happens if you connect from A to B with NoMachine and run NoMachine from within your NX connection?
