0

I have 1 Wazuh server and 2 Windows 10 agent machines.

Wazuh Manager: 10.1.0.3
Agent1: 10.0.2.2
Agent2: 10.1.0.4

All firewall rules are turned off and set to ALLOW ALL

Wazuh itself is functioning as it is supposed to. We know Wazuh functions proporly because one of the Windows agents can connect. The successful agent is my primary Windows machine. Wazuh is not the issue. The failed agent is.

The failed agent is a fresh Windows 10 Pro install on a Proxmox virtual machine. This machine can successfully access the Wazuh dashboard, but can NOT connect the agent. Which means there is no network failure.

Here are the settings I use to create the agent for the failed machine.

Package: Windows

Server Address: 10.1.0.3

Agent Name: WINDOWS10

Group: default

ran the following command as administrator

Invoke-WebRequest -Uri https://packages.wazuh.com/4.x/windows/wazuh-agent-4.9.2-1.msi -OutFile $env:tmp\wazuh-agent; msiexec.exe /i $env:tmp\wazuh-agent /q WAZUH_MANAGER='10.1.0.3' 

NET START WazuhSvc
"The Wazuh service started sucesfully"

Used the following Ubuntu command on the Wazuh manager to see if the new agent is listed in the system. It is not

/var/ossec/bin/agent_control -l
    Wazuh agent_control. List of available agents:
   ID: 000, Name: WAZUH (server), IP: 127.0.0.1, Active/Local
   ID: 001, Name: FLAGSHIP, IP: any, Active

OSSEC agent log keeps saying the management interface has not been configured and the default route 0.0.0.0 is being used

2025/01/04 16:10:06 wazuh-agent: ERROR: (4112): Invalid server address found: '0.0.0.0'
2025/01/04 16:10:06 wazuh-agent: ERROR: (1215): No client configured. Exiting.
2025/01/04 16:10:06 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/01/04 16:10:06 wazuh-agent: INFO: Set pending exit signal.
2025/01/04 16:10:34 wazuh-agent: ERROR: (4112): Invalid server address found: '0.0.0.0'
2025/01/04 16:10:34 wazuh-agent: ERROR: (1215): No client configured. Exiting.
2025/01/04 16:10:34 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/01/04 16:10:34 wazuh-agent: INFO: Set pending exit signal.
2025/01/04 16:21:17 wazuh-agent: ERROR: (4112): Invalid server address found: '0.0.0.0'
2025/01/04 16:21:17 wazuh-agent: ERROR: (1215): No client configured. Exiting.
2025/01/04 16:21:17 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/01/04 16:21:17 wazuh-agent: INFO: Set pending exit signal.
2025/01/04 16:26:45 wazuh-agent: ERROR: (4112): Invalid server address found: '0.0.0.0'
2025/01/04 16:26:45 wazuh-agent: ERROR: (1215): No client configured. Exiting.
2025/01/04 16:26:45 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/01/04 16:26:45 wazuh-agent: INFO: Set pending exit signal.
2025/01/04 17:48:31 wazuh-agent: ERROR: (4112): Invalid server address found: '0.0.0.0'
2025/01/04 17:48:31 wazuh-agent: ERROR: (1215): No client configured. Exiting.
2025/01/04 17:48:31 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/01/04 17:48:31 wazuh-agent: INFO: Set pending exit signal.
2025/01/04 17:50:00 wazuh-agent: ERROR: (4112): Invalid server address found: '0.0.0.0'
2025/01/04 17:50:00 wazuh-agent: ERROR: (1215): No client configured. Exiting.
2025/01/04 17:50:00 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/01/04 17:50:00 wazuh-agent: INFO: Set pending exit signal.
2025/01/04 17:50:00 wazuh-agent: INFO: Exit completed successfully.
2025/01/04 22:33:44 agent-auth: INFO: Started (pid: 10580).
2025/01/04 22:33:44 agent-auth: ERROR: Manager IP not set.
2025/01/04 22:35:29 wazuh-agent: ERROR: (4112): Invalid server address found: '0.0.0.0'
2025/01/04 22:35:29 wazuh-agent: ERROR: (1215): No client configured. Exiting.
2025/01/04 22:35:29 wazuh-agent: INFO: Received exit signal. Starting exit process.
2025/01/04 22:35:29 wazuh-agent: INFO: Set pending exit signal.
2025/01/04 22:35:29 wazuh-agent: INFO: Exit completed successfully.

1 Answer 1

0

Manually changed the server IP address in C:\Program Files (x86)\ossec-agent\ossec.conf

    <server>
      <address>10.1.0.3</address>
      <port>1514</port>
      <protocol>tcp</protocol>
    </server>

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.