our Core Server (Landesk 8.8sp1) is behind NAT and as mentioned in the topic, i have a problem to deploy software to clients which are outside the core network.
Everything else seems to work fine, only packages with dependencies fail every time the package is pushed. Some time later usually the policy invoker requests the same task from the Server (policy-based push is used to deploy the task) and installs the package without any errors. There are no problems if a package without dependencies is pushed.
The task log looks like this:
Processing package : Ingres Soft1 - Install
Thu, 11 Sep 2008 06:46:49 Error -2145844745 (0x801901f7) occured when downloading the dependency manifest 'http://[email protected]/ldlogon/FileLists/taskmanifest.25.CORE-SERVER-NAME301.881.cab'
Thu, 11 Sep 2008 06:46:49 Failed to download the dependency manifest
Thu, 11 Sep 2008 06:46:49 processing of package is complete, result -1918091222 (0x8dac402a - code 16426)
Thu, 11 Sep 2008 06:50:03 Core name 'CORE-SERVER-NAME:NAT-CORE-SERVER-IP' obtained from active task list
Thu, 11 Sep 2008 06:50:03 Sending task status, cmd line -coreandip=CORE-SERVER-NAME:NAT-CORE-SERVER-IP -taskid=301 -retcode=229392397
Thu, 11 Sep 2008 06:50:03 MSI Client Thread
Thu, 11 Sep 2008 06:50:04 Checking preferred server path
PREFERRED-SERVER-NAME\pakete\Ingres_2_6\Installation\Ingres.msi instead of
NAT-CORE-SERVER-IP = Core Server IP, behind NAT (cant be reached from outside)
CORE-SERVER-NAME = Core Server Name (can be resolved and reached from outside)
it looks like the Core Server sends his IP (wrong one, in this case) to the client.
Internal Server IP cant be reached and the task fails. But why doesn's the Core Server use the Hostname?
I would appreciate any hints how to solve this problem.