Forum Replies Created
Error: Connections to virtual desktops are disabled on this server.
It appears to be a problem which was just fixed with the release of 4.0.367. Can you update? Note that a fix for https://www.nomachine.com/TR11K04066 is not yet available. It will probably make the next update.December 5, 2013 at 09:26 in reply to: NoMachine freezing intermittently when connected to Mavericks PC #1161
Ang, again the logs don’t show anything strange. If possible, can we send you a debug version for you to install? Let us know: issues[at]nomachine.com
It sounds like the bug with domain users’ authentication for which a fix should be released very soon.
A quick check to see if it is this bug is to try logging in with a local account (if that’s possible).
Packages 4.0.367 fix this TR.December 3, 2013 at 20:47 in reply to: NoMachine connects but doesn’t accept keyboard or mouse input #1124
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.December 3, 2013 at 15:30 in reply to: can't unlock nx4 session with capital letter in password #1109
I will close this now as the team are now in touch with you via email 🙂December 3, 2013 at 08:47 in reply to: Trouble connecting to remote Linux desktop from Windows 7 Laptop #1100
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.
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.
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:
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 #”