Chris,
You are "THE MAN"!!!
First, let me tell everyone: I know Chris from the LA Pocket PC Users Group.
He is an awesome resource and an extremely helpful and friendly individual.
Why MS doesn't have him on the payroll somewhere is beyond me...
Anyway, I have scoured the newsgroups and MS' ActiveSync troubleshooting
pages for help and couldn't find anything. It was only when I inplemented
Chris' instructions from his website that I got the device to sync through my
ISA and Firewall issues.
In case anyone else is having similar problems, here is the info that made
the difference:
First, Chris' page:
http://www.pocketpcfaq.com/faqs/acti...x-firewall.htm
Second, I had added the ports he (and MS) mentioned as exceptions in the
Windows Firewall. No joy yet.
Third, item 5 in the URL above:
If you are using Microsoft's ISA Firewall Client, you need to create a file
called c:\program files\microsoft activesync\wspcfg.ini with the following in
the text file or download and execute create_wspcfg_activesync.bat:
[rnaapp]
disable=1
Also, the network administrator may have to setup the ISA server's Local
Address Table (LAT) to allow 169.254.2.1 and 169.254.2.2 (for Windows Mobile
5.0 devices) and 192.168.55.100 and 192.168.55.101 (for Windows Mobile 2003,
2003 SE and prior devices).
I downloaded and ran the batch file, added the LAT addresses to my ISA
server, restarted the ISA service and rebooted my PC. When I connected the
device, it finally synced.
Chris, again, thank you for your expertise and very timely help. I never
would have found this without your help.
"Chris De Herrera" wrote:
> Hi,
> With ISA Server and the Windows Firewall Client, you need to enable the
> exceptions for ActiveSync. See
> http://www.pocketpcfaq.com/faqs/acti...x-firewall.htm for a
> partial solution.
>
>
> --
> 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/acti...shoot-as4x.htm
>
> "ssanchez" <> wrote in message
> news:158439A4-A61C-43AE-8461-...
> >I have a Verizon XV6700 Windows Mobile 5.0 PDA phone. I have installed
> > Active 4.2 on my office computer that is running Windows XP PRO, SP2. I
> > have administrator rights and my old PDA still syncs with no problem. When
> > I
> > dock the new PDA phone, ActiveSync says it is connecting (using USB) for a
> > minute or two and then I receive "Activesync connot connect to the
> > Windows Mobile powered device. To troubleshoot the problem, click OK."
> > This opens the troubleshooter which discovers nothing significant other
> > than it cannot connect to the device. The link it provides me talks
> > about access to port 990, but I don't know if/where I can remedy this.
> >
> > My Win XP Pro SP2 PC connects through an ISA server and uses a proxy and
> > Windows Firewall client. I checked and the ActiveSync install seemed to
> > install the necessary exceptions in the firewall. I'm not even trying to
> > go
> > out over the internet yet so I don't know if the ISA server is a problem
> > or
> > not. I can't even get my PC to sync with the new device.
> >
> > When I dock the phone, it starts up ActiveSync and I can see the device in
> > my device manager under Network Adapters as a Windows Mobile-based Device
> > so
> > I think everything is installed right. My "guess" is that there is some
> > problem with the firewall client or proxy on the PC that is somehow
> > preventing ActiveSync from connecting the device to the PC. When I hard
> > reset
> > the device, it installed a number of specialized CAB files which I believe
> > setup the device to work with the Verizon network.
> >
> > The phone works fine and as I've searched online, everything seems to
> > point
> > to the firewall. ActiveSync seemed to install the ActiveSync Application,
> > RAPI Manager and Service as Exceptions, and I added TCP Port 990 as an
> > Exception hoping that was the problem, but still no sync.
> >
> > Can anyone suggest what I should try or where I should look for the
> > problem?
> > At this point everything looks right, but when the sync starts, it can't
> > sync
> > with the device, even though the USB starts the sync and the Device
> > Manager
> > sees the device.
> >
> > Thanks for any help!
>
>
>