Warning Techie talk!!
When a Windows Mobile device is plugged in, a new network interface is
established on the PC. The PC will have a new network interface with an IP
address of 169.254.2.2. There are also new entries added to the PC routing
table. These new entries will route IP packets destined to 169.254.2.X to
only the device. Note that this address range is reserved. There should be
no networks deployed that uses these IP addresses. The PC and device can now
talk to each other via TCP.
DTPT
There is no routing service on the PC to route IP packets between the two
interfaces. To achieve DTPT a process is started on the PC. This process
routes IP requests from the device to the other NIC's on the PC, much like a
NAT. When an application on the device opens a TCP socket on the device, the
operation is intercepted by a Winsock Layered Service Provider (LSP) on the
device. If DTPT is enabled, it will connect to the running process on the PC
and pass the IP packet to it. This is similar to a VPN tunnel.
After the encapsulated data is received on the PC, it unbundleds the packet
and sends it back into the PC's Winsock layer. The routing table on the PC
will have a default gateway if connected to a network. Since the routing
table is setup that only the subnet of 169.254.2.x will go to the device,
the packet (which isn't on the 169.254.2.x) came from the DTPT LSP on the
device is destined for a different network.
Internet/Work
To put is simply "Internet" doesn't use a proxy; "Work" may need one.
This setting works in tandem with the "Connection Manager" on the device.
When a application on the device (say Pocket IE (PIE)) wants to connect to
www.microsoft.com, it asks Connection Manager, given this URL, does it
connect to the internet or is it a local address on the network. Connection
manager usually just looks for a dot '.' in the name. If there is a dot than
it's on the internet otherwise it's local.
Now the application needs to connect to the other computer. If the Device is
on the internet, then the application is good to go. But let's say that the
device is inside the corporate work environment. The application will have
to send the request to a proxy, since the address is not reachable from
inside the work's LAN.
This is really an over simplification of Connection Manager, but is at the
core of what is happening under the covers.
--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no rights.
"mada" <> wrote in message
news:du36jh$j9s$...
> Hello
>
>> The network is referring to the network connections built into the
>> device - not ActiveSync.
>
> I understand this, however I was wondering what is the (exact) difference
> between "Work" and "The Internet". From some experimentation, I've been
> able to find out that when the network is set to connect to "The Internet"
> it is able to resolve addresses that do not only belong to the 169.254.x.x
> range but, still, I may be wrong on this. In any case, I am really curious
> as to what exactly is the difference between these two settings.
>
>> You can set ActiveSync to allow the Pocket PC to connect to the internet
>> by clicking on File - Connection Settings and make sure that This
>> Computer Connects To has The Internet selected.
>
> Again, I can understand this, from a functional point of view, however I
> would like to be able to understand from a technical point of view, too. I
> am a computer professional for about 15 years and, still, I find it hard
> to understand settings as ambiguous as "Work" and "The Internet" 
>
> Thank you for yout reply, Chris
>
> mada
>
>> --
>> Chris De Herrera
>> http://www.pocketpcfaq.com
>> http://www.tabletpctalk.com
>> http://www.pocketpctalk.com
>> http://www.mobilitytalk.com
>>
>> ActiveSync 4.x Troubleshooting Guide -
>> http://www.pocketpcfaq.com/faqs/acti...shoot-as4x.htm
>>
>> "mada" <> wrote in message
>> news:dtvfcu$n9a$...
>>> Hi all, a question on ActiveSync 4.0 passthru over a usb connection
>>> which, as far as I understand, uses the RNDIS protocol, between a WinXP
>>> machine and a WM5.0 device.
>>>
>>> On the mobile device, the RNDIS Host settings are (manually specified):
>>> IP address: 169.254.2.1
>>> Subnet mask: 255.255.0.0
>>> Default gateway: 169.254.2.2
>>> There is also a (mysterious) setting announcing that "My network card
>>> connects to: The Internet" (someone please oh please explain to me what
>>> these mean).
>>>
>>> On the WinXP machine, there are two network connections:
>>>
>>> 1) "Local Area Network"
>>> Settings (manually specified settings for my home lan):
>>> - IP address: 10.0.0.4
>>> - Subnet mask: 255.255.255.0
>>> - Default gateway: 10.0.0.111 (my DSL router on my home lan)
>>>
>>> 2) "Local Area Network 5"
>>> Settings (this is the DHCP-enabled ActiveSync connection over the RNDIS
>>> protocol):
>>> - IP address: 169.254.2.2
>>> - Subnet mask: 255.255.255.0
>>> - Default gateway: not set
>>>
>>> With these settings, of which I had to manually set nothing related to
>>> the ActiveSync stuff neither on the Win XP machine nor on the WM5.0
>>> device, I can connect to the Internet through Internet Explorer on the
>>> WM5.0 device. I understand that this is achieved thanks to ActiveSync
>>> passthru, which uses the "Local Area Network" interface which can "see"
>>> the DSL router to route packets to and from the "Local Area Network 5"
>>> interface, which can "see" the WM5.0 device.
>>>
>>> My question is simple: On what basis does ActiveSync choose which
>>> interface to use for RNDIS passthru? There are other interfaces on the
>>> Win XP machine, such as a dialup interface that is TCP-IP enabled, also
>>> I could have more than one network card installed, so why does
>>> ActiveSync choose the interface it does?
>>>
>>> Thanks to all for any time you spend reading my post
>>>
>>>
>>
>>
>
>