Re: ActiveSync 4.1 Still does not work... (Solved for me)

They test like crazy, but there are a huge number of combinations with all
of the versions of everything which are floating around and MS typically
doesn't test as extensively with older devices, older OSes, etc. Think
about all of the pieces that MS does not control that are involved in AS:
USB hardware (computer vendor), USB drivers (hub vendor, computer vendor,
MS), TCP/IP stack (MS, firewall vendor, VPN vendor, etc., etc.), mobile
device USB (mobile device vendor, MS).

The MVPs have been beating on MS to seed us with newer devices so that they
can get a more broad test of things. This is troublesome, of course,
because it's the device vendor that builds the operating system for his
device, *not* Microsoft. Some of this is happening and MS had a *lot* of
beta testers for AS4.1 from this program. In theory, the quality of the
device itself is up to the OEM, but of course, you see "Microsoft" all over
the OS, so you blame them, not the device vendor (and the device vendor does
the same, when you call support). MS knows that the AS experience is
poor-to-mediocre for many people and they are working on that.

I'm an end-customer too and I know what you mean!

Paul T.

"guillaume riviere" <riviereg@xxxxxxxxx> wrote in message
news:1136522430.148155.208580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi, I got the same kind problem with my new o2 atom,
> I solve it with the recomendations on microsoft web site:
>
> (The default installation do not configure the network connection
> to this device, that mean no one try/test it before they sell it)
>
> http://www.microsoft.com/windowsmobile/help/activesync/default.mspx
>
> I really got a lot of problem with windows 5.0, did they
> test this software ? do you need to be an IT engineer to use this ?
>
> I mean, when i pay a device this price, it should have been
> tested/patched
> and well design for end user customer.
>
> Gui.
>
> Paul G. Tobey [eMVP] wrote:
>> OK, here are a few comments.
>>
>> Your configuration matches mine on both computers with which I
>> synchronize
>> *exactly*. They both use static IPs and neither is part of a domain.
>> This
>> suggests to me that some component of the system, other than the OS and
>> ActiveSync, is responsible for the problem. If it were me, I'd do a
>> check
>> with the computer manufacturer and, of course, Microsoft Update, to see
>> if
>> there are any driver updates, especially for USB. AS4.1 installs some
>> USB
>> updates because of problems found with 4.0 in that area. Another thing
>> that
>> you might try is removing the USB drivers for your USB root hub,
>> installing
>> ActiveSync, then allowing Windows to find it again.
>>
>> I guess that, to be more specific, here are the steps that I'd look at.
>> You've probably done some of them, but it might be worth one more attempt
>> before you go through the hassle of dumping the phone:
>>
>> 1. Inspect %tmp%\activesync.log. This indicates what the installer did
>> when
>> you installed ActiveSync. It's possible that there was some sort of a
>> problem which was identified here, but not elsewhere.
>>
>> 2. Plug the device in and delete all references to it from the Device
>> Manager. We want to, as much as possible, make sure that Windows is
>> seeing
>> the device as new the next time we install it. Remove the device. Also
>> delete any existing partnerships that might be lingering around in AS.
>> Since you completely killed the old version, I'd be surprised if there
>> were
>> any, but you might search the registry for the device name (from the old
>> partnership, if you remember that), and make sure that there's nothing
>> still
>> there. You might also, if you want to be very aggressive, uninstall
>> ActiveSync and delete all folders that are AS-related from the hard disk.
>>
>> 3. We should have a 'clean' surface for the device to arrive now.
>> Connect
>> it. You should see the following in roughly this order: a) found new
>> hardware bubble, b) various driver install bubbles and RNDIS bubble, c)
>> icon
>> in the system tray for the new 'network adapter' with the 'acquiring
>> network
>> address' appearance and tip. If I understand you, this is where things
>> fail
>> right now (although the address appears to be getting assigned). If they
>> fail there again, I'm thinking that there is a handshake problem between
>> AS
>> on the device and the desktop, which comes down to ports not being
>> accessible. Perhaps some vestige of an old firewall or even the Windows
>> firewall blocking access to some ports.
>>
>> Another thing that might go wrong here is if you are using any Virtual
>> Private Networking. I don't do this, but I've heard that some such
>> clients
>> route everything to the VPN, which would be a problem, since AS wants to
>> get
>> a DHCP address from the device (not from the VPN network), and AS sends
>> various types of network messages to various ports during the
>> establishment
>> of a connection. Both UDP and TCP messages are sent, so you've got to be
>> sure that both datagrams and streams work.
>>
>> You might also check the settings for the types of connections that the
>> device is going to allow on the device AS application itself (Menu |
>> Connections). Obviously, you want USB enabled.
>>
>> If everything seems to be set correctly, but no connection is
>> established,
>> MS recommends grabbing some network traces. It's pretty hard to give a
>> step-by-step on this, but you want to see any and all UDP and TCP packets
>> sent on the RNDIS interface. If you don't see any UDP, this might
>> indicate
>> that something is redirecting them to another interface, so you might
>> check
>> and see if UDP packets from the desktop machine *are* going out another
>> interface. You might also check the %tmp%\wce*.log files to see if any
>> of
>> them show a process starting but not completing. The one that looks the
>> most promising to me is wcescomm.log. It doesn't get many entries, but
>> it
>> should show the RNDIS adapter appearing.
>>
>> 4. Green ActiveSync icon should start spinning. You're on to the next
>> problem ;-)
>>
>> Paul T.
>>
>> "ckelsoe" <charles@xxxxxxxxxx> wrote in message
>> news:%2386zkbaEGHA.2012@xxxxxxxxxxxxxxxxxxxxxxx
>> > alrightly, you ask - here is what I have done and still do not have as
>> > working...
>> >
>> > Environment:
>> >
>> > Windows XP with SP 2 and all patches / updates
>> >
>> > Connected to network, not connected to domain
>> >
>> > Static IP Assigned (changed to dynamic as part of diagnostics)
>> >
>> > I-MATE K-JAM Phone with WM 5.0
>> >
>> >
>> >
>> > Symptom: ActiveSync shows it is connecting but never connects.
>> >
>> >
>> >
>> > Observations:
>> >
>> > 1.. Setting the Tray notification on the Windows Mobile based Device
>> > shows a connection.
>> > 2.. Running Ethereal shows that the port 5679 is unreachable.
>> > 3.. The device shows the following message after a time: "Unable to
>> > obtain a server assigned IP Address". Changing to a static ip on the
>> > device makes no difference.
>> > 4.. User is administrator
>> > 5.. Tried 8 different USB ports including those directly attached to
>> > the
>> > motherboard.
>> > 6.. The device shows up as connected in the Network Connections area.
>> > 7.. Followed steps at
>> > http://www.pocketpcfaq.com/wce/activesync3.1remove.htm to totally
>> > remove
>> > ActiveSync and try again.
>> > 8.. ActiveSync 3.x worked on this machine prior to purchase of new
>> > phone.
>> > Things I have done to attempt to resolve:
>> >
>> > 1.. Uninstall and reinstall ActiveSync 4.1 many times with reboots in
>> > between uninstalls and reinstalls.
>> > 2.. Run WinsockFix -
>> > http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml.
>> > 3.. Verified that checkmarks are beside Client for MS Networks, File
>> > and
>> > Print Sharing for MS NW, Internet protocol
>> > 4.. Booted up in Safe Mode with Networking
>> > 5.. Ran NetStat -a (See attached)
>> > 6.. Ran TCPView (See Attached)
>> > 7.. Ran FPORT (See Attached)
>> > 8.. Ran TDIMON (see attached)
>> > 9.. Added the following to the registry:
>> > 10..
>> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters]
>> > 11.. "MaxPacketSize"=dword:00000001
>> > 12.. Specifically opened port 5679 in Windows Firewall
>> > 13.. Ran NetSH Winsock Reset
>> > 14.. Do an in place upgrade to Windows XP with SP 2
>> > 15.. Verified that the DHCP Client Service is running on the PC
>> > 16.. Ping from desktop to 169.254.2.1 (PPC) was successful
>> > 17.. Run Start / Run / devmgmt.msc and look under "Network Adapters"
>> > as
>> > "Windows Mobile Device #xx" where xx seems to vary depending on which
>> > usb
>> > port you are plugged in to.
>> > 18.. Ran ipconfig/all to confirm that "Windows Mobile Device #xx"
>> > shows
>> > up with an IP address of 169.254.2.2 and the DHCP server listed at
>> > 169.254.2.1
>> > 19.. Run "Route print" as command prompt to verify that there are
>> > routes
>> > there for the 169.254.2.2 interface.
>> > 20.. Disabled antivirus (NOD32)
>> > 21.. Uninstalled portions of VS2005 that may related to SmartDevices
>> > programming just in case. Made no difference.
>> >
>> >
>> > "Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT
>> > com>
>> > wrote in message news:%23BXjBhWEGHA.344@xxxxxxxxxxxxxxxxxxxxxxx
>> >> If you could give just a slightly more-detailed description it might
>> >> help
>> >> narrow the problem down. Are you connecting the device using the USB
>> >> cable that came with it? Are you connecting it *directly*, *not*
>> >> through
>> >> a USB hub, to the PC's USB port?
>> >>
>> >> You should be able to leave the XP firewall turned on. Depending on
>> >> when
>> >> you turned it off, you might want to turn it back on, make sure that
>> >> Allow Exceptions is checked, and reinstall AS 4.1, then see what
>> >> happens,
>> >> too.
>> >>
>> >> Paul T.
>> >>
>> >> "John" <john.kaufmann@xxxxxxxxxxxx> wrote in message
>> >> news:OfEhT0IEGHA.2036@xxxxxxxxxxxxxxxxxxxxxxx
>> >>> Hi, I got similar probs on a Medion MD96700 PDA with mobile5 on it.
>> >>> (XP
>> >>> Pro /Sp2, all firewall soft unloaded)
>> >>> Activesync 4.1 UK downloaded on 31.12.2005 installed after complete
>> >>> removal of Activesync 4.0.
>> >>>
>> >>> USB device is recognized and drivers loaded (Medion USB mobile - so
>> >>> it
>> >>> sounds OK)
>> >>>
>> >>> But Activesync won't ever find a device, no matter what USB-port I
>> >>> tried - even on a second PC (my lap running a french XP Pro /SP2 with
>> >>> FW
>> >>> disabled for the test).
>> >>>
>> >>> MICROSOFT can U hear me - I am starting to get really frustrated:
>> >>> this
>> >>> is between MS Mobile 5 and MS XP, theres no third party - so get the
>> >>> problem solved!
>> >>>
>> >>> regards
>> >>>
>> >>> John
>> >>>
>> >>> "ckelsoe" <charles@xxxxxxxxxx> wrote in message
>> >>> news:eoHFvjAEGHA.208@xxxxxxxxxxxxxxxxxxxxxxx
>> >>>> Here is what I have done to try to resolve this issue. Any feedback
>> >>>> would be appreciated.
>> >>>>
>> >>>> Environment:
>> >>>>
>> >>>> Windows XP with SP 2 and all patches / updates
>> >>>>
>> >>>> Connected to network, not connected to domain
>> >>>>
>> >>>> Static IP Assigned (changed to dynamic as part of diagnostics)
>> >>>>
>> >>>> I-MATE K-JAM Phone with WM 5.0
>> >>>>
>> >>>>
>> >>>>
>> >>>> Symptom: ActiveSync shows it is connecting but never connects.
>> >>>>
>> >>>>
>> >>>>
>> >>>> Observations:
>> >>>>
>> >>>> 1.. Setting the Tray notification on the Windows Mobile based
>> >>>> Device
>> >>>> shows a connection.
>> >>>> 2.. Running Ethereal shows that the port 5679 is unreachable.
>> >>>> 3.. The device shows the following message after a time: "Unable to
>> >>>> obtain a server assigned IP Address". Changing to a static ip on the
>> >>>> device makes no difference.
>> >>>> 4.. User is administrator
>> >>>> 5.. Tried 8 different USB ports including those directly attached
>> >>>> to
>> >>>> the motherboard.
>> >>>> 6.. The device shows up as connected in the Network Connections
>> >>>> area.
>> >>>> 7.. Followed steps at
>> >>>> http://www.pocketpcfaq.com/wce/activesync3.1remove.htm to totally
>> >>>> remove ActiveSync and try again.
>> >>>> 8.. ActiveSync 3.x worked on this machine prior to purchase of new
>> >>>> phone.
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> Things I have done to attempt to resolve:
>> >>>>
>> >>>> 1.. Uninstall and reinstall ActiveSync 4.1 many times with reboots
>> >>>> in
>> >>>> between uninstalls and reinstalls.
>> >>>> 2.. Run WinsockFix -
>> >>>> http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml.
>> >>>> 3.. Verified that checkmarks are beside Client for MS Networks,
>> >>>> File
>> >>>> and Print Sharing for MS NW, Internet protocol
>> >>>> 4.. Booted up in Safe Mode with Networking
>> >>>> 5.. Ran NetStat -a (See attached)
>> >>>> 6.. Ran TCPView (See Attached)
>> >>>> 7.. Ran FPORT (See Attached)
>> >>>> 8.. Ran TDIMON (see attached)
>> >>>> 9.. Added the following to the registry:
>> >>>> 10..
>> >>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters]
>> >>>> 11.. "MaxPacketSize"=dword:00000001
>> >>>> 12.. Specifically opened port 5679 in Windows Firewall
>> >>>> 13.. Ran NetSH Winsock Reset
>> >>>> 14.. Do an in place upgrade to Windows XP with SP 2
>> >>>> 15.. Verified that the DHCP Client Service is running on the PC
>> >>>> 16.. Ping from desktop to 169.254.2.1 (PPC) was successful
>> >>>> 17.. Run Start / Run / devmgmt.msc and look under "Network
>> >>>> Adapters"
>> >>>> as "Windows Mobile Device #xx" where xx seems to vary depending on
>> >>>> which usb port you are plugged in to.
>> >>>> 18.. Ran ipconfig/all to confirm that "Windows Mobile Device #xx"
>> >>>> shows up with an IP address of 169.254.2.2 and the DHCP server
>> >>>> listed
>> >>>> at 169.254.2.1
>> >>>> 19.. Run "Route print" as command prompt to verify that there are
>> >>>> routes there for the 169.254.2.2 interface.
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>


.

Relevant Pages

  • Re: ActiveSync 4.1 Still does not work...
    ... AS4.1 installs some USB ... ActiveSync, then allowing Windows to find it again. ... in the system tray for the new 'network adapter' with the 'acquiring network ... If everything seems to be set correctly, but no connection is established, ...
    (microsoft.public.pocketpc.activesync)
  • Re: ActiveSync 4.1 Still does not work... (Solved for me)
    ... (The default installation do not configure the network connection ... AS4.1 installs some USB ... > the device as new the next time we install it. ... > in the system tray for the new 'network adapter' with the 'acquiring network ...
    (microsoft.public.pocketpc.activesync)
  • Re: no Actisync with USB! Ideas?
    ... Connections via USB are made via network I/O. ... Since USB is a network connection, ... from the Internet are invoked when you try to use USB for ActiveSync. ...
    (microsoft.public.pocketpc.activesync)
  • Re: Limited or no Connectivity XP Home SP2 w/USB adapter
    ... still no network or internet activity. ... Ethernet Adapter Local Area Connection 2 ... description SMC compact usb to ethernet adapter ...
    (microsoft.public.windowsxp.network_web)
  • USB Wireless LAN card drops connections
    ... The system detected that network adapter USB Wireless LAN ... connection associated with it, that my connection would ...
    (microsoft.public.windowsxp.network_web)
Loading