Forum Replies Created
-
Posts
-
It’s very strange. If you send in your node.cfg we can check it to see that there’s no weird setting.
After further investigation it seems that it’s not an issue of codecs (indeed logs don’t show any errors from codecs whatsoever). It appears that codecs (both H264 and VP8) are encoding a blank frame, hence the blank screen.
To allow us to check whether the frame is indeed blank and possible reasons as to why, we need you to install the package that I’ve emailed to you. It’s not a patch. Install it, enable logs as you did before, run the session, grab the logs and then zip up and send to us.
Thanks for your patience!
We aren’t able to reproduce this behaviour. If you have the AVC pack available, you shouldn’t need to change anything in the server-side settings (or client, for that matter). NoMachine by default checks first if H.264 is available, if it isn’t available, it falls back to VP8. The settings are there for additional configuration when you want to force a specific codec, frame-rate and so forth. Did you do a restart of NoMachine?
Since we never received the logs, what I suggest is you update to v6 and let us know if the problem persists. If it does, please open a new topic.
We never received the new set of logs as Kroy requested. Since you have a Workstation Subscription, what I suggest you do is open a ticket in the customer area (Support Enquiries) to let us investigate further and to avoid sensitive information from being published on the forums. Your support entitlements are documented here:
https://www.nomachine.com/support-services#Terminal-Server
and you can log in from the menu using the customer ID and password you received from us when purchasing.
The attachments were too big. Try sending them to forum[at]nomachine[dot]com. Also, please tell us the Linux distribution and version, and what NoMachine packages you have installed from the website.
Firstly check that the firewall is not interfering on the server side.
Secondly, please send the logs via forum[at]nomachine[dot]com. They most likely didn’t attach because they were too big. We’ll need both client and server sides.
We’ve not been able to reproduce this issue at all, neither on 5.3.9 nor the latest version which is 6.0.66.
First check the /usr/NX/etc/server.cfg file and verify that the clipboard is enabled for both ways:
EnableClipboard both
If that doesn’t work, logs will be required in order to see what the problem is. You can extract them using the instructions here: https://www.nomachine.com/AR07K00677
Both client and server side are required.
The guide for the menu in web sessions is available here: https://www.nomachine.com/DT09O00148#2. You can also preconfigure some parameters in web sessions: https://www.nomachine.com/DT10O00160
On the fly we aren’t able to reproduce it. Can you confirm the desktop environment, and which applications you are noticing this problem?
The exact steps that you take would also be useful.
@jaw1959 what you are seeing is normal in that upon opening the client it will show you records of what you recently connected to, and if on a local network, it will take a few moments to update to show you exactly what is available on that LAN (which in your case is just one server). In fact, you notice that two disappear – that’s because the client now sees an updated situation.
If you don’t want to wait (again, how long this takes depends on your LAN), you can remove the cache, which on Windows is here: %USERPROFILE%\.nx\cache 🙂
What’s the distro and version on the Terminal Server host? What Windows version and what Linux distro and version on the clients you’ve connected from?
What about if you connect the other way around? Is it the same?
Btw, if you want, you can just install the free Enterprise Client (or the free NoMachine packages) on the connecting clients.