Fsecure client not update through PM Proxy

Aspirant

Fsecure client not update through PM Proxy

We have upgrade our Policy Manager server to 11. All the branches are connecting to PM server through policy manager proxy.  Branch pc's are using f-secure client security 9.x. We have set " Allow falling back to PMS if PMP is inaccessible =no" setting on PM server for each branch. These branches are not getting update. Last update it shows is "2013-09-18_01".  When we set  " Allow falling back to PMS if PMP is inaccessible =yes" branches are getting update. Due to the high bandwith consumption we are not allowed this setting to yes. Pls help us to resolve this issue.

3 REPLIES 3
F-Secure Product Expert
F-Secure Product Expert

Re: Fsecure client not update through PM Proxy

Hello Thenu,

 

Your Policy Manager Proxy(PMP) seems to have issues. You could try to check the troubleshooting section of the admin guide to clarify the status of the PMP.

http://www.f-secure.com/en/c/document_library/get_file?uuid=bbb4938b-9561-4808-8a98-37647ff8b6d7&gro...

 

If the issue cannot be solved you might want to open a support ticket (include an fsdiag to speed up the process).

 

Thank you



Best Regards

-Ben

_________________________________

Has somebody helped you? Say thanks by giving likes. Has your issue been solved? Mark the post using "Accept As Solution" button to let others know.
Aspirant

Re: Fsecure client not update through PM Proxy

This happened to the all branches connect through policy manager proxies. All the branches have policy manager proxy version 2.0. So it can't be a issue on policy manager proxy as per my undersatnding.  When I checked the fsaua log in client pc it displays error as " 

 

308]Wed Oct 09 08:41:22 2013(2):  Connection to PMS denied without PMProxy by policy (1)
[  308]Wed Oct 09 08:41:22 2013(3):  Update check failed. There was an error connecting http://192.168.100.32:34420 (Unspecified error)
[  308]Wed Oct 09 08:41:22 2013(2):  Connection to PMS denied without PMProxy by policy (1)
[  308]Wed Oct 09 08:41:22 2013(3):  Update check failed. There was an error connecting http://192.168.100.32:34420 (Unspecified error)
[  308]Wed Oct 09 09:49:16 2013(2):  Connecting to http://192.168.100.32:34420 (http://192.168.173.100:34421, no HTTP proxy)...
[  308]Wed Oct 09 09:51:22 2013(3):  Update check failed. There was an error connecting http://192.168.100.32:34420 via update proxy http://192.168.173.100:34421 (Connection lost)

[  308]Wed Oct 09 09:51:22 2013(2):  Connection to PMS denied without PMProxy by policy (1)
[  308]Wed Oct 09 09:51:22 2013(3):  Update check failed. There was an error connecting http://192.168.100.32:34420 (Unspecified error)
[  308]Wed Oct 09 09:51:22 2013(2):  Connection to PMS denied without PMProxy by policy (1)
[  308]Wed Oct 09 09:51:22 2013(3):  Update check failed. There was an error connecting http://192.168.100.32:34420 (Unspecified error)

 

F-Secure Employee

Re: Fsecure client not update through PM Proxy

Hello thenu,

 

I would suggest that you take an FSDIAG from the server where Policy Manager Proxy is installed and one from the client workstation and open a support ticket as per Bens instructions.