Forum Replies Created
-
Posts
-
See Kroy’s earlier reply to you from November. The document explains how to enable debug and extract the logs.
If the problem is still there, enable debug, reproduce again and send logs from the server side (instruction how to collect logs you can find there: https://www.nomachine.com/DT10O00163
Thanks!
So you don’t even reach the login prompt (username and password pane)? We’ve gone through the instructions again just to make sure they are correct, which they are. Have you checked whether there IP address has changed? If you are using a previous session file, try creating a new connection from scratch. Does that help?
@b17, you can either attach them here if they’re not too big, or send them to forum[at]nomachine[dot]com. In the latter case, please reference the title of your topic. Thanks!
Hi Ben, migrating a license to another machine for HW upgrade reasons or when decommissioning the old server is allowed. The only thing you have to be careful of is the Cores don’t change, but that doesn’t affect you since you are using Small Business Server. If in doubt, reach out to the sales team or open a ticket in your customer area. They will be able to provide more details about your SLA terms and conditions.
@Randomin123, 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.
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.