Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

Consider the following scenario:

  • You are running a Microsoft Windows Embedded CE 6.0 R3-based image on a device.

  • You try to establish a Layer Two Tunneling Protocol (L2TP) over Internet Protocol security (IPsec) connection from the device.

  • The device connects to a private network. The private network connects to a public network through a Network Address Translation (NAT) gateway. The L2TP server is located in a public network.

In this scenario, you cannot establish the L2TP over IPsec connection. 

Cause

This issue occurs because some Internal Key Exchange (IKE) packages are lost when they are sent through a port on the device. Therefore, the IPsec connection fails in the NAT gateway.

Resolution

Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (January, 2011). You can confirm this by scrolling to the "File information" section of this article. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is:

Product version-yymmdd-kbnnnnnn-processor typeFor example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows Embedded 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 obtaining Windows Embedded CE Platform Builder and core operating system software updates:

837392 How to locate core operating system fixes for Microsoft Windows Embedded CE Platform Builder productsNote This Windows Embedded CE 6.0 Monthly Update is also available for download from the following Microsoft Download Center website:

Windows Embedded CE 6.0 Updates

Prerequisites

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

Restart requirement

After you apply this 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 other 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.

File name

File size

Date

Time

Wincepb60-110112-kb2484550-x86.msi

1,143,296

12-Jan- 2011

22:13

Wincepb60-110112-kb2484550-armv4i.msi

1,212,928

12-Jan-2011

22:13

Wincepb60- 110112-kb2484550-mipsii.msi

1,190,912

12-Jan-2011

22:13

Wincepb60-110112-kb2484550- mipsii_fp.msi

1,190,912

12-Jan-2011

22:13

Wincepb60-110112-kb2484550-mipsiv.msi

1,191,424

12-Jan- 2011

22:13

Wincepb60-110112-kb2484550-mipsiv_fp.msi

1,191,424

12-Jan- 2011

22:13

Wincepb60-110112-kb2484550-sh4.msi

1,185,792

12-Jan-2011

22:13

File name

File size

Date

Time

Path

Ipsec.lib

862,482

05-Jan- 2011

15:46

Public\Common\Oak\Lib\Armv4i\Debug

Ipsec.lib

529,254

05-Jan-2011

15:46

Public \Common\Oak\Lib\Armv4i\Retail

Ipsec.lib

819,242

05-Jan-2011

15:46

Public\Common\Oak\Lib\Mipsii \Debug

Ipsec.lib

508,038

05-Jan-2011

15:46

Public\Common\Oak\Lib\Mipsii \Retail

Ipsec.lib

819,496

05-Jan-2011

15:46

Public\Common\Oak\Lib\Mipsii_fp \Debug

Ipsec.lib

508,234

05-Jan-2011

15:46

Public\Common\Oak\Lib\Mipsii_fp \Retail

Ipsec.lib

825,874

05-Jan-2011

15:47

Public\Common\Oak\Lib\Mipsiv \Debug

Ipsec.lib

511,924

05-Jan-2011

15:46

Public\Common\Oak\Lib\Mipsiv \Retail

Ipsec.lib

826,128

05-Jan-2011

15:47

Public\Common\Oak\Lib\Mipsiv_fp \Debug

Ipsec.lib

512,126

05-Jan-2011

15:47

Public\Common\Oak\Lib\Mipsiv_fp \Retail

Ipsec.lib

715,252

05-Jan-2011

15:47

Public\Common\Oak\Lib \Sh4\Debug

Ipsec.lib

476,138

05-Jan-2011

15:47

Public\Common\Oak\Lib \Sh4\Retail

Ipsec.lib

697,738

05-Jan-2011

15:46

Public\Common\Oak\Lib \X86\Debug

Ipsec.lib

479,570

05-Jan-2011

15:46

Public\Common\Oak\Lib\X86\Retail

Status

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

More Information

For more information about 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, click the following article number to view the article in the Microsoft Knowledge Base:

2467615 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

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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×