Forum Replies Created
-
Posts
-
Hi,
What you most likely need is one of the products from out Terminal Server for Linux range. This will let you run a virtual display (like RDP) even if you are logged in locally, what we call a virtual desktop session. “Workstation” should suffice if you want it for just for yourself, though you can get versions which cater for larger environments. See here for more details: https://www.nomachine.com/comparison-terminal-server-products.
Enterprise Desktop allows you to connect to the physical desktop/display. To connect to the desktop you need to use the same credentials that you would normally use to log in locally. Each user connecting will see the same desktop. If you have a monitor attached to that computer, whoever is sitting in front of it will see what’s on the screen. So you should enable screen-blanking on the host you want to connect to. See here for more details: https://www.nomachine.com/DT10O00155#2.2.
Further reading:
What is the difference between physical desktop connection and virtual desktop connection?
https://www.nomachine.com/AR10K00700After serveral attempts we are still not able to reproduce the problem. The only last try is to do what we suggested before: you didn’t tell us if you had tried changing the port.
What happens if you shut down the server completely the instead of just stopping and then try with netcat again?
This is not the normal behaviour. We opened a Trouble Report after we were able to reproduce it. You can ignore this warning in the meantime. Please use the ‘notify me’ service to know when a patch has been released.
During system shutdown where nxserver is running a warning is issued that “Other users are logged in”
https://www.nomachine.com/TR04R09618Thanks for the feedback. We will certainly take a look at the documentation on how to improve it.
Let’s handle each of the points you raise separately.
1) UPnP – When the NoMachine (server) computer is behind a NAT router or a firewall, NoMachine tries to use the UPnP or NAT-PMP protocol (depending on what is supported by the router) to retrieve the public or external IP of the host machine where it’s installed and configure the router to allow a NoMachine client to connect from outside of the private network. The UPnP or NAT-PMP port mapping service can work efficiently only when it’s enabled in the server configuration, the router supports UPnP or NAT-PMP, UPnP or NAT-PMP is enabled and the router accepts UPnP or NAT-PMP commands for enabling port forwarding.
Those users who have a double NAT doesn’t mean it’s impossible to connect. It means additional configuration is required, which is not always possible especially if one of the routers is not your own.
We fully understand that this is not an ideal scenario for the less tech-savvy user and for this reason we will be releasing NoMachine Network which will eliminate the need for knowing the IP address of the computer and users won’t need to enable port-forwarding on their routers. You can read more about this here: https://www.nomachine.com/FR07J02731.
2) Key based authentication with NX protocol (article AR02L00785), i.e so if you’re a user that doesn’t want to use a password to connect but prefers to use an SSH key certificate when connecting to the server, then this article is for you. It’s a way to authorize the user from whatever client machine they may be connecting.
3) EnableNXClientAuthentication – By setting that to ‘1’ only the devices which have a valid certificate are allowed. This key allows you to specify which client machines can connect. All other connections will fail. So that article “How to enable SSL client authentication for connections by NX protocol” (AR10M00866) is ideal for environments where many client devices are connecting and administrators want to lockdown access to a per-user or per-host basis. It’s not for your average user and hence that article mentions multi-node, clustering and other advanced functionalities.
4) Protocols and ports. Take a look at the article here: https://www.nomachine.com/AR01L00770 (NXD and the NX and UDP protocols). The rules would be like this:
Rule name: NoMachine
External port: 4000 or any unused port that you prefer
External IP: blank
Protocol: It depends on your router version, but it should TCP/UDP or “Both”
Internal port: 4000 (NoMachine’s default)
Internal IP: local IP of the NoMachine serverRule name: NoMachine
Local port: 4000
Local IP: your NoMachine server’s local IP
Action: Accept in both way
Protocol: It depends on your router version, but it should TCP/UDP or “Both”
Remote port: 4000 or any unused port that you prefer
Remote IP: blankLogs received.
I assume that you can connect to the remote computer whilst on the same network? To do that you should use the local IP that we can see in the logs 192.168.1.xxx and try to connect whilst both PCs are on the same LAN. Does that work ok?
For access from outside, from the logs we can see that you have a double NAT, the same scenario as this: https://forums.nomachine.com/topic/double-nat-remote-through-internet (so there are two routers involved and you need to configure port-forwarding rules on both routers to tell the routers what they need to do when you try to access using NoMachine). You are using an external IP of 179.xxx.xx.xxx on port 24244 so you should try forwarding port 24244 to the IP 192.168.15.146. If you tell me the router models, I can try and point you in the right direction for what rules you need to set.
Sorry, I thought I had put a link on “client logs” to that document…. Yes, it’s unticked by default. Having it ticked would mean the majority of users fill up their NoMachine folder with log files that they probably don’t need.
When a client connects to a remote host, it stores certain information in the session file. It is enough to connect once to be able to store what OS the client connected to. Next time you open NoMachine on your client, the recent connections panel will show the details of the session, including the OS, which was started.
The client logs will store the same information.
Did you reboot the computer after installation? Logs would be useful at this stage (not the session file) of the server Windows host (the computer you want to connect to). Please follow the guidelines here: https://www.nomachine.com/AR10K00697 You can submit them directly forum[at]nomachine[dot]com making sure you reference the topic title as the subject. Thanks!
Session history is available. For more details see here: https://www.nomachine.com/FR03M02882
sudo /etc/NX/nxserver --history --client-platformDisplay Username Remote IP Session ID Date ------- --------- --------- -------------------------------- ------------------- 1003 nomachine 10.0.5.43 232E14CB00F250F404170DF788A5FFB7 2020-04-07 15:42:33 Status Node Type Client platform Connected localhost:4000 shadow linux--history [<sessionid> | <username> | <node:port> | clear] [--client-type] [--client-version] [--client-platform] [--stats] [ --file <file>]Cloud Server would need Enterprise Desktops added to it. Each PC you have must have Enterprise Desktop installed. With the implementation of the following Feature Request (coming very soon) it will be possible to see if there are users attached to a specific machine.
Displaying the number of users connected to the child servers
https://www.nomachine.com/FR03R03953Terminal Server products are for Linux only. Using Enterprise Terminal Server and adding on Terminal Server Nodes you can achieve the entrypoint that you wish to set up and then by setting profiles you can decide which users can access which nodes, which type of desktop and other permissions. It’s a very powerful product. If you don’t want to load-balance, you can activate the ‘manual-node’ selection of the nodes. This means that all users, or only some specific users, will be able to choose on which node to create their virtual Linux desktop.
In this case, could each node represent a ‘classroom’ maybe? Each user could have their own desktop session.
Send the screenshot to forum[at]nomachine[dot]com using the topic as the subject of your email. We’ll then make sure it’s uploaded to your reply above. Thanks
I assume you are using the latest NoMachine software, correct? What version of Windows are you using? Have you done a recent update of the OS?
Can you try updating to the latest version?
Also, on the version you have installed, did you disable the key AND uncheck the box “Advertize this computer…” in the player’s services panel on each host?
And restarted?