April 9, 2020 at 07:43 #26629
How can I clear a NoMachine client’s cache of dynamically discovered LAN servers?
On my home network I have a collection of CentOS 7.7 and Windows 10 computers that all act as both clients and servers. Initially I let my computers dynamically discover each other, but I found that sometimes there’d be a delay before a dynamically discovered server would appear in a NoMachine client window. Therefore I’ve decided to statically configure all the server connections on each of my clients (I only have a few PCs at home, so this didn’t take long).
At the same time in each computer’s Server Preferences->Services I also unchecked “Advertise this computer on the local network”. Therefore I shouldn’t have any more dynamically discovered servers. However (now that I’ve statically defined connections for all of my servers), I now have two connections listed for each server (the manually created connection and the cached dynamic LAN connection).
On my CentOS 7 client I tried clearing out the “~/.nx/cache” folder, but this didn’t help.
According to https://forums.nomachine.com/topic/cant-delete-old-session#post-23807 “Old servers discovered in LAN could stay in the cache for a few hours before being completely removed”, but in my testing they’ve stayed for for days (and counting).
NoMachine 6.9.2 free version
Windows Client and Server = Windows 10 Pro x64 Version 1909
Linux Client and Server = CentOS 7.7.1908 with the default Gnome 28April 9, 2020 at 13:53 #26650kroyContributor
We weren’t able to reproduce such problem.
At the same time in each computer’s Server Preferences->Services I also unchecked “Advertise this computer on the local network”.
Did you restart nxserver after after making changes? It’s needed to take effect.April 9, 2020 at 14:32 #26653
Yes, I restarted nxserver after making the changes. What protocol/port does nxserver use to advertise its presence? For example TCP or UDP port 4000? With that info I can take a packet capture to check if my servers are still advertising their presence.April 15, 2020 at 19:31 #26775brotechParticipant
NX is using MDNS protocol for advertise its presence to other NoMachine computers, visible for example in third party tool – Wireshark.April 20, 2020 at 08:41 #26889
I’m sorry, this was my mistake. I thought I restarted all the servers, but when I went back and checked I had forgotten to restart a couple of them. I had assumed it was all of my servers re-populating my connection list when in fact it was just these two. After I restarted these two servers I no longer have any dynamically discovered servers in my list. I did use Wireshark to check out MDNS traffic on my network and discovered I have several devices using it, but no more NoMachine servers advertising themselves.
So sorry for the noise/misinformation, but thanks for the help.
This topic was marked as solved, you can't post.