Hello everyone,
I’m trying to allow a remote Zabbix proxy to connect to a Zabbix server hosted on my local network. The proxy is configured in active mode, so it initiates the connection to the server. On my side, I’ve opened port 10051 on the firewall and set up a NAT rule pointing to the local IP of the Zabbix server.
I also added a security rule to allow incoming traffic on that port. However, the connection fails. When testing from the proxy with telnet or nc to the public IP and port 10051, I get a timeout.
The Zabbix server is properly listening on that port, and the proxy configuration looks correct. What’s even more strange is that other existing NAT rules for different services don’t seem to work either, even though they’re properly set up and active.
I’m starting to wonder if there’s a broader issue with how NAT or security policies are being handled on the firewall.
If anyone has encountered a similar situation or has any ideas on what I could check, I’d really appreciate your help. Thanks in advance.
I’m trying to allow a remote Zabbix proxy to connect to a Zabbix server hosted on my local network. The proxy is configured in active mode, so it initiates the connection to the server. On my side, I’ve opened port 10051 on the firewall and set up a NAT rule pointing to the local IP of the Zabbix server.
I also added a security rule to allow incoming traffic on that port. However, the connection fails. When testing from the proxy with telnet or nc to the public IP and port 10051, I get a timeout.
The Zabbix server is properly listening on that port, and the proxy configuration looks correct. What’s even more strange is that other existing NAT rules for different services don’t seem to work either, even though they’re properly set up and active.
I’m starting to wonder if there’s a broader issue with how NAT or security policies are being handled on the firewall.
If anyone has encountered a similar situation or has any ideas on what I could check, I’d really appreciate your help. Thanks in advance.
Comment