Desktop-Pass-Through internet connection / ActiveSync 4.5 ..

Hello all,

I am experiencing the following problem with ActiveSync 4.5 / Windows Mobile
6.0:

When the device (it's an HTC with WM6) is connected to the Desktop PC
through USB, it cannot connect to the internet using Desktop-Pass-Through
internet connection (= using the internet connection that is provided by the
Desktop PC / Laptop computer).

With ActiveSync 4.1 / Windows Mobile 5.0 this always worked without a problem.

After trying one million things and searching the internet for a LONG, LONG
time, I found a post from Edington Watt from the MS Windows Mobile Platform
(Edington, are there ... ??).

This post communicated to me that exactly this problem already appeared when
ActiveSync was upgraded from ActiveSync 4.1 to ActiveSync 4.2.

Together with his post, Edington Watt offered a registry key fix with the
following content:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services]
"AllowLSP"=dword:00000000

This seems to solve the problem for ActiveSync 4.2 but unfortunately NOT for
ActiveSync 4.5 as I have found out ...

Is there anybody who can help ?? (Edington, are you out there ...??)


THIS IS EDINGTON'S ORIGINAL POST:
(from 07/07/2006 on PDAPhoneHome.com)

To all those who have had problems with connecting to the internet from the
device when upgrading from ActiveSync 4.1 to 4.2:

ActiveSync version 4.2 made a change to how it interacts with the Windows
networking stack to use Layered Service Providers (LSPs) on outgoing
Desktop-Pass-Through connections. This allows for improved compatibility in
environments where connections to the internet must be passed through these
LSPs (ISA Proxy is one such example).

Unfortunately, it appears this change has caused some issues for a small
segment of users who have LSPs that interfere with ActiveSync communication.

There is a registry key fix which will essentially remove this change.

Please download and rename the attached text file with the .txt extension to
the .reg extension. In other words, change the file LSPvalue.txt to
LSPvalue.reg. Afterwards, please double click on the newly renamed .reg file
and click on the "Yes" button.

This should resolve your issues.

Thanks,

Edington
--
Edington Watt
Windows Mobile Platform
Microsoft Corp.

This posting is provided “AS IS” with no warranties, and confers no rights.
Attached Files LSPvalue.txt (262 Bytes, 7370 views)