Many 5159 events are logged in the Security event log after you disable Windows Firewall and enable the "Filtering Platform Connection" auditing policy
On a computer that is running Windows Vista or Windows Server 2008, you disable Windows Firewall for the Domain profile, the Private profile and the Public profile.
You enable the "Filtering Platform Connection" audit policy.
In this scenario, the following Event ID 5159 is logged many times in the Security event log:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Event ID: 5159
Task Category: Filtering Platform Connection
Level: Information
Keywords: Audit Failure
User: N/A
Description:
The Windows Filtering Platform has blocked a bind to a local port.
Application Information:
Process ID: process ID
Application Name: %path to some application%
Network Information:
Source Address: IP address
Source Port: port number
Protocol: 17
Filter Information:
Filter Run-Time ID: 0
Layer Name: Resource Assignment
Layer Run-Time ID: 36
These events quickly fill the Security event log. Because of the large number of entries in the Security event log, it is difficult to monitor audit failures.
This issue occurs because the Windows Filtering Platform (WFP) incorrectly logs an audit event for a blocked bind to a local port. However, this bind is permitted.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
Prerequisites
To apply this hotfix, your computer must be running one of the following operating systems:
Windows Server 2008
Windows Server 2008 Service Pack 2
Windows Vista Service Pack 1
Windows Vista Service Pack 2
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Vista and Windows Server 2008 file information note
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are
listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Netio.sys
6.0.6001.22423
221,664
30-Apr-2009
12:58
x86
SP1
Bfe.dll
6.0.6001.22423
328,704
30-Apr-2009
12:15
x86
SP1
Fwpkclnt.sys
6.0.6001.22423
99,808
30-Apr-2009
12:58
x86
SP1
Fwpuclnt.dll
6.0.6001.22423
595,456
30-Apr-2009
12:17
x86
SP1
Ikeext.dll
6.0.6001.22423
438,272
30-Apr-2009
12:17
x86
SP1
Wfp.mof
Not Applicable
814
01-Apr-2009
19:02
Not Applicable
SP1
Wfp.tmf
Not Applicable
208,966
30-Apr-2009
10:23
Not Applicable
SP1
Tcpip.sys
6.0.6001.22423
890,352
30-Apr-2009
12:58
x86
SP1
Tcpip.sys
6.0.6002.22126
897,000
30-Apr-2009
12:36
x86
SP2
For all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Service branch
Netio.sys
6.0.6001.22423
344,032
30-Apr-2009
13:19
x64
SP1
Not Applicable
Bfe.dll
6.0.6001.22423
458,240
30-Apr-2009
12:28
x64
SP1
Not Applicable
Fwpkclnt.sys
6.0.6001.22423
166,880
30-Apr-2009
13:19
x64
SP1
Not Applicable
Fwpuclnt.dll
6.0.6001.22423
779,776
30-Apr-2009
12:29
x64
SP1
Not Applicable
Ikeext.dll
6.0.6001.22423
454,656
30-Apr-2009
12:30
x64
SP1
Not Applicable
Wfp.mof
Not Applicable
814
01-Apr-2009
16:13
Not Applicable
SP1
Not Applicable
Wfp.tmf
Not Applicable
207,843
30-Apr-2009
10:40
Not Applicable
SP1
Not Applicable
Tcpip.sys
6.0.6001.22423
1,411,552
30-Apr-2009
13:20
x64
SP1
Not Applicable
Fwpuclnt.dll
6.0.6001.22423
595,456
30-Apr-2009
12:17
x86
SP1
WOW
Wfp.mof
Not Applicable
814
01-Apr-2009
19:02
Not Applicable
SP1
WOW
Tcpip.sys
6.0.6002.22126
1,426,392
30-Apr-2009
12:58
x64
SP2
Not Applicable
For all supported Itanium-based versions of Windows Server 2008
To configure the three profiles in Windows Firewall, follow these steps:
Click Start, click Run, enter wf.msc, and then press ENTER.
In Windows Firewall with Advanced Security, click Windows Firewall Properties, and then configure the profiles in the Windows Firewall with Advanced Security on Local Computer dialog box.
Note These settings may be controlled by corresponding Group Policy settings. Therefore, you cannot change them.
For more information about the "Filtering Platform Connection" audit policy, visit the following Microsoft Web site:
Back to the top
