Views:

To resolve the issue, follow the procedure for the scenario that applies to you:

Third party applications cannot be accessed via HTTP protocol and adding them in the global approved URL list does not resolve the issue. For example, accessing IP cameras via web browser does not work.

  1. Open the ..\PCCSRV\ofcscan.ini file using a text editor like Notepad.
  2. Under the [Global Setting] section, add the following parameters:
    • SEG_WhiteListIPNum=1
    • SEG_WhiteListIP0="<IP address of the device/server that cannot be accessed>"
     
    The maximum value for "SEG_WhiteListIPNum" is "10".
     
  3. Save and close the file.
  4. Log on to the WFBS console. Go to Preferences > Global Settings - Desktop/Server.
  5. Click Save to deploy the settings to the clients.
  6. Test if the issue is resolved. If the issue still persists, double-check if the deployment was successful using the following steps:
    1. Open the Registry Editor of an affected client computer.
    2. Check if the HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\NSC\TmProxy\WhiteList\SEG_WhitelistIP0 registry key exists.

Application communication via HTTP protocol is blocked and adding them in the global approved URL list does not prevent the issue.

 
Do not safelist the web browser itself, like iexplorer.exe or firefox.exe, for this will disable Web Reputation Service and URL Filtering completely.
 
  1. If you are using WFBS 7.0, make sure that hot fix build 1495 is installed. If you are using WFBS 7.0 SP1, proceed to Step 2.
  2. Enable the approved TMProxy process approved list deployment feature.
    1. Open the ..\PCCSRV\ofcscan.ini file using a text editor like Notepad.
    2. Under the [Global Setting] section, add the following parameters and assign an appropriate value for each:
      • SEG_WhiteListProcNum=x

        where "x" is the number of approved process (maximum is "10".)

      • SEG_WhiteListProc0=ABC.exe
        SEG_WhiteListProc1=DEF.exe
        .
        .
        .
        SEG_WhiteListProc9=XYZ.exe

        where: "ABC.exe", "DEF.exe", and "XYZ.exe" are user-approved process names.

    3. Log on to the WFBS console and go to Networked Computers > Global Client Settings.
    4. Click Save to deploy the setting to clients.

      After the global settings are deployed to WFBS client computers, the following registry keys will be installed in [HKLM\SOFTWARE\TrendMicro\NSC\TmProxy\WhiteList]:

      • SEG_WhiteListProcNum=x (DWORD) - This specifies the number of approved processes.
      • SEG_WhiteListProc0=ABC.exe (String) - This specifies a user-approved process name.
      • SEG_WhiteListProc1=DEF.exe (String) - This specifies a user-approved process name.
      • SEG_WhiteListProc9=XYZ.exe (String) - This specifies a user-approved process name.
        The following installed subkeys are based on the number of processes you specified in the "SEG_WhiteListProcNum" key:
      • Path: [HKLM\SOFTWARE\TrendMicro\NSC\TmProxy\WhiteList\ABC]
        Name: ProcessImageName
        Type: REG_SZ
        Data: ABC.exe
      • Path: [HKLM\SOFTWARE\TrendMicro\NSC\TmProxy\WhiteList\DEF]
        Name: ProcessImageName
        Type: REG_SZ
        Data: DEF.exe
    5. Restart the Worry-Free Business Security NT proxy service on client computers.
  3. Test if the issue still occurs.

If an application (.exe) is still blocked after being added using the procedure in Step 2.b, open the folder containing the application then list all the .exe and .dll files present. Add each one by one as explained in Step 2.b, ensuring that all dependencies for this application get safelisted as well for the application to work.