Forum Replies Created
-
Posts
-
We’re investigating and will update with our findings. In the meantime can you tell us if you encountered the problem of input not being accepted anywhere else, e.g. is it only ever in the login screen?
Hi, we’ve often contemplated offering a version for FreeBSD, but it really all comes down to the number of users who would be interested. Interest has been rather sporadic which simply doesn’t justify the costs: not just investment for initial development, but also the subsequent maintenance efforts involved when supporting any platform such as the constant regression tests which are fundamental at every release.
Neil, see this topic here: https://www.nomachine.com/forums/forums/topic/changes-disabled-cant-unlock-with-ad-account which looks similar.
Some further information would be useful. Are you able to tell us the output (from a terminal) of ‘net user
and send it to us at issues[at]nomachine.com? Logs (both sides) would also be interesting to see. Just attach them to your email with the subject of your topic. To extract the logs take a look at the article here: https://www.nomachine.com/AR10K00697
Thanks.
Hi Marsh,
Can you read this similar topic here: https://www.nomachine.com/forums/forums/topic/cannot-connect-to-server#post-858
If the tips don’t help, send us the information requested in our last post.
Britgirl
Hi Werner,
Thanks for letting us know 🙂
It would have been interesting to understand what happened, but I don’t think this had to do with the server. The CTRL+V you are talking about is handled by the application that is target of the clipboard operation, not by the NX server.
If the copy+paste operation worked by right clicking on the selection, it should have worked even using a keystroke. It is more likely that the problem was resolved by the application restart.
I will close this topic now. Just open a new one if you need to.
Hi sdepner,
This forum is for dealing with features and problems of version 4. This includes client and server and excludes compatibility problems with older versions, that are obviously managed by our support channel. I noticed you are using a client (3.4.0), which is 6 years old and for sure is not supported by version 4. What I suggest is that you first try to upgrade the client. If you experience the same problem with client 4 I’ll be glad to help you if you’ll open a new topic.
Thank you for submitting the logs. A Trouble Report has been inserted:
https://www.nomachine.com/TR11K04044
A fix will be available in one of the next updates.
We weren’t able to reproduce this particular behaviour. The logs might provide some useful information.
Hi, we have just published an article which will help you with this. Can you follow the instructions there and let us know how you get on?
An audio fix should be coming with the next update, so watch out for that.
But to make extra sure, are you able to show us output of these commands run in the session while audio is playing?
$ amixer -c 0 get PCM
$ amixer -c 1 get PCM
$ amixer -c 2 get PCM$ pactl list | grep -A3 “Source #”
Sounds similar to a bug we already fixed:
https://www.nomachine.com/TR11K04037
Can you update to the latest version? You should have 4.0.366 installed.
We passed a patch to another user with the same issue and it fixed the problem. It will be made available with the next release, so make sure you keep an eye on our software updates.
Hi, there is no correlation between audio not working and the colour of the monitor icon. The colour was changed to black because many found red too alarming.
We’ll follow up on your other topic about audio, so we don’t confuse threads.
No problem yazoor! I forgot to mention that you can use the following link to track the status of the TR: https://www.nomachine.com/TR11K04079