Forum Replies Created
-
Posts
-
If you connect from a PC on the same network, you have to use the internal IP which you have done correctly. When you connect from a PC on an external network, you need to use the Gateway IP instead. Your office’s external IP address should be shown in the Gateway IP field (in your case 108.xxx.xxx.xx) which you obtain by opening the GUI from the menu and clicking on the penultimate icon on the right (Server settings). It takes you to the Forwarded ports panel by default. Write down this IP address along with the port number shown next to NX:…. This information is what you need to use in the connection GUI when connecting from home. Make sure that the checkbox for NX is ticked.
If you did this, and you are still getting the connection error, then it’s either a firewall issue or a router issue. In that case you will need to configure your office router to forward a suitable port to your local IP port 4000 (NoMachine uses 4000 by default).
To connect from home, you then use your office’s external IP address and the port that you either obtained from the Forwarded ports panel or which you configured manually on the router.
Hi John, this is strange and we would need to see the logs to be able to understand what is happening. If they are not too big, you can submit them there, otherwise send to forum[at]nomachine[dot]com. You will need to follow the instructions in the article here (first reproducing the problem) on how to enable and extract them.
https://www.nomachine.com/AR10K00697The client side logs you attached are not complete. If you have problems attaching client and server side logs here, you can send them to forum[at]nomachine[dot]com.
Please consult the following article for instructions on how to get the complete client and server logs:
https://www.nomachine.com/AR10K00697
https://www.nomachine.com/AR07K00677
On the client side (on Windows 7):
– Start the session and reproduce the problem
– go to C:\Users\<YOUR_USERNAME>\.nx\
– find newest R-* directory and compress it .Make sure you set in the player settings ‘do not delete old log files on exit’ (Open the UI, click ‘Player settings’ icon, click ‘Player options’)
Do the following:
1. As root edit /Applications/NoMachine.app/Contents/Frameworks/etc/server.cfg
2. Change #SessionLogLevel 6 to SessionLogLevel 7
3. Restart nxserver command: /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver –restart
4. Try to reproduce problem.
5. Send /Library/Application\ Support/NoMachine/var/log/nxserver.log. Either attach it here or submit to forum[at]nomachine[dot]com.I’m now going to close this thread. The problem can be tracked via the Trouble Report that was opened.
Hi,
Our developers will be interested in investigating the issue when connecting from version 4 to version 4. It might be an idea to submit your logs to forum[at]nomachine[dot]com making sure you reference the forum post if they are too heavy attach here.
This forum is for dealing with features and problems of version 4. This includes client and server and excludes compatibility problems with older versions, that are managed by our support channel. Any questions about 3.5.0, you can either submit a bug report here: https://www.nomachine.com/report-issues, or contact us via the website at Contact us below.
Hi, if it makes it clearer, it’s not a problem updating it. Our developers are able to reproduce it in any case 😉
Hi techxedu,
NoMachine, the free version, is perfect as a remote access tool for almost anyone, so that means if you are in a school that needs to provide a tool for easy access to remote hosts, perhaps you are an IT admin, then you can use the free version. It depends what your requirements are, but also what the school wants to do with the software.
For example, if you need to provide remote collaboration between teacher and students, you should probably contact our sales team to see what your options are. The free version offers one connection which means that multiple users can’t connect to the same PC simultaneously. For that you would need Enterprise Desktop, or perhaps Workstation if they are Linux.
We know we have to document better how GUI settings in the previous version apply to the GUI in version 4, and we are
are working on that.For the moment you can do it by hand in the NXS file.
<option key=”Use default image encoding” value=”1″ />
enables custom settings, and
<option key=”Image Compression Type” value=”2″ />enables RGB.
Did you install the Terminal Server product on top of a free NoMachine? Virtual desktops are enabled by default. If you had NoMachine (free) installed earlier, uninstall everything, remove the installation dir, and reinstall the Terminal Server from scratch. I agree, what would be the point of a terminal server if can’t create virtual sessions 😉