Forum Replies Created
-
Posts
-
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.
So this is a different problem and should be dealt with in a new topic. https://www.nomachine.com/forums/topic/black-screen-when-connecting-to-red-hat
An update: we anticipated the transition to the latest version of X.org in 4.3. Download the latest version from the website.
Please see the following posts:
https://www.nomachine.com/forums/topic/no-available-sessions-on-this-server-error
https://www.nomachine.com/forums/topic/no-available-sessions-on-this-server-on-rhel
https://www.nomachine.com/forums/topic/no-session-on-headless-server
There is also the article here: https://www.nomachine.com/AR10L00818
Can you send us the logs @iceback. (Instructions are here: https://www.nomachine.com/AR07K00677, send them to issues[at]nomachine[dot]com.