Why does it take 10-20 minutes for the computer to appear in MeshCentral after I run the agent? Is there something I didn’t set up correctly?

[xian-yuwang]

Why does it take 10-20 minutes for the computer to appear in MeshCentral after I run the agent? Is there something I didn’t set up correctly?

[si458]

This could be a number of reasons

(My example, why did my cars broke down randomly? Well did i forget to put fuel in, did i have a flat tyre, did someone put diesel in my unleaded engine and try sabotage me?)

Can u share ur config.json (sanitised https://sanitizer.meshcentraltools.com)

[xian-yuwang]

First of all, thank you very much for your reply. I have uploaded the config.json file. Please take a look. Thank you.
sanitized-config.json

[si458]

Ok so ur config.jsok is setup to work only internally and it uses multicast packets, so all ur machines need to be on the same network as ur meshcentral server to work and they all need to be able to receive the multicast packets too

Also we are aware the linux agent might not work correctly in lanonly mode because of the multicast packets

[xian-yuwang]

Is there any remedial measure available? Here, I am using Rocky Linux 9.7 as the MeshCentral server, with clients running Windows 10 and Windows 7. The server's IP segment is 192.168.1.0, while some clients are on 192.168.1.0 and others are on 192.168.2.0.

[si458]

so you would need to use meshcentral as it was intended with a DNS value set for cert and remove lanonly then it runs in WAN+LAN mode, then you make sure the remote devices can resolve the DNS to your meshcentrals IP address
you can use a service like nio.io or sslip.io which converts say meshcentral.10-0-0-99.sslip.io or meshcentral.192.168.1.66.nio.io to the IP addresses in the dns value but this should ONLY be used for testing purposes! as you cannot change the CERT value AFTER you have installed meshagent on remote devices WITHOUT having to uninstall the meshagent on the remote machines and then redownloading and reinstalling all the meshagents again

[xian-yuwang]

Currently, my configuration has been updated. For details, please refer to the attachment. Additionally, an A record has been added to the DNS server for the MeshCentral server, pointing to the server's IP address. Client machines can successfully resolve the MeshCentral domain name to the server's IP when pinging it directly, and communication is normal. Furthermore, the latency issue has now been resolved. Thank you very much for your help.
sanitized-config.json