New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MeshAgents went offline. Cannot re-add or reestablish communication outside server subnet. #5992
Comments
right so meshcentral is running in LAN mode, because you havent set a |
I removed CYNET from the machine meshcentral is hosted on as well as from a remote machine with the mesh agent on it and it did not seem to fix the issue. Is there a service name I should be looking for? C:\meshcentral\WinService\daemon\meshcentral.exe is listed on the host machine as the service. I did further test this on a machine that is not and has never been protected by CYNET and was still unable to communicate with the machine via meshagent but can ping and RDP into it. Thanks. |
yes thats the daemon to run the service, |
OK. I will check with our system manager on adding exceptions for node.exe and meshagent.exe All of the unresponsive remote machines I have tested can reach the MC server address without issue. Here is the current output from the show server configuration: { Thanks |
If each node can see the web interface then it shouod be OK, so it must be something else. If u run the meshagent.exe on a node, u should get a panel, if u click the info button it should show more information. Can u share a screenshot of it? Also I would also check the command line console for the meshcentral and see if the is any errors being shown |
As a side note, I set up another instance of MC on another machine which is located on the same network as my host I am having issues with. I was able to add and connect machines across all subnets without issue. That seems to confirm that something is wrong with my MC instance an it is not related to antivirus, firewalls or security. I really appreciate your time on this. Thanks! |
dont run 2 meshcentral instances at the same time, this will confuse the agents!! |
Ok. So, no further investigation at this time is needed it sounds like. Is there any way to get my existing agents to respond to a new instance of MC? Thanks. |
Sadly this is only possible if u have setup the the machines with a dns name. As with a dns name, u would just point it to the new vm ip, copy over meshcentral-data and away u go. But u could try doing that as ur only using local? Copy the whole meshcentral-data from old to new. |
Windows Mesh Agents no longer communicating with MC server
Not sure this can be reproduced as a bug. Apologies if this is the wrong area to ask.
Expected behavior
I expect to see network devices online and to be reached through MC web gui but they are not.
Screenshots
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
Agent Time: 2024-04-04 11:55:03.835-05:00.
User Rights: 0xffffffff.
Platform: win32.
Capabilities: 15.
Server URL: wss://10.2.200.71:443/agent.ashx.
OS: Microsoft Windows 10 Pro - 22H2/19045.
Modules: amt-apfclient, amt-lme, amt-manage, amt-mei, computer-identifiers, monitor-border, smbios, sysinfo, util-agentlog, wifi-scanner-windows, wifi-scanner, win-console, win-deskutils, win-info, win-securitycenter, win-terminal, win-virtual-terminal, win-volumes.
Server Connection: true, State: 1.
Application Location: C:\Program Files\Mesh Agent\
this is the only device that remains online and is located on the same subnet as the server.
Additional context
Add any other context about the problem here.
json config file remains the same as it was at install. I made no changes and everything worked out of the box so to speak.
All AMT enabled devices are discovered and have an agent on them but I am unable to communicate with them.
Your config.json file
The text was updated successfully, but these errors were encountered: