Forum Replies Created
January 20, 2014 at 13:03 in reply to: Error is 22: Invalid argument #1773
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.
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.January 20, 2014 at 09:57 in reply to: NX client for windows login problem #1761
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/AR01F00496January 17, 2014 at 15:39 in reply to: Looking for Documentation #1750
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.January 17, 2014 at 14:04 in reply to: Number of sessions and how to save/restore session #1749
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.January 17, 2014 at 13:51 in reply to: Unable to test the Workstation version #1748
Glad to hear that 🙂January 16, 2014 at 18:44 in reply to: Unable to test the Workstation version #1738
Hi, when you uninstalled NoMachine (free version), did you also remove the directory /usr/NX before installing the Workstation? It looks like the previous license is interfering with the Workstation installation.January 16, 2014 at 15:46 in reply to: Custom-Session connection to the server was lost #1730
Can you tell us what Linux distribution and version you are using on the server side. What OS on the client side? Steps to reproduce.January 16, 2014 at 13:42 in reply to: Error is 60: Operation timed out. #1723
For us to provide you with some guidance, can you provide more information? Check the list “What to include” just below 😉January 15, 2014 at 12:11 in reply to: Hide menu panel on connect #1715
Hi, version 4.1 will provide a check box “Don’t show this message again” or similar. That way, you will be able to hide it.January 13, 2014 at 13:43 in reply to: Error is 54: connection reset by peer #1691
Can you send us the server logs from the Window host, too? These client logs are reporting a problem on the server, so we would need to see those. Enable logs on the server side, reproduce the problem and then send them on as you did before.January 13, 2014 at 13:12 in reply to: Error: Session agent timeout: ‘Initial’ since too much time #1690
I am just updating this so the thread is not lost. We received the logs, but it would be useful to look at the .nx directory from the user’s home on the server side.January 10, 2014 at 19:18 in reply to: Connecting 4 client to 4 server on the same machine messes up the GUI #1678
That’s correct. The Workstation and all the Terminal Server versions work as terminal servers, by creating sessions running in the background. These are terminal servers, intended for the enterprise market. The free 3 worked as a terminal server limited to 2 users. This functionality (virtual desktop) is no longer available in the free version. SSH support which was previously available in the free 3 is now available in the enterprise market-oriented products. If you want to replace NX Free Edition with version 4, the Workstation is what you need.January 9, 2014 at 18:17 in reply to: Hangs after login #1643
The logs show there was a problem with display driver initialization. You could try disabling the driver:
– Run devmgmt from Windows command prompt
– Find the device “NoMachine Display Adapter” and disable it.January 9, 2014 at 15:06 in reply to: Cannot connect to NX server on a Ubuntu box #1640
Are you getting any error messages?January 9, 2014 at 11:28 in reply to: Error is 54: connection reset by peer #1637
I can’t connect to my Mac using my PC, the message was connection timed out.
This is very likely a firewall problem. Try disabling the firewall or check that the firewall is not blocking port 4000 (this is the default port used by NoMachine).
Every time I connect to the PC, “The connection with the server was lost. Error is 54: connection reset by peer” pops up.
Logs would be useful for the problem connecting from Mac to Windows. We would need sets from both sides, so client logs from the Mac machine and server logs from the Windows PC. You can submit them here or send them to issues using the title of your topic.
Instructions on how to gather logs are available here: https://www.nomachine.com/AR10K00697.