Forum Replies Created
-
Posts
-
Hi keyxmakerx,
Currently NoMachine tries to configure automatically a router to allow incoming connections. If it is successful, details of an IP and a port to use to connect are available in the Player GUI.
Routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required informations are 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).What you ideally need is NoMachine Anywhere. It will be perfect for users who either don’t know their IP or are not able to configure their router for whatever reason.
NoMachine Anywhere is in its final stages of development and will be introduced along the development of the new version 5.Hi oar, the recent release permanently fixes the problem you encountered.
We therefore recommend you to update to version 4.5.
Hi ambm01,
Please make sure you have a public IP and configure the firewall to pass traffic on port 4000.
As an alternative you can install a version with SSH support and it should work out of box.
Let us know if you have further issues.
Hello shalafi71,
In order to allow us to investigate your issue, could you please send us the logs (server and client sides) ? You can send them to forum[at]nomachine[dot]com, making sure you reference this topic.
If needed, you can find the procedure explained in the following article: “How to gather debug logs for support requests” (https://www.nomachine.com/AR07K00677).
Best regards.
Hi Heywood,
If you are using NX protocol, maybe you put the public key in the wrong place ?
Please follow the procedure described in the article “How to set up key based authentication with NX protocol” (https://www.nomachine.com/AR02L00785) and let us know if you encounter further problems.
Best regards.
Hi pwisnovsky,
From our latest test we can confirm that our NoMachine server and client are compatible with MacOSX 10.10 Yosemite.
Hi ou_cto,
Thank you for your message.
Could you please forward it to forum[at]nomachine[dot]com and attach both client logs and server logs ?
Thank you.
Hi ekimm2,
In the future it will be handled by NoMachine Anywhere.
Right now routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required informations are 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).
Hi jwsudd,
This problem has been fixed; the updated version will be available soon. Keep watching this space.
Thank you for your patience!
Hi cosmonaute,
Logs would be useful; for some reason your attempt to attach them failed.
If needed, follow the instructions here on how to enable and extract them (https://www.nomachine.com/AR07K00677).
You can send them to issues[at]nomachine[dot]com. Make sure you reference your topic title.
Thank you,
The NoMachine Team
Hi mohseniaref,
Logs would be useful; for some reason your attempt to attach them failed.
If needed, follow the instructions here on how to enable and extract them (https://www.nomachine.com/AR07K00677).
You can send them to issues[at]nomachine[dot]com. Make sure you reference your topic title.
Thank you,
The NoMachine Team
Hi Shawn,
There’s no nxbuilder any more, but there’s a Web Companion for NoMachine 4.0.
You can download it here: https://www.nomachine.com/product&p=NoMachine%20Web%20Companion.
Hi mivang078,
Blanking remote screen during connection is a feature that will be implemented soon. In the meantime, you have the possibility to start a separate X server (Xvfb) and attaching to it, instead of X display connected to monitor.
The article “How to use NoMachine 4 on a headless Linux server” (here: https://www.nomachine.com/AR10K00710) will give you some tips about Xvfb.
In your case, you will have to start it on display other then :0, and adjust DisplayDefault key in node.cfg.
Best regards,
Bilbotine
Hi imn,
%PROGRAMDATA%/NoMachine/var/log path is valid for logs obtained on server side, as it is explained in the article “How to gather debug logs for support requests” (https://www.nomachine.com/AR07K00677), section “How to gather server side logs”.
If you want to help us with debugging this issue, you have to follow the procedure explained in the “How to gather client side logs” section of the same article on the computer on which you installed NoMachine Enterprise Client and the procedure of “How to gather client side logs” on the server where you are connecting.
Please send us the logs to issues[at]nomachine[dot]com, and make sure you reference your topic title.
Thank you.