|
Posted by Juggs Ravalia \(MS\) on August 13, 2006, 12:58 am
Please log in for more thread options
Error 10054 is a socket error. Basically, an existing connection was
forcibly closed by the remote host. This normally results if the peer
application on the remote host is suddenly stopped, the host is rebooted,
the host or remote network interface is disabled, or the remote host uses a
hard close. This error may also result if a connection was broken due to
keep-alive activity detecting a failure while one or more operations are in
progress.
Is it possible for you to grab us a network traffic snapshot when thus
occurs. You can install some network monitoring tool like Ethereal and then
hit Start, cradle device and after you see this WSAECONNRESET (10052 )
error, hit stop and mail us the capture. Seems like one of the required
ports might be blocked or some 3rd party network service blocking
communication. Make sure that ActiveSync via USB is enabled both on device
side as well as desktop side.
Juggs Ravalia [MSFT]
jayrava@online.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
>I am getting an error on my PDA that says:
>
> Cannot start communications with the desktop computer. Winsock services
> could not start due to a critical error (ERROR 10054).
>
> I have restarted the computer and installed the latest version of
> Activesync
> and it still will not sync. Any help would be greatly appreciated. Thanx
| 
XML Sitemap