net.tcp.port fails if target is down

[RobertS]

Hi,

I want to monitor port 3389 on a server with [net.tcp.port[10.20.1.103,3389]]. As long as the server is up the results are as expected, but when the server goes down the status is not updated anymore an keeps as OK ("1" on 1.1.3; "0" on previous) which is not exactly correct on a shutdown server. Zabbix Server is 1.1.2, Agent is Windows 1.1.2

zabbix_server.log
009243:20061025:111821 Getting value of [net.tcp.port[10.20.1.103,3389]] from host [work] failed
009243:20061025:111821 The value is not stored in database.

Thanks for help,
Robert

[RobertS]

I now trigger on nodata() also.

eg.
({mypc:net.tcp.port[2.1.17.5,5019].last(0)}#1)|({mypc:net.tcp.port[2.1.17.5,5019].nodata(120)}=1)

[cadbury]

to monitor a host status, I always set an icmpping as the condition to other triggers.
when the icmpping is false, no need to care about other values.

[RobertS]

The problem is that the port I want to monitor is on an external server which is only reachable from one host in my network. It's a Windows host with a VPN conntection to the external server doing the net.tcp.port. So I have to monitor if my host can reach the external server and if the port on the external server is reachable.

As I understand icmpping is always send from the Zabbix Server an there is no (built in) way to check if a Zabbix Agent can ping a single server.

[cadbury]

ok I see the problem

if your solution works, all right
you can also set a simple script on the windows server that will ping what you want, but you may not need it now

[bashman]

Problem still persists on Zabbix agent (win) v1.8.4:

https://support.zabbix.com/browse/ZBX-3437