1 Reply Latest reply on Sep 15, 2014 1:18 PM by cplatero

    Client Definition Download Problem LDMS 9.5/6




      We have a problem with our test LDMS 9.6 core.  The issue is with the clients downloading AV definitions from the core, if you initiate the download from the client the update gets to 2% and fails with the message 'Network Operation Timed out'. 

      If i start an AV scan (with definition download) from the console, the client updates itself without any issue.

      The only way i have found to make the download work client side is to turn of the user's proxy server, and the download works fine.   I've tried everything with the proxy exceptions, up to the point of just replacing it with a wildcard and still no success, the only thing that works as i say is completely disabling the proxy server.

      The AV settings are set to download from the core only, and the Kaspersky log file shows it is correctly choosing the update source from the core's LDLOGON directory


      The client and Core server are both located on the local network so shouldn't be too complicated.  Appreciate i've probably missed something, if anyone could possibly shed some light on point me int he right direction i'd be greatful, as i'm not sure where else to go with this!

        • 1. Re: Client Definition Download Problem LDMS 9.5/6
          cplatero SupportEmployee



          That's an interesting one.  And actually reveals a slight difference in how it is being updated.


          When you use the "Update" inside the AV Client it is different than if you used a scheduled task to update.


          When you click "Update" from the client GUI the engine uses the Proxy settings listed in the AV client.


          When starting the update from the console, it sends down a Vulscan Task to run "LDAV.exe /update"


          It sounds like it only fails when the Kaspersky agent itself tries to get the definitions.  This will require some additional troubleshooting.  I recommend you open a support ticket with LANDESK support as we'll likely need to get Kaspersky's help to figure this one out.