Forum Replies Created
-
Posts
-
In version 3.5.0 ‘shadow session’ referred to both sharing the physical desktop of another user, and sharing the X11 desktop. In version 4 it’s the same concept, but you don’t configure the GUI to run a ‘Shadow’ session. Now most of the session configuration happens at runtime based on information provided by the server after authentication to the server has taken place. This includes the type of session (shadowing of the physical screen or creation of a new virtual desktop), the X client or desktop environment (GNOME, KDE, custom session, etc.), the display resolution, the configured printers and so on.
The free version allows one connection to the desktop. So anyone connecting to the computer from another device will count as one connection. To allow others to connect too, you will need Enterprise Desktop.
If I have understand correctly, you want users which are connecting to the physical desktop (sharing it in other words) in view-only mode.
This is on the server side, so the machine which is hosting the Enterprise Desktop software.Open the Server preferences and check the box ‘Require permission to let the remote users interact with the desktop’. That way they will be in view-only mode when connecting from their Player machines to your Enterprise Desktop host.
NoMachine software lets you access your remote computer whether it’s Windows, Linux or Mac. You can install it on the physical machine or on a VM. You can install it on your Windows VM already running on your Linux server (you will need a hypervisor to do that), and you will be able to get remote access to that Windows VM.
If you choose one of the products with the terminal server functionality (for Linux) you can run multiple instances of the Linux desktop on the same host.
I suggest you check out the following:
What can I do with NoMachine? https://www.nomachine.com/AR10K00716
What do I need to use NoMachine? https://www.nomachine.com/AR10K00723
How to get started with NoMachine – https://www.nomachine.com/getting-started-with-nomachineThree joined pipes indicates a computer that is being broadcast on your local network: See figure 3 in the tutorial here: https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network.
If you are the admin of that computer showing up on the network, you can disable the broadcast feature using the same tutorial. If you are not and you don’t want to see broadcast computers on your LAN, you can check the box in the Player settings ‘Don’t show other computers on the network’.
(Player preferences -> Appearance).You have enabled broadcasting to let other computers discover you on the local network.
There are two ways to disable the ‘Advertize on the network’ feature. Uncheck the box in Fig 1 in the tutorial here:https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network
Or you can disable it in the server.cfg file on the server host:
# Enable or disable broadcasting the required information to let
# other computers discover this host on the local network.
#
# 1: Enabled. Other computers on the local network can find
# this host machine.
#
# 0: Disabled. This computer cannot be found on the local
# network but it’s still reachable by providing its IP
# or hostname.
#
#EnableNetworkBroadcast 0A restart will be required for it to take effect.
I know that issue 1 is a bug: https://www.nomachine.com/TR06M05548. You can sign up to be notified of an official fix.
For the second problem, are the credentials you are using in the browser to log in to NoMachine the same as in Login Window? I.e are you using the same user account? If you are using a different account when you get to the Login Window, disconnect is the correct behaviour. Disabling PhysicalDesktopAuthorization 0 in server configuration file could help.
@wagometer, send them to forum[at]nomachine[dot]com. Please put the title of your topic in the subject. Thanks.
Hi Michelle,
an IP address starting with 192.168.x.x is typical of a LAN network, and this is what you use to connect from one Mac to your husband’s Mac at home (you are on the same network). Using a LAN IP address in the ‘Host’ field when connecting to any computer over the Internet won’t work. You see something like this in your first set of numbers, I take it.
The second set of numbers is what you should use to connect to those computers from another machine over the Internet. The last five digits is the port. (You can see an example in Screenshots 1 here: https://www.nomachine.com/getting-started-with-nomachine and https://www.nomachine.com/getting-started-with-nomachine#internet.
To connect to your Windows PC you need this second set of digits. Your Windows computer is showing only the LAN IP address. This is ok for connecting to it, let’s say, from a colleague’s computer in the office.
It can be that your office router doesn’t support UPnP. Or that our UPnP doesn’t support your router 🙂 Anyway this shouldn’t affect your ability to connect, even from the outside. Many routers that don’t support the query for the external IP still accept the commands required to enable port forwarding. If that’s your case, you will have to configure the port forwarding by using the router admin interface. This is normally a Web application running at http://192.168.1.1. Is there someone at the office that can do this for you? By default the port is 4000 but it can be changed to another.
NoMachine 5 (coming soon) will allow you to connect to your office PC without having to know this IP address. This would be ideal in your case.
Hi, we’ve reproduced and have opened a Trouble Report.
https://www.nomachine.com/TR06M05561
You can sign up to the ‘Notify me’ to know when a fix is available.
@jy can you follow the instructions above and let us know if that helps.
All NoMachine servers and nodes on Linux and Mac OS X hosts are affected and you are advised to update. So this means if you are running a Cloud Server, you need to update it; if you are running a Terminal Server Node, you need to update it; if you are running an Enterprise Desktop, you need to update it. Enterprise Client is not affected, but we recommend you update clients in order to keep versions aligned.
The logs are from the client. What we need are the logs from the server side, and additionally the .nx directory client side. Please follow the instructions in the article https://www.nomachine.com/AR07K00677. They will possibly be too large to attach here, so you will need to send them to forum[at]nomachine[dot]com.
Thanks