- This topic has 5 replies, 3 voices, and was last updated 5 years, 8 months ago by
.
-
Posts
-
Hello,
Here are 2 setups:
1) A Windows desktop connects to a Linux server using NoMachine.
2) A Windows desktop connects to another Windows desktop through Windows Remote Desktop (WRD) and then from there connects to a Linux server using NoMachine.
In setup 1) NoMachine works very fast, in setup 2) it often works quite slow. By slow, I mean that: A) it could take seconds for the Linux server screen to refresh, B) responsiveness of the Windows desktop accessed through WRD is much higher than of the server accessed through NoMachine from the desktop.
I use setup 2) both to work from home and to connect from one desktop at work to another (the two desktops are in close proximity). In both cases, I can feel slowdown of NoMachine if it is used through WRD. Connecting/disconnecting a few times through WRD to the desktop often helps to make NoMachine to work much faster.
Could you please let me know if there is anything I could do to improve performance of NoMachine when it is used through WRD?
NoMachine version: 6.3.6 (free). Windows desktop accessed through WRD runs Windows 7. The Linux server runs RHELÂ 7.3 (virtual machine, KDE).
Thank you for your help!
Hi, just for clarity: Windows ‘A’ (don’t know the version), Windows 7 (‘B’ ) and RedHat computer we’ll call ‘C’.
Am I right in assuming that when you connect from B to C the performance is fast, i.e they are the same hosts you mention in Set-up 1?
If so, that would mean that the problem is WRD, not NoMachine. A possible assumption about any slowness being caused by WRD could possibly be because it intercepts primitive graphics and not images in order to draw the content of Windows applications (?) Nxplayer draws the remote desktop as images which Windows Remote Desktop Protocol can’t compress optimally.
Out of curiosity, what happens if you connect from A to B with NoMachine and run NoMachine from within your NX connection?
Hello Britgirl,
Windows A is Windows 10 (when I work from home) or Windows 7 (when I work from another office).
Yes, you are right: when I connect from B to C (this is setup 1), the performance is fast.
Unfortunately, I can not test what happens when I connect from A to B with NoMachine since there is no direct connection to the company computers from the outside world. We have to go through a specific web-site, use RSA token to go through 1st level authentication, which then downloads and launches some software, which in turn starts WRD and then go through 2nd level authentication.
So, you are saying there is nothing I can do to improve performance of NoMachine in setup 2?
Thank you!
You could try turning off scaling (Fit to Window). See https://www.nomachine.com/DT10O00157#5 for more details.
Yes, you are right: when I connect from B to C (this is setup 1), the performance is fast.
What to say? Well… Good for NoMachine, comparing the performance of RDP vs. NX, in this particular case.
Yes, indeed.
In general, when streaming a Windows desktop, RDP has access to the internal OS graphics primitives. But this doesn’t occur when streaming the NoMachine session, whose content is a Linux screen that is rendered remotely.
RDP is not able to stream this type of content as efficiently, so it’s not a NoMachine problem. This is a performance issue that must be solved in RDP.
This topic was marked as solved, you can't post.