Passthrough Network between PDA and PC is never created

I've spent the better part of the day attemping to get this to work, and I'm
beginning to think there's something seriously wrong here.

Everywhere I look on blogs, FAQ's, etc., it says that when docking my PDA in
the cradle, a network is established between my PC and the PDA. The PC is
assigned IP address 169.154.2.2, and the PDA is assigned IP address
169.154.2.1.

Opening Network Connections on the PC should reveal a new network connection
called "Windows Mobile-based Device."

Except, I get no such connection at all. Anywhere. With any PDA. I have
used a Windows Mobile 5 device (HP iPaq hx2490b) and a Pocket PC 2003 device
(Compaq iPAQ H3900).

I have used both PDA's on two machines: A Windows XP Professional machine &
a Windows Media Center PC, both with XP SP2. I have cradled both devices and
attached the USB cable to both machines. Both machines are running
ActiveSync 4.5, build 5096. I have completely disabled ALL firewalls on both
machines so that I could discard that as an issue.

I have never, in any combination of devices and computers, ever seen a
network connection created between these devices matching the description
above. The only IP address my PDA's are ever assigned when connected to the
PC is 192.168.55.101, which apparently is the default IP for when DHCP lookup
fails.

Both PC's obtain their IP addresses from the network using DHCP.

The few cryptic remarks people have made seem to suggest I don't have some
kind of driver installed, but of course nobody ever says WHAT should be
installed. I've spent more than 8 hours doing nothing but Google searching
and reading everything I could find, and not one thing has ever actually
dealt with this problem.

Does anyone have ANY idea why I am not getting a network between my PDA's
and my PC's?

Have you tried ipconfig /all from a command prompt? Mine shows 169.254.2.2
for the Windows Mobile Remote Adapter on a WM5 device hooked to Vista/WMDC.
I remember looking that stuff up with older PPC OSs and XP and seeing it
that way. I have never seen any indication of a network connection on any
GUI screen such as Network Connections. I think you do get some indications
in Device Manager in networks, depending on the PC OS, which sync app and
what device OS. I get Windows Mobile Remote Adapter with my setup, but WMDC
works very differently than AS. You can get a copy of vxUtil, or vxIPconfig
free from www.cam.com to see IP setting on the PPC.

Not sure why you care. You can't do much with the connection. You can't
address it in the network, or ping it, from either side. It purely there as
a small, partially featured network between the PPC and the PC. It is not a
full IP implementation. The PC side forms a small internet connection
sharing function with the one device that can be at the end of it, your PPC.

If AS or WMDC is working and syncing your PPC, then the little IP network
is established. If what you are really saying is that you can't get the
device to sync, say so. Trying to troubleshoot this from a network (IP)
point of view is probably not the way to go.

--
Sven
MS MVP Mobile Devices
"Patrick Sears" <Patrick > wrote in message
news:7100A769-2712-4DD4-B36E-...
> I've spent the better part of the day attemping to get this to work, and
> I'm
> beginning to think there's something seriously wrong here.
>
> Everywhere I look on blogs, FAQ's, etc., it says that when docking my PDA
> in
> the cradle, a network is established between my PC and the PDA. The PC is
> assigned IP address 169.154.2.2, and the PDA is assigned IP address
> 169.154.2.1.
>
> Opening Network Connections on the PC should reveal a new network
> connection
> called "Windows Mobile-based Device."
>
> Except, I get no such connection at all. Anywhere. With any PDA. I have
> used a Windows Mobile 5 device (HP iPaq hx2490b) and a Pocket PC 2003
> device
> (Compaq iPAQ H3900).
>
> I have used both PDA's on two machines: A Windows XP Professional machine
> &
> a Windows Media Center PC, both with XP SP2. I have cradled both devices
> and
> attached the USB cable to both machines. Both machines are running
> ActiveSync 4.5, build 5096. I have completely disabled ALL firewalls on
> both
> machines so that I could discard that as an issue.
>
> I have never, in any combination of devices and computers, ever seen a
> network connection created between these devices matching the description
> above. The only IP address my PDA's are ever assigned when connected to
> the
> PC is 192.168.55.101, which apparently is the default IP for when DHCP
> lookup
> fails.
>
> Both PC's obtain their IP addresses from the network using DHCP.
>
> The few cryptic remarks people have made seem to suggest I don't have some
> kind of driver installed, but of course nobody ever says WHAT should be
> installed. I've spent more than 8 hours doing nothing but Google
> searching
> and reading everything I could find, and not one thing has ever actually
> dealt with this problem.
>
> Does anyone have ANY idea why I am not getting a network between my PDA's
> and my PC's?

Hi Sven,

Thanks for the help -

Let's get a few of the more obvious things out of the way.

1. Syncing works just fine. ActiveSync will connect to the device and I
can transfer files, sync settings, etc.
2. vxUtil running on both PDA's displays only the autoconfig IP address
192.168.55.101
3. ipconfig /all displays no IP connection between the devices and my PC's.

Those out of the way:

The reason I care is that if I want to write a desktop application that
communicates with the PDA via that network, I need that IP address. This is
how this problem originated: I am coordinating with another company on an
application. They are able to establish this connection for software
testing; I am not able to, because this network is not appearing on any
computer I connect to. So long as this problem persists, I'm unable to
proceed with software testing.

I've hit one of the very rare fringe cases when this network is actually
necessary. I realize for most people (99.9999% of users) this is an
irrelevant issue. Alas, I'm not one of them

Thing is, because AS is working correctly on both generations of devices and
on both PC's, I suspect that network actually IS being created (particularly
because AS 4.5 on WM5 DOES use the virtual network), it simply isn't being
listed in my IP config info.

Patrick



"Sven" wrote:

> Have you tried ipconfig /all from a command prompt? Mine shows 169.254.2.2
> for the Windows Mobile Remote Adapter on a WM5 device hooked to Vista/WMDC.
> I remember looking that stuff up with older PPC OSs and XP and seeing it
> that way. I have never seen any indication of a network connection on any
> GUI screen such as Network Connections. I think you do get some indications
> in Device Manager in networks, depending on the PC OS, which sync app and
> what device OS. I get Windows Mobile Remote Adapter with my setup, but WMDC
> works very differently than AS. You can get a copy of vxUtil, or vxIPconfig
> free from www.cam.com to see IP setting on the PPC.
>
> Not sure why you care. You can't do much with the connection. You can't
> address it in the network, or ping it, from either side. It purely there as
> a small, partially featured network between the PPC and the PC. It is not a
> full IP implementation. The PC side forms a small internet connection
> sharing function with the one device that can be at the end of it, your PPC.
>
> If AS or WMDC is working and syncing your PPC, then the little IP network
> is established. If what you are really saying is that you can't get the
> device to sync, say so. Trying to troubleshoot this from a network (IP)
> point of view is probably not the way to go.
>
> --
> Sven
> MS MVP Mobile Devices

OK, since you are syncing, then as you seem to agree/admit, the little
network is being created. You are luckier than some...count your blessings


I do understand your issue. I wasn't aware that you could do anything with
that network, That is, nothing I have ever tried to do from the PC has let
me address the PPCs IP address with any IP protocol. Be that as it may, I'm
not a programmer, so I'm over my head here. I can tell you that the PC is
going to be 192.168.55.100, but as you probably know, you can't ping that
unless, 1) the routing tables know where to sends the request, and 2) the
stack around 192.168.55.100 supports SNMP, so it will respond. Don't think
vxUtil will even ping that, though I bet you can ping your PCs normal host
address. As I mentioned it isn't a very full featured implementation. It is
designed to have just enough to sync and form the pass-through connection.

Did you like the CAM utilities? Pretty nice for free, huh?

My suggestion would be to take this question, with the things we already
know here, (you can sync, you do know the IP of the device, can't find the
other end at the PC. etc.) to the developer newsgroup. That would be
Microsoft.public.pocketpc.developer. Guys and Gals over there are much more
likely to be able to help with this sort of issue.

--
Sven
MS MVP Mobile Devices
"Patrick Sears" <> wrote in message
news:6AD4A0C3-1197-46D9-9C85-...
>
> Hi Sven,
>
> Thanks for the help -
>
> Let's get a few of the more obvious things out of the way.
>
> 1. Syncing works just fine. ActiveSync will connect to the device and I
> can transfer files, sync settings, etc.
> 2. vxUtil running on both PDA's displays only the autoconfig IP address
> 192.168.55.101
> 3. ipconfig /all displays no IP connection between the devices and my
> PC's.
>
> Those out of the way:
>
> The reason I care is that if I want to write a desktop application that
> communicates with the PDA via that network, I need that IP address. This
> is
> how this problem originated: I am coordinating with another company on an
> application. They are able to establish this connection for software
> testing; I am not able to, because this network is not appearing on any
> computer I connect to. So long as this problem persists, I'm unable to
> proceed with software testing.
>
> I've hit one of the very rare fringe cases when this network is actually
> necessary. I realize for most people (99.9999% of users) this is an
> irrelevant issue. Alas, I'm not one of them
>
> Thing is, because AS is working correctly on both generations of devices
> and
> on both PC's, I suspect that network actually IS being created
> (particularly
> because AS 4.5 on WM5 DOES use the virtual network), it simply isn't being
> listed in my IP config info.
>
> Patrick
>
>
>
> "Sven" wrote:
>
>> Have you tried ipconfig /all from a command prompt? Mine shows
>> 169.254.2.2
>> for the Windows Mobile Remote Adapter on a WM5 device hooked to
>> Vista/WMDC.
>> I remember looking that stuff up with older PPC OSs and XP and seeing it
>> that way. I have never seen any indication of a network connection on any
>> GUI screen such as Network Connections. I think you do get some
>> indications
>> in Device Manager in networks, depending on the PC OS, which sync app and
>> what device OS. I get Windows Mobile Remote Adapter with my setup, but
>> WMDC
>> works very differently than AS. You can get a copy of vxUtil, or
>> vxIPconfig
>> free from www.cam.com to see IP setting on the PPC.
>>
>> Not sure why you care. You can't do much with the connection. You can't
>> address it in the network, or ping it, from either side. It purely there
>> as
>> a small, partially featured network between the PPC and the PC. It is not
>> a
>> full IP implementation. The PC side forms a small internet connection
>> sharing function with the one device that can be at the end of it, your
>> PPC.
>>
>> If AS or WMDC is working and syncing your PPC, then the little IP
>> network
>> is established. If what you are really saying is that you can't get the
>> device to sync, say so. Trying to troubleshoot this from a network (IP)
>> point of view is probably not the way to go.
>>
>> --
>> Sven
>> MS MVP Mobile Devices

I have exactly the same problem - I am using a HP iPaq 6915 Mobile Messenger
Series and whilst the syn via USB works fine the Sync with an Exchange server
does not work when docked via USB but works fine when not docked (because it
uses GPRS).

My understanding is as follows:
The Device (WM5) has several connections available to it to communicate over
and it has a precedence about which one to use. It will always use USB (if
available), then Wi-fi then GPRS as a last resort but it will attempt to do
all communication through the highest level adapter present.

So for example. If the device is connected via USB, the sync with Microsoft
Outlook (2003 SP2 on XP SP2) works fine but the part which attempts to sync
with our Exchange Server fails with error code "The server could not be
reached. This can be caused by Temporary Network Conditions. Support Code:
80072efd".
However I believe that the Network Conditions problem is not a temporary one
whilst the PC is docked. My understanding is that the device should be able
to make use of the PCs network connection whilst connected to the PC via USB
(almost like a router).

Another example is that the bundled TomTom application states that to
download the free map (and any subsequent maps) you should connect your
device to your PC via USB and then click on a link. The link is an internet
site but the web broswer on the device will not access any internet sites
whilst it is connected to USB. As soon as I undock the device I can of course
access the sites perfectly well but of course may be downloading large files
over GPRS which can be a little tedious and expensive.

I too have looked for troubleshooting information and can find very little
information. The one bit that looked relevant said to check the network
adapter created on the PC and make sure that "bridging" (or similar) was
enabled bit I too do not have this adapter.

Can anyone suggest how to get this specific passthrough feature working?

Cheers

Mike

"Sven" wrote:

> OK, since you are syncing, then as you seem to agree/admit, the little
> network is being created. You are luckier than some...count your blessings
>
>
> I do understand your issue. I wasn't aware that you could do anything with
> that network, That is, nothing I have ever tried to do from the PC has let
> me address the PPCs IP address with any IP protocol. Be that as it may, I'm
> not a programmer, so I'm over my head here. I can tell you that the PC is
> going to be 192.168.55.100, but as you probably know, you can't ping that
> unless, 1) the routing tables know where to sends the request, and 2) the
> stack around 192.168.55.100 supports SNMP, so it will respond. Don't think
> vxUtil will even ping that, though I bet you can ping your PCs normal host
> address. As I mentioned it isn't a very full featured implementation. It is
> designed to have just enough to sync and form the pass-through connection.
>
> Did you like the CAM utilities? Pretty nice for free, huh?
>
> My suggestion would be to take this question, with the things we already
> know here, (you can sync, you do know the IP of the device, can't find the
> other end at the PC. etc.) to the developer newsgroup. That would be
> Microsoft.public.pocketpc.developer. Guys and Gals over there are much more
> likely to be able to help with this sort of issue.
>
> --
> Sven
> MS MVP Mobile Devices
> "Patrick Sears" <> wrote in message
> news:6AD4A0C3-1197-46D9-9C85-...
> >
> > Hi Sven,
> >
> > Thanks for the help -
> >
> > Let's get a few of the more obvious things out of the way.
> >
> > 1. Syncing works just fine. ActiveSync will connect to the device and I
> > can transfer files, sync settings, etc.
> > 2. vxUtil running on both PDA's displays only the autoconfig IP address
> > 192.168.55.101
> > 3. ipconfig /all displays no IP connection between the devices and my
> > PC's.
> >
> > Those out of the way:
> >
> > The reason I care is that if I want to write a desktop application that
> > communicates with the PDA via that network, I need that IP address. This
> > is
> > how this problem originated: I am coordinating with another company on an
> > application. They are able to establish this connection for software
> > testing; I am not able to, because this network is not appearing on any
> > computer I connect to. So long as this problem persists, I'm unable to
> > proceed with software testing.
> >
> > I've hit one of the very rare fringe cases when this network is actually
> > necessary. I realize for most people (99.9999% of users) this is an
> > irrelevant issue. Alas, I'm not one of them
> >
> > Thing is, because AS is working correctly on both generations of devices
> > and
> > on both PC's, I suspect that network actually IS being created
> > (particularly
> > because AS 4.5 on WM5 DOES use the virtual network), it simply isn't being
> > listed in my IP config info.
> >
> > Patrick
> >
> >
> >
> > "Sven" wrote:
> >
> >> Have you tried ipconfig /all from a command prompt? Mine shows
> >> 169.254.2.2
> >> for the Windows Mobile Remote Adapter on a WM5 device hooked to
> >> Vista/WMDC.
> >> I remember looking that stuff up with older PPC OSs and XP and seeing it
> >> that way. I have never seen any indication of a network connection on any
> >> GUI screen such as Network Connections. I think you do get some
> >> indications
> >> in Device Manager in networks, depending on the PC OS, which sync app and
> >> what device OS. I get Windows Mobile Remote Adapter with my setup, but
> >> WMDC
> >> works very differently than AS. You can get a copy of vxUtil, or
> >> vxIPconfig
> >> free from www.cam.com to see IP setting on the PPC.
> >>
> >> Not sure why you care. You can't do much with the connection. You can't
> >> address it in the network, or ping it, from either side. It purely there
> >> as
> >> a small, partially featured network between the PPC and the PC. It is not
> >> a
> >> full IP implementation. The PC side forms a small internet connection
> >> sharing function with the one device that can be at the end of it, your
> >> PPC.
> >>
> >> If AS or WMDC is working and syncing your PPC, then the little IP
> >> network
> >> is established. If what you are really saying is that you can't get the
> >> device to sync, say so. Trying to troubleshoot this from a network (IP)
> >> point of view is probably not the way to go.
> >>
> >> --
> >> Sven
> >> MS MVP Mobile Devices
>