Cristian The issue you are describing is not a valid reason for disabling a feature like this. Enabling cache on the client should allow the client to store details on the workstation which will stop the client from needing to do an update when connecting for the second time. If cache is enabled already and the files are not getting updated but the check process is slow then you may need to look at your network. BUT before going down any troubleshooting path, I notice from your graphic that your client version shows 184.108.40.206….You said " I don't understand but why broadcom put this fix but don't working the solution" . How do you know if Broadcom is not working on this problem when it does not look like you have updated since 3.0 ….We are close to ending support for 3.2 and you have not upgraded. This may simply be because you client version hasn't upgraded but that would be even worse because there would be a lot of fixes you are missing. I strongly suggest you upgrade your systems to the latest versions ( 3.3.2 ) and then if you cannot figure out why the cache feature is not working on 3.3 you can open a ticket with support to assist you in evaluating your network and configuration.