Zabbix agent / agent2 on CentOS 9.7 - server cannot connect.

[Motok]

Hey there,
I have a working Zabbix server 7.0 LTS with some hosts, Windows and Linux, everything is going fine.
Today, I have just installed a new virtual machine with Linux CentOS 9.7 with Zabbix agent / agent2 (tried both) but i cannot connect from server.
They are both on same VLAN, server IP is 192.168.100.42 and client IP is 192.168.100.25.

When i m trying to netcat from server into client on port 10050 :

nc -zv 192.168.100.25 10050
myhost.domain.local [192.168.100.25] 10050 (zabbix-agent) : No route to host

But it s working when i m trying others ports, like 80 and 443 :

nc -zv 192.168.100.25 80
myhost.domain.local [192.168.100.25] 80 (http) open

I did checked the open ports on the client :

tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      2555/docker-proxy  
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      2533/docker-proxy  
tcp        0      0 0.0.0.0:10050           0.0.0.0:*               LISTEN      967/zabbix_agentd  
tcp        0      0 0.0.0.0:8022            0.0.0.0:*               LISTEN      952/sshd: /usr/sbin
tcp        0      0 0.0.0.0:62354           0.0.0.0:*               LISTEN      948/glpi-agent: wai
tcp6       0      0 :::443                  :::*                    LISTEN      2561/docker-proxy  
tcp6       0      0 :::80                   :::*                    LISTEN      2542/docker-proxy  
tcp6       0      0 :::10050                :::*                    LISTEN      967/zabbix_agentd  
tcp6       0      0 :::8022                 :::*                    LISTEN      952/sshd: /usr/sbin

I did tried to remove SELinux :

sestatus
SELinux status:                 disabled
getenforce
Disabled

I disabled the firewall iptables too :

iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination​]

I m still stucked any ideas ?

Many thanks

[Motok]

I m answering to myself, the service firewalld was active on the ens33 and i added a rule for port 10050.
What got me in the wrong way was the message "No route to host".

[Motok]

I m answering to myself, the service firewalld was active on the ens33 and i added a rule for port 10050.
What got me in the wrong way was the message "No route to host".

[Motok]

The topic can be closed, thank you.