Forum Replies Created
-
Posts
-
Hi, we’ve reproduced this and a Trouble Report has been opened: https://www.nomachine.com/TR05L04413
We also have a patch available if you are interested in testing it. If so, can you contact us via the website for further instructions? 🙂
There is currently a bug in profiles which won’t let you correctly disable access to the node:
User can connect to a remote node even if access to that host is disabled by profile rules
http://www.nomachine.com/TR05L04399Once this bug is fixed the correct procedure will be to create user profile rules to forbid connections to specific Enterprise Desktops:
/usr/NX/bin/nxserver –ruleadd –class node –type <node:port> –value no –user <username>where <node:port> is the name of the node as displayed by the nxserver –nodelist
Because of TR05L04399, a solution is to use the redirect capabilities instead of profile rules. You can use the following command to redirect connections from the cloud server to the enterprise desktop based on the users:/usr/NX/bin/nxserver –useredit <username> –redirect <node:port>
where <node:port> is the name of the node as displayed by the ‘nxserver –nodelist ‘ command.
Redirection can be set also on-per client IP basis:
/usr/NX/bin/nxserver –hostadd <clientIP> –redirect <node:port>
Pre-requisite is that the user has a system account on the Cloud server host and on the Enterprise Desktop host. The username has to be the same. First of all add each Enterprise Desktop as a node of the Cloud server by running the following command from a console on the server host:
/usr/NX/bin/nxserver –nodeadd <IP of the Enterprise Desktop>
You can gather information on the node by running:
/usr/NX/bin/nxserver –nodelist
All the Enterprise Desktop you added will be seen by all users connected to the Cloud Server. Users will be able to choose which Windows desktop to join.
Can you please send server side logs to us?
%PROGRAMDATA%\NoMachine\var\log on Windows Vista, 7 and 8.
Please compress this folder and send to issues[at]nomachine[dot]com.
Did you accept to reboot your Windows as requested by the NoMachine installer? If not, try rebooting your machine now.
The free version of NoMachine provides one connection to the remote physical desktop. Two users cannot access that desktop at the same time from remote.
See here: https://www.nomachine.com/AR10K00716 and https://www.nomachine.com/AR10K00700
NoMachine doesn’t currently support virtual sessions on Mac. On Linux, yes. There are things that are trivial to do on Linux that are not as easy on OSX, especially when you are dealing with an OS where what you can do and what you cannot do is written in the EULA.
From your Android tablet, once you’ve installed NoMachine, you can connect to any computer which has NoMachine installed: Mac, Windows or Linux are currently the platforms that we support. Currently, there is no server version for Android. If our documentation is misleading, we will make the necessary improvements.
Yes, it does matter. My apologies, I completely missed that you had submitted this request to the Mac forum. My answer wrongly assumed you were connecting to Linux.
Can you give us more details about the sandbox you created? Also, are you trying to start the desktop via fast-user switch or are you already logged on?Hi Jim, you can achieve your goal with help of NoMachine for Linux package installed on your Ubuntu and NoMachine for Windows
package on your Windows computer.If your Ubuntu machine doesn’t have X running please remember to check our instructions for headless servers available at:
https://www.nomachine.com/AR10K00710
Can you provide more details about what you had problems with? You say you tried installing without success. It would be useful to know what difficulties you had so we can evaluate what improvements are required.
It sounds like you need to change the display of the X server which is shared by NoMachine. If you want to set a different display (the x server owned by your sandbox), change the node.cfg key: #DisplayDefault :0 by replacing the ’0′ with the correct number. Not sure if you’ve seen this:
https://www.nomachine.com/AR10K00710
Brannon, we will need logs from both the Windows client (when connecting to the Linux server), and then server side. Follow the instructions here (make sure they are the logs of the affected session 😉 ) https://www.nomachine.com/AR07K00677
I also suggest an update to 4.2.21 before trying to reproduce and sending logs. You can attach them here or submit to issues[at]nomachine[dot]com.
Can you clarify what you mean? Are you referring to “the image becomes very pixelated for 4-5 seconds after big screen updates”. Please provide all details of display settings, what you are connectin from and to etc as usual.
From the logs of your connection to server 4.2.21, port 4000 is somehow being filtered or blocked. Port 22 (SSH) is open, so you have two options:
1) Check your firewall settings and allow connections via NX to port 40002) Or you can connect via SSH instead of NX provided you have a version that supports SSH (any of the Enterprise Server/Terminal Server products).
I have removed your logs of the 3.5.0 server. As I mentioned earlier, our traditional support channels are available for 3.5.0 users. If you have a subscription, log in and submit your enquiry there.