Fire on_demand Event creates [Errno -2] Name or service ...

[Earwain]

Hi,

I think I know what's happening, just looking for confirmation.

Our OPSI server is in our (service provider) domain, let's say FOO.COM
We have a Depot server at a customer, say BAR.COM
The only config server is at our domain, say the config server is opsi.foo.com

opsi.foo.com and opsidepot.bar.com are publicly accessible FQDN's, so the servers can communicate for package updates etc.

However, the clients at bar.com, say client1.bar.com is not publicly accessible, since we cannot list all client dns records on the internet.
I believe that's why the OPSI config server @ opsi.foo.com cannot "send" the trigger event to the client at client1.bar.com.

Is this correct? Could this be tackled in a future OPSI version by having the local depot server "forward" such an action, since "opsidepot.bar.com" can of course reach "client1.bar.com"!

Thanks
Krgds
Koen.

[d.oertel]

Hi,

sorry for the late answer.

Yes - your right.
It would be better to do all connections to the clients through the depot server.
To change this will take about 8 hours work. So if anybody likes to spend the money for this we will do it.

regards

d.oertel