|
Posted by Sven on January 14, 2007, 10:04 pm
Please log in for more thread options We are way over my head here. I am a bit surprised at the error message
though. Don't think I have ever seen that with a USB based AS connection.
WM5 does do things a bit different than previous versions though. I can
tell that you are seeing the right IP addresses. when connected via USB my
PC IPConfig shows
Ethernet adapter Local Area Connection 16:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Windows Mobile-based Device #14
Physical Address. . . . . . . . . : 80-00-60-0F-E8-00
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 169.254.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 169.254.2.1
Lease Obtained. . . . . . . . . . : Sunday, January 14, 2007 7:51:27
PM
Lease Expires . . . . . . . . . . : Tuesday, February 13, 2007
7:51:27 PM
And the device IP shows 169.254.2.1 using vxUtil, which you can get free
from www.cam.com
Beyond that I usually have to sacrifice a chicken to get AS to work, if it
doesn't do it on it's own.
--
Sven
MVP - Mobile Devices
> Hi Sven, thanks for your comments.
>
> ok, I've :-
> 1. turned off Windows firewall,
> 2. tempoarily disabled my ethernet lan
> 3. set my Sygate firewall to pass packets as specified in
> http://www.microsoft.com/windowsmobile/help/activesync/default.mspx
> 4. turned off all other Sygate action (in Tools.Options.Security).
> 5. turned off McAfee virus scanner
> 6. reset the pda and reconnected it.
>
> The pda still shows "Unable to obtain a server-assigned IP address", and
> still hangs when transferring files.
> ***This first point seems odd, as the firewall log shows that it has
> accquired an IP address ok
> (the log appears below).
>
> Do I need any particular services running for ActiveSync to work properly?
>
> Colin
>
>
>
> The firewall log :-
>
>
> Time Action Severity
> Direction Protoocl Remote Host Remote MAC RemotePort Local Host
> Local MAC Local Port Application name
>
> 377100 01/14/2007 21:22:31 Allowed 3 Incoming UDP 169.254.2.1
> 82-00-60-0F-E8-00 67 255.255.255.255 FF-FF-FF-FF-FF-FF 68
> C:\WINDOWS\system32\svchost.exe
> 377101 01/14/2007 21:22:31 Allowed 10 Outgoing UDP 255.255.255.255
> FF-FF-FF-FF-FF-FF 67 0.0.0.0 80-00-60-0F-E8-00 68
> C:\WINDOWS\system32\svchost.exe
> 377102 01/14/2007 21:22:31 Allowed 3 Outgoing UDP 169.254.2.1
> 82-00-60-0F-E8-00 5679 169.254.2.2 80-00-60-0F-E8-00 1439 C:\Program
> Files\Microsoft ActiveSync\rapimgr.exe 377103 01/14/2007 21:22:36 Allowed
> 3 Incoming TCP 169.254.2.1 82-00-60-0F-E8-00 1029 169.254.2.2
> 80-00-60-0F-E8-00 990 C:\Program Files\Microsoft ActiveSync\rapimgr.exe
> 377104 01/14/2007 21:22:36 Allowed 3 Incoming TCP 169.254.2.1
> 82-00-60-0F-E8-00 1030 169.254.2.2 80-00-60-0F-E8-00 990 C:\Program
> Files\Microsoft ActiveSync\rapimgr.exe 377105 01/14/2007 21:22:59 Allowed
> 3 Incoming UDP 169.254.2.2 80-00-60-0F-E8-00 137 169.254.2.255
> FF-FF-FF-FF-FF-FF 137 C:\WINDOWS\system32\NTOSKRNL.EXE 377106 01/14/2007
> 21:22:59 Allowed 10 Outgoing UDP 169.254.2.255 FF-FF-FF-FF-FF-FF 137
> 169.254.2.2 80-00-60-0F-E8-00 137 C:\WINDOWS\system32\NTOSKRNL.EXE 377107
> 01/14/2007 21:23:08 Allowed 3 Incoming UDP 0.0.0.0 82-00-60-0F-E8-00 68
> 255.255.255.255 FF-FF-FF-FF-FF-FF 67
> 377108 01/14/2007 21:23:08 Allowed 3 Incoming UDP 169.254.2.2
> 80-00-60-0F-E8-00 138 169.254.2.255 FF-FF-FF-FF-FF-FF 138
> C:\WINDOWS\system32\NTOSKRNL.EXE
> 377109 01/14/2007 21:23:08 Allowed 10 Outgoing UDP 169.254.2.255
> FF-FF-FF-FF-FF-FF 138 169.254.2.2 80-00-60-0F-E8-00 138
> C:\WINDOWS\system32\NTOSKRNL.EXE
>
>
>
> Sven wrote:
>> I'll get started here, though others can do much better. You do not need
>> to set any IPs in either your PPC or the PC for ActiveSync to work. The
>> IPs that it uses are fixed and the same for everybody. Makes no
>> difference what other IPs are being used for other things. Typically what
>> your sort of symptom indicate is that some firewall/security program has
>> decided that the little network AS has set up is foreign and not to be
>> trusted, and applications using it, AS, it's sync manager, etc. should
>> not be allowed to connect. The built in Windows Firewall has been
>> implicated in the past for this behavior and lately folks have seemed to
>> have problems with MSs own Live OneCare thing.
>>
>> Any firewalls, anti-virus, etc., things running, that might help the real
>> AS wizards help.
>>
|