January 24, 2020 at 10:52 #25355
I installed NoMachine first time on my Windows 10 computer. I checked several times the connection settings and my login data and it’s fine. But if I try to connect, I get an “authentication failed. try again”. If I use the same settings on my colleague’s computer, it works.
I already checked: I use the last version, have a Windows 10 system and admin rights, didn’t forgot any cross or number in the settings.
What can I do to get access?January 24, 2020 at 14:57 #25366
First, can you try a ‘Reset saved preferences and password’? To do that, right click on the connection icon in the GUI and choose Edit. Tick the box ‘Reset saved preferences and password’, then click ‘ok’. Try logging in again.
If that doesn’t help, you need to tell us how you are authenticating – is it via password, private key or kerberos?January 24, 2020 at 15:52 #25367
I did this reset, but still not log in. I have to use authentication via password.January 24, 2020 at 16:13 #25369
Is the remote server you are connecting to version 6?
I noticed from your original post that you mention “a colleague’s computer”. If you are trying to connect to your organization’s server, it might be better to check that the administrator of the server has not changed something (such as only allowing certain clients to connect).
The logs would be useful at this point to understand what authentication fails. Please submit to forum[at]nomachine[dot]com. Instructions are here: https://www.nomachine.com/AR10K00697.
If you are also administrator of the server, submit those as well. If you are not and the NoMachine server has a valid subscription, it would be better to ask your Administrator to submit a support ticket.January 24, 2020 at 16:30 #25372
I don’t know the version of the organization’s server. Does it make a difference? I tried the version offered from the organization (5) and the last version of 6. Both cases doesn’t work. They also offered download on there side for Windows and Linux (no version mentioned).January 24, 2020 at 16:30 #25373
And you should received an email with the log dataJanuary 24, 2020 at 16:44 #25378
It shouldn’t make much difference what version you are using, but as I said previously, you should check with the administrator of the server whether something has changed (edit: we also need to be sure that they have installed an updated server version)
Logs are from your client but do not include the Player logs. This is what I need to see in order to help. In the meantime, you could ask your administrator to open a ticket with our support team so they can investigate properly why you are not able to connect.
Btw, from the logs you did submit, it seems that you didn’t reboot.February 11, 2020 at 08:44 #25566Ice_BirdParticipant
I have something similar issue.
I have two PC at home one with Win7 the other is Win10.
When I installed NoMachine for both of them. They found each other via local network (wi-fi). Than, does not matter what I do, what kind of user I create. I got this authentication failed. Btw I want to connect from Win10 to Win7 machine.
What I am missing?February 11, 2020 at 09:57 #25579
Sorry for the long break. I had to wait for response from the admin. However, the settings should be fine. My colleague is able to log in/authentificate using my computer and I can log in with my account in anything except NoMachine. The administrator also said, that I don’t need special permission for NoMachine.February 11, 2020 at 13:01 #25588
@Icebird, can you submit a separate topic with details of the error you are getting, a screenshot would be useful. Thanks!February 11, 2020 at 17:32 #25600og00rContributor
In received logs there are only logs from client side, which is not enough to proceed with problem.
Please enable logs on server side reproduce the problem and send them if possible.
Here is article how to do this:
At this moment all can I say, is that connection is closed after entering username to login procedure.
Please ensure that account name is correct and user is active in system.
You must be logged in to reply to this topic.