An RAS client cannot establish a direct cable connection to an RAS server if the connection request does not contain the "CLIENT" keyword and the server is running Windows Embedded CE 6.0 R3

Symptoms

You have a Windows Embedded CE 6.0 R3-based device that is set up to work as a Remote Access Service (RAS) server. However, an RAS client cannot establish a direct cable connection to the server if the connection request does not contain the "CLIENT" keyword.

Resolution

Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (August 2010). 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 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 CE Platform Builder and core operating system software updates:

837392 How to locate core operating system fixes for Microsoft Windows CE Platform Builder productsTo bypass the "CLIENT" keyword check for the Windows CE Telephony API (TAPI) service provider (Unimoderm.dll), you must locate the DCCRequest registry entry in the following path after you install this update:

HKEY_LOCAL_MACHINE\Drivers\Unimodem\Settings subkey

Then, set the registry value of the registry entry to NULL. This behavior lets the RAS client establish a direct cable connection to the server successfully.

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.

Installer files

File name

File size

Date

Time

Wincepb60-100818-kb2362408-armv4i.msi

821,760

18-Aug-2010

18:04

Wincepb60-100818-kb2362408-mipsii.msi

805,888

18-Aug-2010

18:04

Wincepb60-100818-kb2362408-mipsii_fp.msi

805,888

18-Aug-2010

18:04

Wincepb60-100818-kb2362408-mipsiv.msi

809,984

18-Aug-2010

18:04

Wincepb60-100818-kb2362408-mipsiv_fp.msi

809,984

18-Aug-2010

18:04

Wincepb60-100818-kb2362408-sh4.msi

801,280

18-Aug-2010

18:04

Wincepb60-100818-kb2362408-x86.msi

779,264

18-Aug-2010

18:04

Files that are included in this hotfix package

File name

File size

Date

Time

Path

Windows embedded ce 6.0_update_kb2362408.htm

8,030

18-Aug-2010

17:58

100818_kb2362408

Dial.c

89,923

16-Aug-2010

15:53

Private\Winceos\Comm\Tapi\Unimodem

Modem.c

51,240

16-Aug-2010

15:53

Private\Winceos\Comm\Tapi\Unimodem

Unimodem.lib

819,074

16-Aug-2010

15:52

Public\Common\Oak\Lib\Armv4i\Debug

Unimodem.lib

301,404

16-Aug-2010

15:52

Public\Common\Oak\Lib\Armv4i\Retail

Unimodem.lib

777,396

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsii\Debug

Unimodem.lib

295,050

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsii\Retail

Unimodem.lib

777,446

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsii_fp\Debug

Unimodem.lib

295,116

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsii_fp\Retail

Unimodem.lib

784,672

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsiv\Debug

Unimodem.lib

300,968

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsiv\Retail

Unimodem.lib

784,722

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsiv_fp\Debug

Unimodem.lib

301,034

16-Aug-2010

15:52

Public\Common\Oak\Lib\Mipsiv_fp\Retail

Unimodem.lib

705,536

16-Aug-2010

15:53

Public\Common\Oak\Lib\Sh4\Debug

Unimodem.lib

270,850

16-Aug-2010

15:53

Public\Common\Oak\Lib\Sh4\Retail

Unimodem.lib

710,416

16-Aug-2010

15:52

Public\Common\Oak\Lib\X86\Debug

Unimodem.lib

267,990

16-Aug-2010

15:52

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 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?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

×