Forum Replies Created
-
Posts
-
It’s possible by switching the virtual terminal from keyboard connected to the machine or remotely with help of chvt command line tool. Alternatively you can use a Xvfb for a secondary display.
Another solution is to use the Workstation edition from our virtual Linux desktop range of products.
A patch for this issue was released in version 4.3.24. See here:
From the logs your submitted:
The following error:‘2014-10-16 10:55:21 485.536 12919 NXSERVER ERROR! X resources are not enough to start another session.’
can occur when the server is not able to find a free display in the range defined by the server configuration.
Default values are:
#DisplayBase 1001
#DisplayLimit 200
You can try to increase value set for the DisplayLimit key to see if it helps.
The problem can be due to leftovers from previous sessions. The cleaning procedure to free system resources when a session
failed was not working properly in version 4.2.27. This problem is not present in the 4.3 versions.We suggest to upgrade your installation to the latest 4.3.24 version.
I suggest you take a look at our installation guides. You can find these in the support section of the website: https://www.nomachine.com/all-documents.
Alternatively, you can find them also linked in our Knowledge Base https://www.nomachine.com/search/node/installation%20guide.
I also suggest you download and try the any of packages offering the virtual Linux desktop functionality. They are available in the following section of the website in evaluation. A good starting point is Terminal Server or Workstation:
Have you tried this?
Right now routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required information is displayed at initial screen (Welcome to NoMachine).
Routers not supporting UPnP or NAT-PMP and Firewalls have to be configured manually to pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows).
Additionally, your NAT service is running on Virtual Box which means that it cannot be configured automatically with help of UPnP or NAT-PMP. To do it manually please refer to: https://www.virtualbox.org/manual/ch06.html#natforward
Just a reminder that 3.5.0 issues are now dealt with via the traditional support channels. From the logs we saw that it was an issue with 3.5.0 client to version 4 server.
A Trouble Report was opened and has since been fixed.
https://www.nomachine.com/TR11K04011
From what you write it seems that you are connecting to a physical desktop session. Did you try Enterprise Desktop or Enterprise Server? The latter offers the virtual desktop functionality (as do Workstation, Terminal Server, Cloud Server) which is what you should be using.
We are aiming for the end of the year. You can sign up to our news mailing list to get updates from us about any of our products.
Please send us the output to issues[at]nomachine[dot]com. Make sure you reference the title of your topic. Thanks.
Can you send the files to issues[at]nomachine[dot]com? They might have been too big to attach in the forums. Make sure you reference them with the title of your topic. Thanks
From this:
NX> 161 Enabled service: nxserver.
NX> 162 WARNING: Cannot find X servers running on this machine.
NX> 162 WARNING: Connections to the physical display are not possible.
NX> 161 Enabled service: nxd.it’s telling us that nxserver was not able to find or access the local X server, and make it available.
If there is a working X server, then please enable logs in server and node configuration file, restart nxserver, check the
status once again after few seconds and send to us whole var/log directory.Additional output of the command: ps awwxo ‘ppid,pid,comm,args’ would be helpful.
The logs can be sent to issues[at]nomachine[dot]com.
NoMachine for Android tablets is available. (both from our website and Playstore) https://www.nomachine.com/download
Also check out the tutorial: https://www.nomachine.com/getting-started-with-nomachine-for-android
First try updating to the latest version and report back (you are using 4.3.23, and we just released 4.3.24). If the problem is still there, I suggest you extract the logs and submit them to us via issues[at]nomachine[dot]com. To extract the logs, check the instructions here: https://www.nomachine.com/AR07K00677.