Article ID: 912240 - Last Review: September 22, 2011 - Revision: 6.0 ActiveSync does not recognize a Windows Mobile 5.0 device attached by USB cable or cradle
NoticeMicrosoft Activesync 4.5 is now available. If your device is running Windows Mobile 5.0 software or later versions and syncs with computers that are running Windows XP, you should upgrade to Activesync 4.5. In some cases, issues in this document will be resolved by upgrading to Activesync 4.5. However, the content of this troubleshooting guide also applies to Activesync 4.5 in many cases. It is recommended that you reference this guide for issues you experience with Activesync 4.5 as well.View the following Microsoft Web site to download Activesync 4.5:http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/activesync-download.mspx (http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/activesync-download.mspx) SYMPTOMSThe Microsoft Windows Mobile device is not recognized when you attach it to your computer using a USB cable or cradle. CAUSEThis problem occurs when a firewall application blocks
ActiveSync application processes. Firewall applications are designed to help
block network traffic and help secure the personal computer from incoming
network connections. Because ActiveSync uses TCP ports for data transfer with
Windows Mobile-based devices, you may have to unblock this traffic in the
firewall application. You must add the ActiveSync application processes to the
firewall application exception list. Sometimes, when you add ActiveSync 4.1 or ActiveSync 4.0 to the firewall application exception list, the firewall application will not let the communication between ActiveSync and the Windows Mobile 5.0 device succeed. This behavior occurs in the following cases and may occur in other cases:
RESOLUTIONTo resolve this problem, contact the firewall vendor to
determine whether one of the following conditions is true:
http://www.microsoft.com/windowsmobile/help/activesync/default.mspx
(http://www.microsoft.com/windowsmobile/help/activesync/default.mspx)
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONWe do not recommend that firewall vendors implement their
firewalls as a firewall-hook driver. Additionally, we do not recommend that
firewall vendors implement their firewalls as a firewall driver for Windows XP
and for later versions of the operating system. The Microsoft Windows 2000 Driver Development Kit (DDK) introduced the concept of a firewall-hook driver. A firewall-hook driver was intended to manage network packets that were sent and received across a firewall in the context of the TCP/IP protocol. A firewall-hook driver did not meet the firewall requirements because the driver ran too high in the network stack. A firewall-hook driver could also interfere with the operation of Internet Connection Sharing or a personal firewall. To provide firewall functionality in Windows XP and in later versions of the operating system, firewall vendors should create a network driver interface specification (NDIS) intermediate miniport driver to manage packets that are sent and received across a firewall. For more information, visit the following Microsoft Developer Network (MSDN) Web sites: Firewall-hook drivers http://msdn2.microsoft.com/en-us/library/aa504964.aspx (http://msdn2.microsoft.com/en-us/library/aa504964.aspx) Windows Firewall http://msdn2.microsoft.com/en-us/library/ms940335.aspx (http://msdn2.microsoft.com/en-us/library/ms940335.aspx) NDIS intermediate drivers http://msdn2.microsoft.com/en-us/library/aa504394.aspx (http://msdn2.microsoft.com/en-us/library/aa504394.aspx) REFERENCESCollapse this image ![]()
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top

