Forum Replies Created
-
Posts
-
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 😉
Hi Ang, we got the logs, and I believe the team have now followed up with further instructions. Additionally, a patch will be in the next update, 4.1 🙂
Hi, I just published an update on version 4.1 –Â https://www.nomachine.com/forums/forums/topic/nomachine-4-1-status-update
A fix for this bug will be included 🙂 https://www.nomachine.com/TR11K04077
There are two issues here. Firstly,
I’m using 33110 to connect – where should I be forwarding this port to on the server side?
You are forwarding port 33110 to port 22 which is for SSH connections. To connect using NX you need to forward it to 4000. You can read more about ports here: https://www.nomachine.com/AR01L00770.
Secondly,
Running NoMachine sessions over a SSH connection is not supported on this server. Do you want to switch your connection to using the NX protocol?
“SSH not supported” should not appear in the case of the Workstation since SSH is supported in this product. What did you install? Did you perhaps install Workstation over a NoMachine (free)? If you did, uninstall, remove the directory /usr/NX before reinstalling the Workstation.
Do you get this error when using version 4 or 3.5.0?
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.If you are having problems with 3.5.0, please submit a bug report to issues[at]nomachine.com. You can also search our knowledge base here:
For example: https://www.nomachine.com/AR01F00496
Hi Svens,
SSH is not supported in the free version of NoMachine, so if you want to connect using NoMachine (free) over SSH you should look at the article here: https://www.nomachine.com/AR10K00728. Otherwise you will need to use the Workstation.
If you want to do some tinkering with the NoMachine server software, I recommend you take a look at the configuration guides aimed at the Enterprise products (Workstation, Terminal Server and so on) for example, https://www.nomachine.com/DT09K00059. All the documents are listed here: https://www.nomachine.com/documents.
Can you confirm whether you are connecting to a 3.5.0 server or a version 4 because this is not clear. From what you write it sounds like you are connecting to a 3.5.0, but it could also be a version 4 which has been configured to emulate a server 3.x.
Just to clarify what you are seeing in the Recent Connections list. These represent the connection files, and they are not a representation of how many sessions you have running on the server, or how many you are allowed to have. They simply represent the number of connections that you have run to a given server. (Step 2 here: https://www.nomachine.com/how-to-run-a-virtual-desktop-session). You have 4 different connection files for xx.x.xx.121 and only one with IP= xx.x.xx142.
You can click on one of them to connect to the server indicated in the connection information (Otherwise, inserting the IP in the white field evertime will create a new connection file). You will be prompted to log in. Once authenticated you will be presented with a choice of desktops. If you have a Gnome session already running, you will see it listed there. See Step 5 in the link just mentioned.
picked the session with IP=xx.x.xx.142 and was rejected with “OOPS :Reached the maximum of concurrent virtual sessions …..
That means exactly that. On server .142 you have reached the maximum allowed. To be able to provide further advice, we would need to know what product and version you have installed on both the servers you mention.