Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Performance issues when an IKE port receives lots of packets on a Windows Embedded CE 6.0 R3-based device if an L2TP over IPSec connection is established


Symptoms

Consider the following scenario:
  • You establish an L2TP over IPSec connection. The connection is from a Windows Embedded CE 6.0 R3-based device to a server.
  • The Internet Key Exchange (IKE) port of the device receives lots of packets per second. For example, the IKE port receives hundreds of packets per second.
In this scenario, the CPU usage of the device increases, and the device experiences performance issues.

↑ Back to the top


Cause

This issue occurs because the IPSec module is resumed when each packet arrives. Therefore, the device's CPU usage increases, and the performance issues occurs. 

↑ Back to the top


Resolution

Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (November 2010). You can confirm this by scrolling to the "File information" section. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is as follows:
Product version-yymmdd-kbnnnnnn-processor type
For example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows CE 5.0 Platform Builder fix that is documented in KB article 917590 and that is contained in the May 2006 monthly update. To resolve this problem immediately, click the following article number for information about how to obtain Windows CE Platform Builder and core operating system software updates:
837392 How to locate core operating system fixes for Microsoft Windows CE Platform Builder products

Prerequisites

This software update is supported only if all previously issued software updates for this product have also been applied.

Restart requirement

After you install this software update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
  • On the Build menu, click Clean Solution, and then click Build Solution.
  • On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any updates. 

File information

The English version of this software update package 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.
Installer files
File nameFile sizeDateTime
Wincepb60-101130-kb2467615-armv4i.msi1,212,41630-Nov-201022:51
Wincepb60-101130-kb2467615-mipsii.msi1,190,40030-Nov-201022:51
Wincepb60-101130-kb2467615-mipsii_fp.msi1,190,91230-Nov-201022:51
Wincepb60-101130-kb2467615-mipsiv.msi1,190,91230-Nov-201022:51
Wincepb60-101130-kb2467615-mipsiv_fp.msi1,190,91230-Nov-201022:51
Wincepb60-101130-kb2467615-sh4.msi1,185,79230-Nov-201022:51
Wincepb60-101130-kb2467615-x86.msi1,143,29630-Nov-201022:51
Files that are included in this hotfix package
File nameFile sizeDateTimePath
Windows embedded ce 6.0_update_kb2467615.htm7,63730-Nov-201022:16101130_kb2467615
Ipsec.lib861,15623-Nov-201016:53Public\Common\Oak\Lib\Armv4i\Debug
Ipsec.lib529,15223-Nov-201016:53Public\Common\Oak\Lib\Armv4i\Retail
Ipsec.lib818,14623-Nov-201016:53Public\Common\Oak\Lib\Mipsii\Debug
Ipsec.lib507,86023-Nov-201016:53Public\Common\Oak\Lib\Mipsii\Retail
Ipsec.lib818,40023-Nov-201016:54Public\Common\Oak\Lib\Mipsii_fp\Debug
Ipsec.lib508,05623-Nov-201016:53Public\Common\Oak\Lib\Mipsii_fp\Retail
Ipsec.lib824,75423-Nov-201016:54Public\Common\Oak\Lib\Mipsiv\Debug
Ipsec.lib511,75823-Nov-201016:54Public\Common\Oak\Lib\Mipsiv\Retail
Ipsec.lib825,00823-Nov-201016:54Public\Common\Oak\Lib\Mipsiv_fp\Debug
Ipsec.lib511,96023-Nov-201016:54Public\Common\Oak\Lib\Mipsiv_fp\Retail
Ipsec.lib714,20023-Nov-201016:54Public\Common\Oak\Lib\Sh4\Debug
Ipsec.lib476,09423-Nov-201016:54Public\Common\Oak\Lib\Sh4\Retail
Ipsec.lib696,73023-Nov-201016:53Public\Common\Oak\Lib\X86\Debug
Ipsec.lib479,54623-Nov-201016:53Public\Common\Oak\Lib\X86\Retail

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2467615
Revision : 1
Created on : 1/7/2017
Published on : 12/31/2010
Exists online : False
Views : 173