Forum Replies Created
-
Posts
-
Hi, I don’t know what problems you found from 2012 because version 4 was only released last year. Do you have the links? Perhaps they were about version 3.x?
Anyway, it’ important you have the latest version on both client and server (4.2.27). Provided you have version 4 client and server installed, it will be easier if you enable logs both sides, reproduce the problem and then submit them to us so we can check that it’s not a problem we are already aware of. E.g there is https://www.nomachine.com/TR04L04396
More info here: https://www.nomachine.com/AR07K00677 Send them to issues[at]nomachine[dot]com referencing your topic.
Which product did you decide to install? If you’ve followed the instructions in the article (so setting CommandStartRDP “rdesktop -f”, editing the AvailableSessionTypes key in the node.cfg and server.cfg), it should be out of the box, and when you see ‘Create a new virtual desktop’ in the GUI, an icon for RDP will also be there. See fig. 6 here https://www.nomachine.com/creating-new-virtual-desktop-sessions to see what I mean.
Hi, this is a customized to order PC, not one that Windows users would easily find. It’s not reproducable on any standard Windows PCs. Further investigation on that specific hardware will be required in order to understand what’s triggering it.
Hi Archie, one of the articles (now updated) had Terminal Server missing, sorry about that. You can use Terminal Server, Enterprise Server or Cloud Server, they all support rdp sessions.
rdesktop client needs to be installed on the machine where you have installed the server, so in your case, it’s the Ubuntu machine 🙂
Hi Archie, take a look at these articles:
An approximate time could be the second quarter of 2015 (provided that development goes smoothly between then :-)) We’ll keep you updated via the forums.
Can you upgrade to the latest version? A lot of fixes have been released since 4.0.360. Let us know if this helps.
Hi did you try this?
How to use NoMachine 4 on a headless Linux serverhttps://www.nomachine.com/AR10K00710&articleName=ec2
Keep calm (and the original post was moderated to keep the tone down). Did you try selecting ‘Resize remote screen’ from the Menu? From the screenshot it looks like you’ve got Viewport enabled.
https://www.nomachine.com/DT10K00060&documentName=#5.2
This seems to be a very specific issue, related to an application that not many users will know, and I feel should be dealt with via the support channels (Support enquiry, or even Contact us). Let’s try to keep the forums dedicated to more “familiar problems” 🙂 i.e NoMachine issues related to applications and desktop environments shipped with Linux distros at source are fine, as most users of Linux will be familiar with those.
Hi,
the logs excerpt are from version 3.5.0 client. NX 3.5.0 is now dealt with via the traditional support channels, so I suggest you use the contact us link at the bottom of the website if you need further information about backward compatibility between versions. That said, the logs show that you are trying to connect using SSH (port 22), and SSH is not supported in the free NoMachine server. Try installing the NoMachine 4 client on Windows and report back. By default it uses port 4000 (NX protocol). If you want to continue using port 22, you need to install the Workstation on the remote server host.
Related post: https://www.nomachine.com/forums/topic/cannot-connect-to-nomachine4-from-wndows-client-installed-on-linux-server
Send us the full set of log files and also .xsession-errors.
The output of “xset q” and also “xdpyinfo”. The logs can be extracted using the article here and sending to issues[at]nomachine[dot]com.
https://www.nomachine.com/AR07K00677
When submitting via email, make sure you reference the topic title, thanks.
If the problem occurs when you are connecting to server 3.5.0, you need to contact the team via the website. The forums only deal with version 4 on server and client.
Hi everyone, there is a Trouble Report open on this: https://www.nomachine.com/TR08L04502
You can sign up for notification of its fix.