Maybe you have a firewall that starts after AS runs in the first, good case,
and blocks it thereafter. I suppose that some sort of stateful firewall or
VPN client could also cause this problem, as long as they run after the time
when your initial successful sync occurs.
Paul T.
"Dan" <> wrote in message
news:...
> BlankI have a situation where right after a reboot, when I drop my PDA
> into the
> cradle I get the Windows "de-doop" audible for a USB device being found
> and
> the ActiveSynch "bling" chime letting me know it found it as well. If I
> return later, generally the next day, and drop my PDA into the cradle, I
> get
> the Windows "de-doop" audible, but no Active-Synch "bling" chime and no
> device found in ActiveSync either. The system is left on overnight and
> there
> are no other system issues at this point.
>
> Obviously a reboot cures the problem, but this is not a suitable
> workaround.
>
> To alleviate any hoop jumping, here are the stats:
>
> WindowsXP SP2 w/ latest updates via WSUS on our domain network,
> Latest ActiveSync 4.x
>
> -Dan
>
|