Forum Replies Created
-
AuthorPosts
-
BritgirlKeymaster
The administrator could install NoMachine on every virtual instance (‘NoMachine nodes’), and then add these nodes to the main server: Enterprise Server. Via manual selection, users would then select their desktop node once authenticated on the Enterprise Server. There is no randomly assignment of user to the session. Admin could configure/customize access to remote nodes using NX profiles.
The following resources may be useful:
Multi-node concepts in NoMachine – https://www.nomachine.com/DT07M00091#7
Profiles – https://www.nomachine.com/DT07M00091#3For more information about Active Directory take a look here:
https://www.nomachine.com/forums/topic/only-allow-specific-windows-domain-users-to-login andalso here:
https://www.nomachine.com/AR01O00914I would also suggest you contact our sales team. They will be able to go into more technical detail about your specific requirements.
BritgirlKeymaster@Iceback, can you send us the logs from the server side?
https://www.nomachine.com/DT07M00098
Send to forum[at]nomachine[dot]com
Thanks!
August 25, 2016 at 11:25 in reply to: OpenSuse Leap unable to authenticate for software update #12180BritgirlKeymasterWe’ve reproduced it and open a Trouble Report. You can check the ‘notify me’ box to receive notification of when a fix has been released.
https://www.nomachine.com/TR08N07155
Thanks!
BritgirlKeymasterAdditional note from the user about the debug version sent.
“I removed the standard versions and then installed the debug-versions as supplied on both server and client, and the problem was gone.
* I reinstalled a 5.1.44-1 version downloaded from http://www.nomachine.com on the client, and the problem was not apparent anymore* I then reinstalled a 5.1.44-1 version downloaded from http://www.nomachine.com on the server as well, and the problem was not apparent anymore”August 24, 2016 at 12:52 in reply to: Physical monitor limitations for virtual sessions w/ floating window #12163BritgirlKeymasterHere is the link to the Trouble Report opened: https://www.nomachine.com/TR07N07020
BritgirlKeymasterHi, we are aware of this issue and it will be fixed. Once Sierra is out of beta, we can then work on adding it to our list of supported platforms. See here for our policies about beta versions: https://www.nomachine.com/AR03E00450
BritgirlKeymasterOk, remember there is this which has some tips on setting up Amazon VMs in case you need it.
BritgirlKeymasterIt looks like this Trouble Report we have open already: https://www.nomachine.com/TR04N06804
August 22, 2016 at 09:36 in reply to: How to set up key-based authentication for connecting to Windows #12144BritgirlKeymasterI made a quick search of the KB to make sure what we were missing: https://www.nomachine.com/knowledge-base ‘key-based authentication’. Perhaps the results were a little overwhelming 😉
Anyway, the following will help you with your question:
https://www.nomachine.com/AR12I00615&an=key-based%20authentication
and this:
https://www.nomachine.com/AR02L00785&an=key-based%20authentication
Let me know how you get on.
August 22, 2016 at 08:28 in reply to: Google Compute Engine Ubuntu 16.04 "Failed to determine the client IP" #12141BritgirlKeymasterWe’ve opened a Trouble Report which you can see here: https://www.nomachine.com/TR08N07141. Check the ‘notify me’ box to know when a fix has been released.
BritgirlKeymasterPlease send the logs to forum[at]nomachine[dot]com.
BritgirlKeymasterDo you have the latest version of NoMachine installed on both your computers? You say you have Windows; is that the OS you are connecting from or to? What is the other OS of the other computer? This information will help us to understand your set-up is and also to check there is no bug that we are unaware of.
Once you’ve started a NoMachine connection there are two ways to send files to and from. One is drag and drop which works both ways, the other is using the Monitor (!M icon in the system tray). This also works both ways. See here for more details: https://www.nomachine.com/sharing-files-between-computers.
August 18, 2016 at 13:40 in reply to: Google Compute Engine Ubuntu 16.04 "Failed to determine the client IP" #12118BritgirlKeymasterThe problem with the connection to the server for Google Cloud is related to a bug in NoMachine. This is the same error in both cases on Ubuntu 16.04 with Gnome and Ubuntu 14.04 with Xface. A possible workaround is to set key EnableUPnP from “NX” to “none” in the server.cfg file.
BritgirlKeymasterHi, try disabling UDP as a temporary workaround. Do that via the GUI: choose the connection -> Edit -> Advanced -> uncheck ‘use UDP communication for multimedia data’.
So far we’ve not been able to reproduce the issue. Would you be interested in installing a debug version to help with our investigation?
BritgirlKeymasterYou are using the legacy version 3.5.0 or earlier. Install the Workstation or ask your provider to update the NoMachine server version they are using, or better still to open a ticket in the support section of their customer area. All 3.5.0 issues are dealt with via that channel. The forums are for users of the latest version from our website.
If the issue continues (though we are not aware of similar problems on Ubuntu) with NoMachine version 5, we can continue the investigation further.
-
AuthorPosts