Windows .bat files with unexpected results through proxy

[markl]

We have repeated issues where a bat script that works fine on the windows server does not work through the proxy (4.0). We found that putting REM statements in various places fixes the issue which is totally bizarre. Anyone else experience this behaviour and know how to resolve it?

For ref, all of our scripts are passed in parameters and all return a numeric value.

Thanks,

Mark.

[dimir]

Timeout issue?

[markl]

Hi Dimir.

I don't think so. The response is pretty instantaneous when testing the key using zabbix_get on the proxy. The strange thing is that running through zabbix_get gives script errors that don't occur when you run directory from the cmd prompt on the windows server.

[dimir]

The response is pretty instantaneous when testing the key using zabbix_get on the proxy.

You mean "using zabbix_get on the agent that runs on the same host as proxy"?

[markl]

Sorry, no.

We have proxies setup using ubuntu 18.04 and docker containers. The zabbix_get was run on the docker container to check the key on the remote windows server.

[dimir]

You realize zabbix_get talks to zabbix agent only?