Ok, so I ran into this problem too and found a fix.
I have VMWare installed on my main computer and it creates two virtual network devices, typically named something like "VMware Network Adapter VMnet?", each of which gets its own IP address with a different subnet. So my main (real) NIC gets its IP address from my wireless router (192.168.0.106), and the two virtual NICs have fixed IP (assigned by VMWare) - in my case they are 192.168.232.1 and 192.168.1.1.
ActiveSync via WIFI never worked for me, actually anything that involved tcp/ip connection to this computer, so I installed
vxUtil, performed a LOOKUP on the computer name and got the following:
192.168.1.1
192.168.232.1
192.168.0.106
What this means is that somehow, the tcp/ip stack on the ppc gets all of the ip addresses the computer you had synced with (most recently) uses but not in the correct order. I guess it does not detect which of the addresses is the correct one - should be easy to fix by MS, just compare the address to the one assigned to the ppc! The ppc in my case is assigned 192.168.0.108 by the router. So when attempting to sync, or even ping from vxUtil, the tcp/ip stack uses 192.168.1.1 as the address and fails to connect!
On Windows computers, you can modify the hosts file (different location based on version of Win) to force a fixed IP address for a particular computer name, i.e. no dynamic translation is performed. Say you want a device/computer with the name myspeedypc to translate to 192.168.0.220, you would create an entry line in this hosts file with the name and the IP address seperated with a space or tab:
myspeedypc 192.168.0.220
Unfortunately, this file does not exist in the Windows Mobile world. Instead, its functionality is implemented via the registry. The magic location is "HKEY_LOCAL_MACHINE\Comm\Tcpip\Hosts".
There are two ways to do this, use
Pocket Hosts to very easily add the values, or manually edit the registry using a registry editor such as Resco's, yeah I always do things the hard way :)
- Expand the Hosts key
- Add a new Key under hosts and give it the name of the computer you want to resolve (force a specific IP address)
- Add a new Binary value and give it the name "ipaddr"
- in the same dialog, enter the ip address you want. Note that the IP address must be in HEX - use the Windows Calculator in scientific mode to convert
Example:
you want to enter 192.168.0.200, in hex enter C0 A8 00 DC
I hope this is helpful to those like me that thought "I'll never be able to get this #$%@ working!"
Good luck
Allawy
|
Originally Posted by Seiford
|
I'm having trouble trying to Sync using my WiFi card in my Axim.
I have the Linksys WCF12 and it seems to be working just fine. I can browse the internet and ping things.
My home network uses a Linksys Access point and a Netgear router. My home network is using a 10.0.0.x addressing scheme.
I believe my Dell Axim is somehow caching old IP addresses for my laptop. When I use vxUtil to lookup the IP address of my laptop, it displays three IP address. 192.168.159.1, 192.168.198.1, and 10.0.0.100. the last address is actually the correct one for my laptop. If I try to ping my laptop by name, it uses the first IP address and I get no response. If I ping 10.0.0.100 by IP address, it will ping fine. Of course when trying to sync with ActiveSync, it uses the name and goes to the wrong IP address.
Does anyone know how to purge old IP addresses out of the DNS cache?
I tried deleting the partnership and recreating it, no luck. I upgraded to ActiveSync 3.7, same problem.
|