Activesync 4.1 and the xv6700

[torcellt]

I just purchased a xv6700 and I cannot get it to sync with my sony winxp laptop, I have tried everything I can think of: reinstalling AS, softreset, hardreset, reinstalling USB drivers, removed all firewalls, and even replacing the handset itself. I have never established partnership as it has never been able to sync. I put the phone in the cradle, and i get the prompt that new hardware is being installed and ready to use. A networking icon pops up connects and then AS starts spinning and says it is connecting, it will not progress any further. I hooked up a friends dell pocket pc to make sure I didnt have any hidden firewalls, and it synced immediatly.

Does anyone have any ideas???????????????????????

[Janak Parekh]

What operating system does your friend's Dell use? If it's WM2003 or WM2003SE, it uses a different sync mechanism, and a firewall can still be the cause of your problem.

Do you have any "Internet Security" packages on your computer? Those often have firewalls, and tend to be the primary cause of your symptom.

--janak

[torcellt]

Janak,
Thanks for your reply, I am not sure as to what system the Dell operated on, but as far as internet security... I had Symantec Corporate edition installed, but i unistalled it in the hopes of getting the phone to sync. The only other thing is the windows firewall, which i also disabled, hoping that it would work.

[fab]

I am still getting used to the activesync idiosyncrasies ;-)

I was having similar problems - activesync connecting but nothing happening, my laptop not recognising the device or my user name.

I have solved the problem (I hope) by turning on my 6700 before I put it on the cradle. If I put it on while it's "asleep" I get all sorts of errors.

HTH

[torcellt]

that didnt work either, but i appriciate the help.

[Darius Wey]

I understand you've already exhausted all firewall possibilities, but there's still a chance that your network settings need a bit of a tweak in order to get the device to sync.

Check out this guide for more information: http://www.microsoft.com/windowsmobile/help/activesync/default.mspx

[torcellt]

I read that as well, but I am already using AS 4.1... I tried diabling all other connections to see if that would do it, but no help there either.

[revangel]

i just had the same issue this morning with my xv6700. i was able to sync with my PC yesterday and this morning i had the endless looping green AS logo.

here's my fix:
> remove the "pairing" relationship between your PC and the xv6700.
* do this by going to File > Delete Mobile Device
> 'OK' through the prompts to confirm deletion.
> re-associate or create a new relationship from scratch.
* make sure to attach the cradle to your PC's USB port, green LED on the left hand side should come up
* turn ON your phone and attach to the cradle
* your PC will now prompt you for add'l info to complete the install/sync

!!Keep in mind that if you have a docking station/port replicator that you *must* do a complete shutdown of your PC first prior to attaching the cradle. This will eliminate some of the quirks between the replicator and your PC/laptop (in case you are using one).!!

Hope this helps. =)

[revangel]

one other thing.

i do not believe this to be a 'firewall' issue for your mobile device should be viewed by your PC as an external/peripheral device and not necessarily a 'networking' device that might attempt to compromise your system.

my understanding is that the device, while cradled and attached via the USB port does not have an IP address hence is technically not a LAYER3 device that is capable of routing/passing traffic. sonofagun-i almost understood what i just wrote down. ME<---geek :roll:

just my 2c.

[Darius Wey]

my understanding is that the device, while cradled and attached via the USB port does not have an IP address...

You would have guessed correctly before the introduction of Windows Mobile 5.0 and ActiveSync 4.0. The two together now utilise the Windows TCP/IP stack, so a cradled device will appear as a network interface and have a valid IP address, despite it being attached via USB.

[Darius Wey]

I read that as well, but I am already using AS 4.1... I tried diabling all other connections to see if that would do it, but no help there either.

Have you been able to synchronise with another computer? Perhaps this way, we can identify if it's a problem to do with your computer, or your device.

[Janak Parekh]

my understanding is that the device, while cradled and attached via the USB port does not have an IP address hence is technically not a LAYER3 device that is capable of routing/passing traffic. sonofagun-i almost understood what i just wrote down. ME<---geek :roll:
Let me give a more technical explanation of what Darius said: WM5 uses a RNDIS-over-USB driver (http://www.microsoft.com/whdc/device/network/NDIS/rmNDIS.mspx) that appears as a legitimate Windows network adapter when the device is cradled/present. The OS/ActiveSync then assigns a 169.254.* address to the WM5 device (and one for itself), and uses TCP connections between those two addresses using the standard IP stack. So it is indeed layer 2/3 with WM5 -- and any firewall that blocks 169.254.* traffic will prevent AS4 from working correctly.

You are correct that with previous versions of Windows Mobile, the IP connectivity was implemented at layer 7 or thereabouts; it was a user-mode software IP stack and therefore not subject to a firewall. I'm not quite sure why they decided to use RNDIS for WM5, but I'm guessing it was the easiest way to redesign the Pocket PC's connection architecture (the previous one only supported serial speeds).

And welcome to the geekhood. Knowing what the heck the OSI model means, as opposed to just memorizing what the layers are, is a truly scary thing. ;)

--janak

[monica_lynn67]

I was having the same trouble. It turns out on my end, I had disabled DHCP Client in my services pannel. Since I operate with static IPs at home, I had turned it off.