ActiveSync not picking up Harrier

Forums › Legacy mobile platforms (Windows Mobile, Palm OS, Web OS, Symbian, Meego, Blackberry) › ActiveSync not picking up Harrier

mrdash

11 posts

Geek

#13951 6-Jun-2007 21:51

I'm at a loss as to what to do next.
My Harrier started off well linking to ActiveSync using the cradle. Now my computer treats it as 'USB device not recognised'! The USB port is fine. The cradle is fine (I've even used a spare cradle). Something's up with the Harrier, even though I have no other problems with it. Soft resets do nothing.
Any tips??

Cheers

freitasm

BDFL - Memuneh
79250 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#73716 6-Jun-2007 23:03

Have you changed anything? A new version of ActiveSync, a new firewall or a new USB HUB?

Tips: do not use USB Hub. Check your firewall. Do not upgade to ActiveSync 4.1 because there's nothing there for Windows Mobile 2003.

If you have ActiveSync 4.1 then you might want to uninstall, install the previous version. Failing all that, a hard reset should do it. Drastic...

mrdash

11 posts

Geek

#74049 8-Jun-2007 21:56

Hi there,

Appreciate the advice. I didn't think to add that I had installed a later version of ActiveSync. Still not working yet. Have opened up firewall too. Have backed up all data on to SD card as I lam ooking at doing a hard reset. But before I do, would anyone be able to tell me if doing a hard reset affects my phone settings that I have with Telecom?

Cheers

Grae

10 posts

Wannabe Geek

#74051 8-Jun-2007 22:17

Before you take the drastic hard reset step. have you made sure that ActiveSync is stopped on your Harrier? I have been experiencing a similar non-connection problem with my iMate JAM and found that restarting ActiveSync got the JAM recognised again when reconnected. I do have to do this occasionally though, so there is some underlying issue which I can't figure out.

I have previously installed ActiveSync 4.5, and thought the problem might have originated with that. Uninstall/reinstall didn't help, other than the first time connected when the JAM was recognised. I have now gone back to AS 4.2 but still get the problem and have to use the above work around.