Britgirl

[Britgirl]

Hi Gabriele,

we’ll use the logs file you submitted directly to us. Thanks!

[Britgirl]

You’ve successfully logged in. You say it’s unresponsive, but from the logs it appears to be a network connection issue. The automatic reconnect kicks in when the network connection is lost for whatever reason. It could be a network issue on the client side. Are you able to ping IP_server-host from the connecting client when it happens?

It could also be a network problem on the server side. Ideally, we would need server side logs to see what is happening and they would also confirm whether it’s being caused by the connection being lost or some other issue.

Logs can be sent directly to forum[at]nomachine.com[dot]com. Instructions to extract them are here: https://www.nomachine.com/AR10K00697

[Britgirl]

@alfa111, sorry for the delay in getting back to you. We’re still investigating and will update the topic soon.

[Britgirl]

Ok 🙂 Thanks for letting us know.

[Britgirl]

Hi, when prompted to log in, you should use the username and password of your account on the remote PC (fig.7 here https://www.nomachine.com/getting-started-with-nomachine)

No empty passwords are allowed by the way (see this article for more information about that: https://www.nomachine.com/AR05L00802)

You say that it doesn’t work. Can you tell me what message you are getting (a screenshot would be useful)?

[Britgirl]

Here is the associated Trouble Report. By clicking on ‘Notify me’ you can sign up to receive notification of when a fix has been released.

https://www.nomachine.com/TR12P09027

[Britgirl]

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!

[Britgirl]

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?

[Britgirl]

@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!

[Britgirl]

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.

[Britgirl]

@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/TR11P08992

Follow the link and sign up to be notified when a fix is available.

[Britgirl]

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/TR11P08992

Follow the link and sign up to be notified when a fix is available.

[Britgirl]

@netyoda, did reinstalling help? If you’re still having the same problem, let us know.

[Britgirl]

@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.

[Britgirl]

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?

[Author]

Posts