Link to home
Start Free TrialLog in
Avatar of nikdanjor
nikdanjorFlag for United States of America

asked on

Palm Treo Versamail - Windows Server 2003 - Active Sync - AirSAMstateMachine error

I have a (Verizon) Palm Treo 700p and I'm having problems getting Versamail to sync with my office's Windows 2003 Server using Exchange Active Sync (Versamail default).  I have installed the latest Verizon firmware updates for the Treo that supposedly addressed networking issues (as of 9/27/07), and updated Palm Desktop (v. 4.2) and Versamail (3.5.4) as of 9/28/07.  "Test Settings" reports a successful connection, but it will not sync successfully. Our IT guy is at a loss.
When I set the incoming port at 80 (the Versamail default) I got the following error: AirSAMStateMachine.c 2214 6 HTTP/1.1 403 Request Forbidden Server: MicrosoftIIS/5.0 [followed by time, date and locale].  When I set the incoming port at 473 (as suggested by our IT guy) I got a the exact same error message.
We tried enabling SSL on the incoming port; this resulted in a different AirSam error message without regard to whether I specified port 80 or 473:  AirSAMStateMachine.c 1913 4628.
One possibility is that Versamail does not have a place to enter a Domain Name.  We tried to force it by putting our domain name followed by a forward slash then my username.
ASKER CERTIFIED SOLUTION
Avatar of souseran
souseran
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of dladowitz
dladowitz

I have the same issue
dladowitz:

Try the solution I posted above.
Avatar of nikdanjor

ASKER

lucienp:
The first reference you provided was erroneous.  The second deals with changing the certificate, but (1) I can't tell whether my problem relates to certificates, and (2) where would I find the "trusted certicate" to install in place of the one currently installed?

souseran:
The M$ article you reference requires the server to be configured to NOT use forms-based authentication, but the problem is our server intentionally DOES require forms-based authentication.  Therefore the M$ solution won't work.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial