My handheld computer will not communicate with my PC and Windows Mobile Device Center does not activate. What can I do?

Windows should automatically install the device driver for your handheld by just by plugging your handheld into the cradle and then turning the handheld ON.   Windows should go through the process of seeing the new USB device, adding drivers, etc., for you.

After that the ‘Mobile devices’ entry in the Device Manager should simply appear and disappear, depending upon whether or not the handheld in the cradle is turned on or not.  Of course, this will only be true if you have the Device Center visible when you do this.

However, there are things that can prevent this from happening, especially in a controlled workstation (limited login privileges).

If the above doesn’t happen, then it is easiest to start with simple things to try and correct the problem, such as logging into your computer as an Administrator.

Next you will want to install Windows Mobile Device Center (WMDC).  There are complete instructions for this in the Bar|Scan User Manual.

If there is still a synchronization problem after installing, then attempt to adjust some of the WMDC settings.   Selecting various connections and trying repeatedly to put the powered up handheld in the cradle for each different connection is the way to try to detect this problem.

Note the image of the above Connection Settings panel. In this case just try each of the available connections one after another, inserting and remove the handheld device for each one.

Another issue is registry locking. Desktops sometimes have their registry locked by your computer administrator.  This can prevent the handheld from being recognized so you will not see the handheld in the device list.  Check the following registry to see if the user utilizing the handheld has the proper permissions to both read and write the registry.

HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionSvcHostWindowsMobile

Lastly, with Windows Mobile 5 (WM5) Microsoft changed the method of communication between handhelds and the desktop PC from a Serial over USB method (PPP-Point to Point Protocol) to a direct network method (RNDIS-Remote NDIS-Remote Network Driver Interface Specification).  In other words, the old method used a serial port to communicate with the handheld, the new method makes the handheld look like another computer on a computer network.  There is a settings panel check box on the handheld that allows reverting back to the old method. It can be found by tapping on the Start Button> Settings>Connections>USB to PC.  You will see a checkbox entitled “Enable advanced network functionality”.

If checked RNDIS is being used.  If unchecked PPP is being used.

If “Enable advanced network functionality” is checked, then the handheld MUST use Bar|Scan’s ‘Custom IP’ address.  This setting also enables use of Bar|Scan’s email feature.

If the checkbox is UNCHECKED, then the handheld will look like an older handheld, one that uses a Serial over USB method.  In this case Windows Mobile Device Center must be configured to use the proper serial port that is being passed through the USB port.  For example, the WMDC ‘Connection Settings’ screen has two serial ports available, only one of which is the correct one for the handheld.

Please note that if you are using a Windows CE handheld rather than a PPC device, then you will not have the ‘USB to PC’ setting available on that device.

There are many other issues that can arise with WMDC.  If these suggestions or other Bar|Scan Knowledge Base Articles do not help, then more detailed descriptions of the symptoms of the problem will be needed.

Common mistakes
The most common mistakes happen at the first attempt at connecting the handheld to the PC.  The key to success is to make sure that both the handheld Windows Mobile Device Center both have the proper settings.  If using PPP (no check mark at “Enable advanced network functionality”) make sure that both the USB ports are enabled and the proper serial port is listed. If using RNDIS (check mark on), make sure Bar|Scan on the handheld is using the Custom IP address and that it is properly filled in.

Finally, when switching these around it helps to reset the connection by simply lifting the handheld out of the cradle then put it back.

Preferences
If you are using email with the handheld computer, use NDIS (checkmark on).  If you are using direct upload from the PC to the handheld and back either will work, but PPP (checkmark off) with the correct serial port configured in WMDC is more convenient.

Communications works for several days or weeks then stops working

If moving the handheld device in and out of the cradle, and your existing installation of Windows Mobile Device Center does not see any change in status then it is not recognizing that the device had been removed from the cradle and continues to report that it was still connected — Or you encounter the opposite reaction, that it would not recognize that the device had been put into the cradle, uninstalling and reinstalling Windows Mobile Device Center may correct the problem.