Forum Replies Created
-
Posts
-
Update: a bug has been queued for fixing:
Black screen shows upon connecting to Windows Server instances running on Google Cloud Platform
https://www.nomachine.com/TR11P08992Follow the link and sign up to be notified when a fix is available.
@netyoda, did reinstalling help? If you’re still having the same problem, let us know.
@Carolus, you were using an old version of the software which handled headless machines only on Enterprise Desktop and not on the free version. From version 6.0.66 the same implementation was included in the free version, and it is possibly for this reason you don’t see that behaviour now you have updated the software.
Please see https://www.nomachine.com/TR11O08272 for more information.
Thanks for the additional information, we are aware of the possible solutions (as part of our investigation ;-)) It’s likely a fix will be made available in the next release.
Thanks for letting us know about the reset password. Tests show there are no problems with resetting the password.
I noticed you actually tried to create two accounts today (not just this one with which you replied herein) one of which failed to be created because the email was undeliverable. Were you using the correct username when logging in with your newly chosen password?
@airscott @jhnhndrsn can you let us know if the issue is still there using the latest version of the software (6.3.6)?
Follow the advice here:
Cannot resize the remote screen to my local monitor’s resolution
https://www.nomachine.com/AR02M00836Can you follow the advice given here and let me know if it helps?
How to solve black screen on headless machines
https://www.nomachine.com/AR03P00973@cvp did you update to 6.3.6? Have you seen improvements?
Hi, it’s not been released yet, so that is why it’s still open. However, it’s in its final stages. This particular implementation means there will be alterations to the UI which implies heavy testing and adjustments at the UX level. But not long now 😉
After looking at the additional information you sent us via email, it appears to be a problem with the order of recording devices in CentOS which is set in Audio Setup > Audio Recording. As a workaround you could try changing this order so that NoMachine Microphone is in first position. After this, the microphone feature should work.
Hi, can you try attaching those images again? If they are too big, you can send them directly to forum[at]nomachine[dot]com. Thanks!
Please tell us:
1) version of NoMachine installed on the server and client
2) NoMachine product installed on the server and client
3) were you able to connect without problems to this NoMachine server in the past or is this the first time you’re connecting to the Debian 4.9 host?
We tested on Debian 4.0 and we are able to connect without any issues.
We have inserted a new Feature Request in the development roadmap:
Adding support for ECDSA and ed25519 SSH key types
https://www.nomachine.com/FR11P03735Please use the ‘notify me’ service to know when it has been implemented 🙂
NoMachine manager with Category
Can you provide more details about your request? It’s not quite clear what you’d like 🙂
city, servers or workstation
Here, do you mean you’d like to make groups of connections of some sort, based on location maybe? We’d need some more info so we understand exactly what you are asking us to add.