I have read most of what the problems are, which I had my own share. I am using windows XP SP2 with all current updates, and had problems with activesync 4.0 that came with Axim x51v (ROM A06), through its USB cradle. My ActiveSync would respond saying "connecting", but would not connect. It seemed like a firewall problem that was blocking TCP, but disabling the firewall would not help. And I learned a few things on the way. There may be other applications that actually capture some of these ports during the system boot (or user login), and activesync would not be able to connect to your PDA. The problems are usually simple, but figuring out may be quite frustrating. Mine was (in my case the problem was that my Secure FTP SSL server was occupying the TCP Port 990 during the boot, thus not allowing activesync to use the port). To get to that point, I needed to find out what ports ActiveSync applications were using.
I had it work with my Dell Inspiron 6000 (window XP) with no problems off the box. It sync'ed, but I had problems syncing with my office computer. I went into details as to what services are running and cross-check between the two computers. I also figured out the TCP ports these applications use, and allowed access through the firewall. I finally got my office computer to perfectly sync and I think this may save some frustration for some of you folks:
First, if the drivers are installed correctly, you should see the axim under your network adapters in device manager as "Windows mobile-based device".
Device Manager
This is the prerequisite for all further steps. Your device communicates through TCP/IP and should show as a network device if you are running Windows Mobile 5.0 - at least in the case of Axim x51v. If you have WM5, do not bother trying any version of ActiveSync prior to the version 4.0. It will not work.
Here is the story and solution with my office computer:
- If you see your axim under "network adapter" as "Windows Mobile-based Device #x", than you are on the right track.
- Most people will have a firewall problem. Since the device uses TCP to communicate to your desktop host computer, you have to have the following ports open (note that the activesync 4.0 and 4.1 installations already add these "exceptions" to your windows xp firewall during the installation)
TCP port 990: This is also implicit FTP port, and if you are running an FTP server with implicit FTP, it is likely that this port will be captured by the system before activesync can use it, and you will not be able to sync. This was my problem. I stopped the FTP server, and woala! I got in.
TCP port 999:
TCP port 5678.
You can add these exceptions to your firewall software for the following IP addresses (In other words, these IP addresses should be allowed to access the above listed ports):
169.254.2.2 (or alternatively put 169.254.2.0/255.255.255.0 in your firewall exceptions)
When you go to your firewall application (here I will cite the window XP built-in one that comes with Service pack 2) you should see the following applications in your exceptions list:
Exceptions figure
ActiveSync Application (WCESMgr.exe): uses TCP ports 999 and 5678
ActiveSync Connection Manager (wcescomm.exe)
ActiveSync RAPI Manager (rapimgr.exe): uses TCP ports 990 and 5721
ActiveSync Service: Uses TCP port 26675
All these ports should be open. A better way to allow these applications use the ports they need is to disable firewall for these applications.
One way to see if these ports are active is to use the "netstat" command in the command window. You should see that all the ports I listed above should have an "ESTABLISHED" state. Here is how it looks in the command window:
Netstat output
If you have the hardware configured correctly and have the TCP ports open, you should already be able to sync, or at least be very close to do so.
Also try to download and install ActiveSync 4.1, which should help. I am not familiar with Windows 2000 problems, but they should have similarities to these above. I hope this helps.