One of the symptoms of this problem is an error 0x80072f78 trying to browse a site from the device, or just getting an ugly connectivity settings error.
If you’ve tried to solve this problem before looking for help on the web, probably you’ve found kind of a “black magic” solution: a registry tweak adding a new DWORD value named “AllowLSP”. But what is all of this about??
Let’s start from the beginning: LSP = Layered Service Provider. It’s a feature of Microsoft Winsock 2 Service Provider Interface (SPI). It makes possible to modify transport services, i.e. implementing a firewall. You can find more info here.
DTPT (Desktop Pass Through) allows the device to talk with the desktop network (or the internet if the desktop has internet access) while ActiveSync is running. It’s implemented as a socket level proxy technology, including a server side (ActiveSync or WMDC) and a client side implemented as a LSP (the DTPT LSP).
ActiveSync, from its version 4.2 and above, has changed the way it interacts with the Microsoft Windows networking stack to support Layered Service Providers (LSP) on outgoing Desktop-Pass-Through connections. In many corporate environments this provides improved compatibility and policy compliance.
Unfortunately, there are several cases where you can find LSPs interfering with ActiveSync communication. So, we need to enable ActiveSync on the desktop to function together with LSP applications.
It requires to edit (or create) a DWORD registry key called “AllowLSP” on the desktop, in the following registry path:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services]
The possible decimal values are:
0: Bypass LSPs for incoming and outgoing connections.
1: Bypass LSPs for incoming connection and use LSPs for outgoing connection.
2: Use LSPs for incoming and bypass LPSs outgoing connections.
3: Use LSPs for incoming and outgoing connections.
The value which used to work in this case is “0”, because it bypasses LSPs as previous ActiveSync versions use to do. But if your computer environment relies on LSPs (a very common scenario in corporate networks), probably you’ll need to identify which LSP is causing the conflict and then decide whether you can uninstall the related software package. It’s doable running this command from a command prompt:
netsh winsock show catalog
As result you’ll find a list of each LSP installed on your machine. For sure this information is really cryptic, but it can be helpful in order to determine what you need to remove.
In some scenarios you can use the value of “2”. It allows LSPs for incoming connections but bypasses them for outgoing connections.
It’s highly probable that you need to reset your desktop (or restart activesync killing the “wcescomm.exe” process and launching ActiveSync manually) to reflect the changes.
Additionally, if you have a firewall running, please add the following processes to the application exception list:
If this post cannot help you, probably you can find an answer in this link.Hope you finally get your device connected to the internet thru ActiveSync!