Forum Replies Created
-
Posts
-
Hi Justin.
1) When interacting with the remote desktop, I get a lot of OS ding sounds (like each time an app is started, new window is created) – known issue, way to resolve?
This has been reproduced in our labs and it is currently being investigated.
2) When you logout of the remote desktop (logout of Windows), the image does not update to the login screen, you are stuck at the image just before logout. Is this by design? Seems like a bug to me.
This should be fixed with the next software update.
3) Do the graphics options in preferences apply only for serving? In other words, if I make a change on my client !M, will that affect how the server streams the graphics? (The UI is not clear on this matter.)
Those settings only apply when the machine where you are doing the changes on acts as a server. If you change preferences (from the NoMachine tray icon) on the client machine, those changes won’t be exported to the server.
Anyway, there is a different set of settings that affects the way the server streams the display. Those are the ones that can be tweaked from the NoMachine Player toolbar during the session.4) In Performance preferences, there are options for framerate and display encoding, and both are unchecked by default. If these are unchecked (i.e., no specification made), what values are they using?
Default value for framerate is 25 fps. The encoding method depends also on the decoding capabilities of the client. If the client supports H.264 decoding (by means of the hardware or by codec libraries), then H.264 will be chosen. Otherwise VP8 encoding is always used. MJPEG won’t be used unless it is explicitly requested.
Hi Justin,
the logs seems to point to a problem related to the video drivers. Can you specify the version of your graphics card so we can try to replicate this issue in our labs?
Please try to disable the hardware acceleration from the NoMachine tray icon on the server machine:
Show the server status -> Server preferences -> Performance
then uncheck “Use acceleration for display processing”.
Hi Bart,
it doesn’t appear to be a NoMachine problem since it was reproduced without NoMachine being involved, though it seems not clear what triggers it. Are you attaching to the physical desktop of the Mint machine? Or are you running a virtual desktop session? In the latter case, with a different user than the one logged in physically? And was the NumLock enabled/disabled on the client and the server hosts?
Hi jackV,
indeed this looks like a problem with the video drivers, but I’m not sure I understand what you mean with “visualization”. Is Ubuntu running inside a virtual machine on the Windows 7 host? And in this case visualization has to be intended as “video acceleration” to be enabled in the virtual machine? What is the version of Ubuntu?
Hi georgesil,
this looks like a configuration problem with the proxy, more than with the software. Maybe there is a firewall that starts dropping packets after a while. Are these public proxies that we can try ourselves? If you want to provide further info privately, you can send a email to forum[at]nomachine[dot]com.Hi Bart,
this looks very similar to the problem reported here: http://forums.mate-desktop.org/viewtopic.php?f=5&t=2094.
Can you try the suggested workaround?
Hi elan,
unfortunately the logs you sent are not complete and not useful for the investigation. Please send a complete set of logs as explained in details here: https://www.nomachine.com/AR07K00677. If you wish, you can send them to forum[at]nomachine[dot]com by referencing this topic in the subject.
But before that, can you tell something more? I see you are connecting to a Xvfb display. Is this a headless machine and you followed instructions in https://www.nomachine.com/AR10K00710? Have you launched a desktop environment (or any X application) inside the Xvfb display?
Hi iceback,
I assume the session was left in disconnected state, and when you reconnected after 2 weeks you found it unresponsive?
Do you still have logs from that session? More info on how to gather logs here: https://www.nomachine.com/AR07K00677. They can be sent to forum[at]nomachine[dot]com.
Finally, if the session is still running, please do a test: try to reconnect that session by double-clicking on the icon representing the session but, while doing so, keep Ctrl+Alt pressed. This will make the session is reconnected in “shadowing” mode. Let’s see if user input works with the different protocol.
Hi claus,
by default NoMachine listens on port 4000. Can you tell us the output of the ‘netstat -an | grep LISTEN’ command on the server?
Also server side logs could be useful. You can find instructions on how to gather logs in https://www.nomachine.com/AR07K00677. You can send them to forum[at]nomachine[dot]com.
Hi,
from the logs it looks like the only running instance of Xserver is a Xvfb (virtual framebuffer). Can you confirm?
Is that a headless machine and you started Xvfb maybe for the purpose of allowing connections through NoMachine?
Are you sure a desktop environment is actually running inside the Xvfb?
Hi,
unfortunately the archive seems to be corrupted. Can you please send the logs again to forum[at]nomachine[dot]com?
Hi BitPerfectRichard,
we finally managed to reproduce the problem with Console Log and the fix will be included in the upcoming software update.
The issue was related to the “Resize remote screen” feature and disabling it would have worked as a workaround. The reason why you don’t reproduce it with the just released Yosemite is that remote resize is not yet fully supported there and we are working on it. This should also explain why you don’t get the expected resolution.
Hi 70tas,
available resolutions depends on the Hyper-V and video drivers. NoMachine can only choose among the resolutions supported by the hardware.
You can try the “Fit to window” option that will stretch the remote screen to match the resolution you have on client side.
Hi sivaraman.s,
what is your NoMachine version?
We would need the complete set of logs to investigate further. Please follow the instructions in https://www.nomachine.com/AR07K00677 (included section “How to gather node logs”) to gather all logs and send them to forum[at]nomachine[dot]com.
Could you please verify the version of your libavcodec and libavutil libraries?
You can do this by listing files in their install directory, e.g.:$ ls -l /usr/lib/libav*
Currently NoMachine supports avcodec library up to major version 55. If you have the newest version (which is 56), you should downgrade your libraries to use it with NoMachine. Support for version 56 is being added.