Connects but shows wrong remote host name

[Arius]

Two Linux Mint 19.3 hosted systems running free NoMachine version 7.6.2.

• Host-A connects to Host-B but NoMachine shows the wrong host name for Host-B.
• Host-B connects to Host-A where NoMachine shows the correct host name for Host-A.
• Host-A can successfully ping Host-B with the latter’s correct host name.
• Nslookup on Host-A for the Host-B ip address shows the correct host name for Host-B.
• The dnsmasq server (pi 4) shows that the Host-B wrong name is set correctly for another system with a different IP address than Host-B.
• I’ve checked both systems with hostnamectl and both /etc/hosts where wrong Host-B name is not present.

How to diagnose this? I am stumped.

[Britgirl]

Hi, can you show me exactly where NoMachine is showing the wrong hostname? Attach the screenshots to your reply.

[Arius]

Screenshot attached from Host A. W7lansvr and Win7nuc are Windows 7 VM’s running under Linux.

Host B shows as FileSvr but should show as Lansvr.

Attachments:

1. 

   Screenshot-from-2021-09-14-10-51-22.png
   

[kroy]

Can you check what the uname -n command shows on that “Host-B” machine? On NoMachine player you should see exactly the same hostname.

[Arius]

uname -n on Host-B shows the name as LANSvr which is correct.

I had previously scanned Host-B but you prompted me to check it again and I found in the Home/.nx directory references to FileSvr for the local system. So I used Synaptic to remove NoMachine and deleted the .nx from Home and then reinstalled NoMachine.

Now all is working correctly. I must have made a mistake somewhere along the line.

Thanks for pushing me over the line to get my mistake fixed.

[kroy]

Thanks for letting us know.
It’s not necessary to remove NoMachine. Network broadcasting informations are cached in ~/.nx/cache folder – to clear remove correct .nxs file or remove all files from that directory.

[Author]

Posts