Cadenza with Windows CE and Palm issues and solution
Tags :Domino 7
We have had great success and numerous frustrations
with Commontime over the past could years. Most of the frustrations
were at times of upgrades. After working with Commontime we would
always get a resolution, but getting it in hand seemed to be the problem.
So this year we cornered them at Lotusphere on the vendor floor during
a slow time. It seems one of the wireless Palm Treo phones decided
it could not sync nor could you set the password.
It had a default password on the screen
(at least there were tiny asterisks in place of the password) but we could
not tell if it was really there or something they put in. We tried
manipulating the config doc for that person in the control database to
no avail. So at Lotusphere we found out that the code version had
a tiny bug that would not let you configure the password on the device.
At all. They took his Treo for a couple hours, cleaned up some
backend log and config things that get hidden and left behind (we were
told) and viola, a new version gets installed on it and we can change the
password on the device again. The funny part was that calling support
we were told someone there ran the same device but we could never, ever
get that person on the phone to see what the deal was.
So we run the Windows CE and Palm integration
in Enterprise mode on the server letting multiple device types sync. Keep
in mind that it uses two different services to do that. The Thin
Client Connector is for the Palm devices and the Commontime main service
is for CE. Both listen on different ports by default also. Port
603 for CE and 608 for Palm. Huge thing to know for wireless synching
and firewalls. But awesome for me anywhere I can get an 802.11b connection
for my PDA. Or anywhere the Treo can get a signal now.
blog comments powered by Disqus
On Monday, February 27th, 2006 by Chris Miller
