To stay updated on your favorite discussions, please create an account or log in. Then, click the Bookmark icon to subscribe and receive notifications.

Policy Manager v9.00 and Problems with Windows 7 PC's

TechGirl
TechGirl MyAccount Posts: 4 Security Scout
in Business Suite

We seem to have a problem with all of our Windows 7 PC's that we do a push install on from the Central Management Server.  They are not getting updated from the server and are going to the INTERNET to get their updates.  Subsequently our INTERNET bandwidth is being compromised, and our network response time is hindered.

 

Are there some special settings we need to "tweak" or is this version of F-Secure too old to recognise Windows 7.?

Comments

  • MJ-perComp
    MJ-perComp Posts: 669 Firewall Master

    Hi,

    1) Please have a look at the file FSAUA.LOG on the W7-Client, what does it tell you where it looks for updates?

    2) on the W7-Clinet disable http proxy and open the url "<your PMS server>/B" or <your PMS server>:<port>/B". What is the answer?

    3) Did you install all the Hotfixes for PM 9?

    4) What about upgrading to PM10.01?

     

    BR

     

  • TechGirl
    TechGirl MyAccount Posts: 4 Security Scout

    Below is a snapshot of our log.  We have the latest hotfix loaded for our version of Policy Manager.  We haven't upgraded to the lastest PM version as our business just rolled out a new manufacturing NAVISION system in October, and IT has been on hold for a while.

     

     2696]Fri Mar 09 15:08:42 2012(2):  Connecting to http://192.13.10.151:21 (no BW proxy, no HTTP proxy)...
    [ 2696]Fri Mar 09 15:08:42 2012(3):  Update check failed. There was an error connecting http://192.13.10.151:21 (Server error)
    [ 2696]Fri Mar 09 15:08:42 2012(2):  Connecting to fsbwserver.f-secure.com (no BW proxy, no HTTP proxy)...
    [ 2860]Fri Mar 09 15:08:42 2012(3):  Installation of 'F-Secure Universal System Scanner Update 2012-01-09_01' : Success
    [ 2860]Fri Mar 09 15:08:54 2012(3):  Installation of 'F-Secure Hydra Update 2012-03-09_01' : Success
    [ 2860]Fri Mar 09 15:09:02 2012(3):  Installation of 'F-Secure BlackLight Engine Update 2009-09-22_05' : Success
    [ 2860]Fri Mar 09 15:09:12 2012(3):  Installation of 'F-Secure Anti-Virus Misc Update 2011-06-30_01' : Success
    [ 2696]Fri Mar 09 15:12:43 2012(2):  Connecting to http://192.13.10.151:21 (no BW proxy, no HTTP proxy)...
    [ 2696]Fri Mar 09 15:12:43 2012(3):  Update check failed. There was an error connecting http://192.13.10.151:21 (Server error)
    [ 2696]Fri Mar 09 15:12:43 2012(2):  Connecting to fsbwserver.f-secure.com (no BW proxy, no HTTP proxy)...
    [  368]Fri Mar 09 15:23:49 2012(3):  Downloaded 'F-Secure Aquarius Update 2012-03-09_03' - 'aquawin32' version '1331295054' from fsbwserver.f-secure.com, 200688245 bytes (download size 111449554 bytes)
    [ 2696]Fri Mar 09 15:23:49 2012(2):  Update check completed successfully.
    [ 2860]Fri Mar 09 15:25:59 2012(3):  Installation of 'F-Secure Aquarius Update 2012-03-09_03' : Success
    [ 2696]Fri Mar 09 16:23:49 2012(2):  Connecting to http://192.13.10.151:21 (no BW proxy, http://192.13.10.151:21)...
    [ 2696]Fri Mar 09 16:23:49 2012(3):  Update check failed. There was an error connecting http://192.13.10.151:21 via http proxy http://192.13.10.151:21 (Server error)
    [ 2696]Fri Mar 09 16:23:49 2012(2):  Connecting to http://192.13.10.151:21 (no BW proxy, no HTTP proxy)...
    [ 2696]Fri Mar 09 16:23:49 2012(3):  Update check failed. There was an error connecting http://192.13.10.151:21 (Server error)
    [ 2696]Fri Mar 09 16:53:49 2012(2):  Connecting to http://192.13.10.151:21 (no BW proxy, http://192.13.10.151:21)...
    [ 2696]Fri Mar 09 16:53:49 2012(3):  Update check failed. There was an error connecting http://192.13.10.151:21 via http proxy http://192.13.10.151:21 (Server error)

  • MJ-perComp
    MJ-perComp Posts: 669 Firewall Master

    Hm,

    I can hardly beleive that your PMS is using port 21 for communication with the clients.

     

    Please use a browser to access the following URLs from a Client:

    http://192.13.10.151:21

    http://192.13.10.151:21/B

     

    Repaet the same on the PMS itself but with IP=127.0.0.1

     

    What is the output?

    on the server: open start/Programs/F-secure Policy Manager/Status-Monitor

    wait a few seconds. What does it tell you?

     

    BR

  • TechGirl
    TechGirl MyAccount Posts: 4 Security Scout

    Using the 2 different addresses on a client in the browswer just returns an error page.  Using the 127.0.0.1 address in the browser n the PM server, also gives an error.

     

    Going to F-Secure Policy Manager Server Status: - see attachedPolicy Manager Status

  • MJ-perComp
    MJ-perComp Posts: 669 Firewall Master

    Hi,

     

    You need to identify the process on the server that blocks using port 21, which is normally a FTP-Port, no Idea why you changed that.

     

    Use NETSTAT -anp to identify the process, disable that and restart PMS.

     

    If tat is not possible open a support ticket

     

    How many hosts are connected to the PMS?

  • TechGirl
    TechGirl MyAccount Posts: 4 Security Scout

    I have used the Netstat command on the server and it doesn't show anything. 

     

    When I run that command on my XP client computer it says Microsoft FTP. 

     

    When I run the command on my Windows 7 client it does not show any active connections.

     

    We currently have 90 hosts connected. (XP SP3 and Windows 7 32bit and Windows 7 64bit).

     

     

  • etomcat
    etomcat Posts: 1,172 Firewall Master

    Hello,

     

    F-Secure recommends using PMS ports 85, 8085 and 8086 in practice. Use of port 21 looks absolutely wrong.

     

    I think PM9->PM1001 upgrade should not be delayed, firstly because it is not a major work 8automated update) and also because new the products, FSCS 9.31 laptop protection and FSAV ESS 9.20 Win + Exch server protection do require it.

     

    Especially FSAV Win Server 9.00 version is very dated and needs to be upgraded as soon as ESS 9.20 is out, so rolling out FSPM1001 should be high priority as it is a pre-requisite.

     

    Bye, etomcat.

  • MJ-perComp
    MJ-perComp Posts: 669 Firewall Master

    Hi,

     

    please do not upgrade until we have sorted out the port problem!

     

    The recommended/default ports are 80, 8080 and 8081!

     

    please check netstat again using "-?" as a parameter to get the options. One should offer to list the associated processes

    What OS/Version is the Server?

     

  • etomcat
    etomcat Posts: 1,172 Firewall Master

    Hello,

     

    > The recommended/default ports are 80, 8080 and 8081!

     

    They are the default, but they are not recommended, because they are legacy ports from ancient times, when F-Secure PMS was IIS-based. Today, PMS installed on 80 and 8080 would block an IIS or Apache instance, that is possibly used for productive work.

     

    Maybe in Germany most customers have funds to devote a dedicated HW or virtual box to FSPM, but east of Germany that is not necessarily true (zloty / forint / lej not really worth much...) It is a significant selling point for us that FSPMS does not need a dedicated server, just think of all those Windows SBS customers who think they can have File Server, Exchange and comprehensive security in 4-6GB of RAM...

     

    By the way, F-Secure demos and slide shows I've seen use 85/8085/8086 for PMS/PMC/PMWR.

  • daempii
    daempii MyAccount Posts: 7 Security Scout

    This default ports are use everywhere. I think I better try it then. Thanks. image

This discussion has been closed.

Categories