Google Answers Logo
View Question
 
Q: Slow remote syncs via IBM Mobile Connect to Lotus Notes ( No Answer,   1 Comment )
Question  
Subject: Slow remote syncs via IBM Mobile Connect to Lotus Notes
Category: Computers > Wireless and Mobile
Asked by: gauly-ga
List Price: $10.00
Posted: 01 Sep 2002 22:26 PDT
Expires: 01 Oct 2002 22:26 PDT
Question ID: 60838
I have recently installed IBM Mobile Connect v2.61 to allow 4 X Compaq
3970 Ipaq handhelds to connect to our Lotus Notes 4.6(7) Domino
environment.

I have configured the Ipaqs to sync with the specific users mail file
and address book.

Syncs direct to the network via the handheld cradle work fine.
Syncing when remote and via handheld IR through IR mobile phone and
our RAS, also works ok, with with typical start/finish connection
times being around 3 - 5 minutes.
We do however get frequent slow remote syncs, that if left to
complete, take as long as 25 minutes, during which time the sync seems
to stall in the Inbox!!
This is despite default email settings ie max 1mb attachments,
truncation at 1000 characters, Unread email only and only 2 days worth
of these!!

At 25 minutes, this is time consuming and costly.

Users who experience this have mail files running in excess of 400mb
in size! Does size matter here!?!? My mail file is 50mb, and while I
too have experienced the above, it is not any where as frequent.

Any clues?
Answer  
There is no answer at this time.

Comments  
Subject: Re: Slow remote syncs via IBM Mobile Connect to Lotus Notes
From: cobbler-ga on 01 Oct 2002 07:12 PDT
 
Gauly,
Unless a large amount of data is being transferred, the sync should
not take significantly longer than a sync via the network/cradle.
Check in the IMC connlog database to see if the slow connections are
accompanied by error messages (these errors may not be shown on the
iPAQ at the end of the session because they might only be warnings.)

If there are messages along the lines of "...performing slow/initial
sync" then this means that the sync history has been thrown away and
all of the data has been sent back down to the device - this could
certainly take a fairly long time over a wireless link. If this is
happening then you will need to look at why the initial syncs are
being generated. This is probably not related to the comms link and
could be happening for cradle syncs as well, it's just less
noticeable. Reasons for slow syncs could be : using a different
username on the same device, running a backup/restore onto the iPAQ,
using ActiveSync as well as IMC to sync the mail. In general with IMC
2.61 these slow syncs shouldn't happen for no good reason. Check that
you client and server versions match.

If there are no "initial sync" type messages then IMC won't be moving
very much data down to the iPAQ so the sync shouldn't take a long time
regardless of the comms link. In this case I'd begin to experiment
with connection methods (eg. via an ISP) which by-pass the RAS server
(open port 5001 to the IMC server) and see if maybe the RAS server is
contributing to the problem.

Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Google does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. Please read carefully the Google Answers Terms of Service.

If you feel that you have found inappropriate content, please let us know by emailing us at answers-support@google.com with the question ID listed above. Thank you.
Search Google Answers for
Google Answers  


Google Home - Answers FAQ - Terms of Service - Privacy Policy