Re: ActiveSync 4.1 Still does not work...
- From: "Fredrik Caesar" <fredrik AT caesar DOT dyns DOT net>
- Date: Tue, 3 Jan 2006 09:08:16 +0100
I am also experiencing the same problem
It usually works the first time, then when you disconnect the USB cable and
reconnects activesync cannot reconnect.
I can solve the problem (workaround) by restarting my Windows Mobile device
every time i want to connect it to my desktop computer. What a nice feature.
"ckelsoe" <charles@xxxxxxxxxx> wrote in message
news:eLt1QPCEGHA.2912@xxxxxxxxxxxxxxxxxxxxxxx
>I have checked and Activesync is listed in the exceptions as ActiveSync
>Application, ActiveSync Connection Manager, ActiveSynd RAPI Manager, and
>ActiveSync Service.The scope has been changed to Any Computer as an
>alternative to the default custom list.
>
>
> "Chris De Herrera" <spam@xxxxxxxxxxxxxxxx> wrote in message
> news:eRnfVxBEGHA.3064@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi,
>> Did you setup all the firewall rules for ActiveSync 4.1? See
>> http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm #1.
>>
>>
>> --
>> Chris De Herrera
>> http://www.pocketpcfaq.com
>> http://www.tabletpctalk.com
>> http://www.pocketpctalk.com
>> http://www.mobilitytalk.com
>>
>> ActiveSync 4.x Troubleshooting Guide -
>> http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm
>>
>> "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.
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- References:
- ActiveSync 4.1 Still does not work...
- From: ckelsoe
- Re: ActiveSync 4.1 Still does not work...
- From: Chris De Herrera
- Re: ActiveSync 4.1 Still does not work...
- From: ckelsoe
- ActiveSync 4.1 Still does not work...
- Prev by Date: Re: ActiveSync 4.1 Still does not work...
- Next by Date: Activesync not creating connection
- Previous by thread: Re: ActiveSync 4.1 Still does not work...
- Next by thread: Re: ActiveSync 4.1 Still does not work...
- Index(es):
Relevant Pages
|
