Britgirl

[Britgirl]

The default is set to ‘0’. If you wanted to change it and set it to ‘1’ (but I doubt it would change anything because this key was inserted to mitigate a problem coming from old packages), then you would need to remove the #.

@JimH24, the logs you sent didn’t show anything strange. Do this instead: from inside the NoMachine session, open a terminal and execute this command:

xev -event keyboard

then press the not working keys and copy the output you get in the terminal. Paste it here or submit a screenshot.

[Britgirl]

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.

https://www.nomachine.com/DT10O00163#2

Btw, from the logs you did submit, it seems that you didn’t reboot.

[Britgirl]

There is a Trouble Report currently open specifically for Windows 10, update 1903. What specific version of Win10 do you have installed?

https://www.nomachine.com/TR05Q09310

[Britgirl]

Ok, please make sure you reference the title of your topic in the subject of your email 🙂

[Britgirl]

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.

[Britgirl]

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?

[Britgirl]

hi, what DE is it?

The TR referenced is rather old and concerns version 4, no longer supported. If there is a new bug, we’d need to start a new investigation for the latest NoMachine 6 packages.

We test with as many environments as possible and AFAIK don’t have problems with arrow keys.

Can you check that you have # AgentLegacyKeyboard 0 in the node.cfg. ‘0’ is the default setting (although it would be odd that you have it set at ‘1’).

Enable logs, reproduce and submit them to forum[at]nomachine[dot]com. For safe measure submit both server side and client side logs.

Instructions are here: https://www.nomachine.com/AR10K00697

[Britgirl]

If you are logged in to the OS locally (ie. not via NoMachine software), then it is possible to have a user connect (via NoMachine or Enterprise Client) 🙂 This is still only one connection for us. Maybe this is what happened.

 

Do I understand it correctly that if I buy the 10pack version for Windows, it means I can only install that version on Windows VMs? and if I had some VMs running Linux/MacOS I’d need to buy those packages individually?

That is correct. Unfortunately, whilst it’s possible to select a mix of Linux distros for the remote servers, you can’t mix Win/Mac and Linux. You would need to opt for individual ones BUT talk with the sales team about pricing because special arrangements can be made.

Happy nomachining!

[Britgirl]

Just ensure you put the title of the topic as your subject 😉

[Britgirl]

This article will help you to discover if you have double NAT or not: https://www.pcworld.com/article/3175739/how-to-identify-and-resolve-double-nat-problems.html. The last section provides some tips which you can follow.

You can submit your screenshot by all means – please submit it to forum[at]nomachine[dot]com, not here because it will be visible to everyone.

[Britgirl]

What version of NoMachine do you have installed on the server and client sides?

[Britgirl]

With a double NAT there’s not much you can do. Take a look here: https://forums.nomachine.com/topic/problems-connecting-to-one-remote-computer

All you can do is wait for NoMachine Network to be released.

[Britgirl]

I think what you need is Workstation. It would probably fit your scenario better than the free version. You could try the evaluation version.

[Britgirl]

The best thing to do is to sign up to the ‘notify me’ to know when a fix has been released.

[Britgirl]

Hmm. The free version of NoMachine does not limit access to LAN only, I just want to make that clear.

So it must be something else. I suggest you try the following:

1) Uninstall (removing all traces completely) and reinstall. Your screenshot shows no !M icon (which is an indication of the server running) plus your screenshot actually says ‘no server running’. If the server was running, it would show the External IP.

2) If you continue to not see the External IP, from a terminal on the server please run:

sudo /usr/NX/bin/nxserver --upnpmap
sudo /usr/NX/bin/nxserver --upnpstatus

It should show something like this:

sudo /usr/NX/bin/nxserver --upnpstatus
Local IP                   10.0.1.XX
Gateway IP                 10.0.1.1
External IP                XX.XXX.XXX.XXX
NX port 4000 mapped to:    XX.XXX.XXX.XXX:23484

3) See the following article: https://www.nomachine.com/AR11L00827

If your home router doesn’t accept UPnP or NAT-PMP commands, it will be necessary to configure it through the router’s admin interface

[Author]

Posts