Forum Replies Created
-
Posts
-
Thanks for info. Indeed you would have to export those devices explicitly in order to trigger that problem.
Would you mind to try one more thing? In https://www.nomachine.com/AR03P00973 you can find a couple of methods to turn off the local X server on Ubuntu. In this case NoMachine will then use its own virtual frame buffer and we would be able to exclude or narrow down this issue to drivers on server side. And if possible, it would be nice to check the CPU usage of the server while reproducing the issue.
Hi,
this is very strange. Logs look clean and we can’t reproduce anything similar on various Windows Servers in our labs. Though another user experienced a similar problem: could you check if the workaround here makes any difference for you?
A small clarification to what Britgirl wrote – obviously we handle multi-touch events such as the ‘traditional’ two-finger swipe or pinch-to-zoom in our iOS and Android apps, and we will add support for them on Windows tablets soon.
This is a really strange issue. Could this Trouble Report possibly apply to your case?
Hi,
could this Trouble Report apply to your case (i.e., are you sharing a USB device between client and server by NoMachine services)?
https://www.nomachine.com/TR06P08609
And yes, logs could be useful. Please find instructions for the server side in https://www.nomachine.com/AR10K00697 and for the client in https://www.nomachine.com/DT10O00163#2. You can send files to forum[at]nomachine[dot]com.
Logs are pretty clean. Are you sure it’s not something with your network setup. Are you using a VPN service between the client and the server maybe? Could that be the culprit?
I would also try to disable UDP (Edit connection -> Advanced -> uncheck ‘Use UDP communication for multimedia data’).
Also, please check CPU usage during the “freeze”.
Hi Babok,
can you tell us more about the hardware you have on the server and about the desktop environment (GNOME, KDE…) in use? Besides lowering the screen resolution, you could try to use a lightweight desktop environment, if that’s not the case already (see https://www.nomachine.com/AR07K00676).
Sometimes had to relaunch the server NoMachine because I couldn’t connect to. I read this bug has been reported before, any news on macOS problem occurring on monitors supporting wide color gamut?
Can you tell us more about this problem? If you are referring to https://www.nomachine.com/TR10P08920, that should be fixed in version 6.8.
Hi Ross,
please gather server and client side logs, as explained in https://www.nomachine.com/AR10K00697 and https://www.nomachine.com/DT10O00163#2.3. You can send them to forum[at]nomachine[dot]com.
Also session statistics could be useful:
– open the Connection panel in the NoMachine Menu Panel (see https://www.nomachine.com/DT07M00087#9);
– click on ‘Take the statistics’ once to reset counters and discard the result;
– reproduce the issue (for example type in the terminal and wait for the result);
– click on ‘Take the statistics’ one more time and send us the resulting file.Hi,
please collect server-side logs from the Windows 8.1 computer and show us. You can send them to forum[at]nomachine[dot]com.
Are you connecting to the login screen of your Windows 8.1 computer?
Hi davide445,
it’s hard to provide any exact figure without a specific investigation. I can confirm that latency generally is in the order of few milliseconds, but as you can imagine it can depend on many factors, like the hardware, the availability of a hardware decoder, the frame resolution, etc. I think the best way is trying it out…
Hi,
I wasn’t able to reproduce your problem. Could you send a screenshot of the scaling options from the display settings of both your client and server Macs?
Hi,
aren’t fonts progressively refined? Or do they stay blurred? In the last case, please send a screenshot showing the problem.
In the meanwhile, you can try to check the ‘Disable multi-pass display encoding’ option in the Display settings.
Thanks for the logs. Please check if any of the these helps:
1) turn off UDP (Edit connection -> Advanced -> uncheck ‘Use UDP communication for multimedia data’);
2) uncomment and set the EncoderMode key (in /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg) to the following:
EncoderMode bitrate(then restart the server)
I exit i3 and went back into a tty. From there I made sure that the nxserver was running. But from my smartphone while I do see my laptop when I try to connect to it it tells me “Error is 113: No route to host”.
It’s not clear to me what you did exactly. To make sure you effectively stopped the display manager, please run this command and tell the output:
systemctl status display-managerAnyway “No route to host” is strange, it seems like the IP address is wrong. Are you inserting it manually?
In the logs you sent previously, I see that the resolution of physical display on the server is 3840×3040. Are there multiple monitors or is it only one with such a high resolution? Can you try to use only one monitor in the first case, or lower the screen resolution in the second, and check how this impacts performance?
Hi kvic,
it seems the ‘lossless refinement’ feature is not being used. Can you send send server (https://www.nomachine.com/AR10K00697) and client (https://www.nomachine.com/DT10O00163#2.2) logs so we can take a further look? You can send them to forum[at]nomachine[dot]com.