Zabbix 6.4 active check is unknown (Monitoring Windows Server)

[Martii]

I have a problem with active monitoring on Zabbix. I set up my lab as follows:

• Zabbix 6.4 (172.16.16.106) on Ubuntu Server 22.04
• Windows Server 2022 (172.16.16.166)
• both machines are in the same network
• the Windows Server 2022 firewall has a rule for inbound port 10050
• in the network there is a Sophos Firewall with IP 172.16.16.254
• I modified the following values in zabbix_agend.conf:
  

  Hostname=Zabbix server

  ServerActive=172.16.16.106

• I can ping both systems from the other one
• I added a template "Windows by Zabbix agent" - and I could see it is working
• after that I added "Windows by Zabbix agent active" to perform active checks

and connected Windows Server to Zabbix. As far as I can see, the passive monitoring is working as intended, but the active monitoring shows me the status "unknown"

After restarting Zabbix services agent on Windows, Windows doesn't show specific logs, but Active Checks status is still unknown:

9032:20240423:155856.369 using configuration file: C:\Program Files\Zabbix Agent\zabbix_agentd.conf 9032:20240423:155856.896 agent #0 started [main process] 9064:20240423:155856.898 agent #1 started [collector] 8008:20240423:155856.901 agent #2 started[listener #1] 5300:20240423:155856.902 agent #3 started[listener #2] 7336:20240423:155856.903 agent #4 started[listener #3] 8288:20240423:155856.904 agent #5 started [active checks #1]

zz0.vamw1a628dzz zz0.ufdbsqfvzcrzz

[cyber]

Hostname=Zabbix server

in agent config it has to be the hosts name there. Passive checks are ok, as your server just asks from given IP, it does not care what is hosts name in config file... but active ones depend on this. Agent sends back data what is marked for that particular name... if it does not match, data will not arrive...

[Martii]

Thanks! I changed it to the hostname of Windows server and it worked.

[ecetin]

Hello!

I solved it by upgrading to same version both server and agent. I use 7.0 for server and my agents were 5.x. Well, I upgraded version of agents and it solved the problem.