|
Unfortunately I am unable to give you an answer, but I think I can give you a piece of the puzzle. This most likely is causing your problem, but I do not know how to fix it:
When you connect your Axim to Windows, your are actually creating a network connection. While your Axim is connected bring open a DOS box run the following without the quotes "ipconfig /all". You should notice a "Ethernet adapter Local Area Connection" with a description of "Winows Mobile-based Device" (or something to that degree). Also notice that the connection is receiving its IP address from a DHCP server. It is my understanding that ActiveSync is fooling XP into thinking that ActiveSync is a DHCP server. You should note that the IP of the Axim is not the same as the IP address of the "connection"
While the "connection" is obtaing its IP address from ActiveSync, XP is stopping packets from being sent and received from the primary NIC. After the connection has received its IP address, XP allows packets to be sent and received from your main NIC.
If you eyes are rolling in the back of your head or are now dead of complete boardom upon reading this post, here is an "English" version.
ActiveSync is buggy and you are hosed for now....
__________________
The two most common elements in the universe are hydrogen and stupidity. But not in that order.
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
-- Brian Pickrell (Date unknown)
Casio Cassiopeia A11 --> Palm III --> Dell Axim X50v + Cingular 8125 -> Dell Axim X50v + Treo 750
|