The older device uses a specific USB function driver and, I think,
essentially serial I/O, like talking to COM1:, to communicate. Firewalls,
virtual private networking software, etc. causes most of the ActiveSync
problems with newer devices (that aren't caused by ActiveSync bugs, at
least).
Paul T.
"Geoff Cox" <> wrote in message
news:...
> On Mon, 22 Dec 2008 10:21:52 -0700, "Paul G. Tobey [eMVP]" <p space
> tobey no spam AT no instrument no spam DOT com> wrote:
>
>>ActiveSync 4.5 comes with some of the same components as ActiveSync 3.x
>>did.
>>That is, when you use AS4.5 with an older Pocket PC device, it can
>>communicate with it using the same method that AS3.8, say, would have.
>>This
>>doesn't work for newer Pocket PC devices, which use the newer
>>communication
>>methods. So, no, it doesn't mean that it's using TCP/IP to do the sync.
>>
>>What's the real question, though? Why would you care if it's using TCP/IP
>>or not?
>
> Paul,
>
> Thanks for the info. The reason I asked was that we have had loads of
> problems getting a newer T-Mobile MDA to synchronize with the PC and I
> wondered whether my older pocketpc, which would connect OK, was not
> using TCP/IP.
>
> The problem was down to the AVG 8 firewall but just yesterday, after
> installing the latest build of the firewall, all is well. I assume
> that the new firewall build detected ActiveSync and opened the
> appropriate ports etc.
>
> Cheers,
>
> Geoff
>
>
>>
>>Paul T.
>>
>>"Geoff Cox" <> wrote in message
>>news:. ..
>>> Hello,
>>>
>>> I have an Ipaq H3870 which has Windows Pocket PC v 3.0.11171 on it and
>>> when I synchronize the Callendar etc it uses ActivSync 4.5.
>>>
>>> Does this mean that it is using TCP/IP to do this?
>>>
>>> Cheers,
>>>
>>> Geoff
>>>
>>
|