I have a couple of applications on my HP iPaq 112 PDA that require an internet
connection for updates (AvantGo, an RRS news reader, stuff like that).

Anyway, for some reason when one of these programs tries to update its data a
window pops up saying that it can't establish a dialup networking connection.
For some reason it's looking for a dialup connection via a mobile phone and
bluetooth. I cannot find the settings to disable this and to force it to only
update when it sees a network coonection, either via USB/ActiveSync or if the
WiFi service is on and a network connection is established that way.

Now, thinking about this, how can I get the PDA to ActiveSync wirelessly? Can it
be done, I suppose is the first question that needs to be asked?

If I can use WiFi and a network connection to my home LAN to activesync then I
could dispense with USB connections other than to charge the battery.

Failing that, any tips on tracing down this problem that I'm having and how to
force the PDA to only try to connect when there is a network connection?

Thanks.

At 08 Jul 2008 06:58:46 +1000 Snapper wrote:
> I have a couple of applications on my HP iPaq 112 PDA that require an
internet
> connection for updates (AvantGo, an RRS news reader, stuff like that).
>
> Anyway, for some reason when one of these programs tries to update its
data a
> window pops up saying that it can't establish a dialup networking
connection.
> For some reason it's looking for a dialup connection via a mobile phone
and
> bluetooth. I cannot find the settings to disable this and to force it to
only
> update when it sees a network coonection, either via USB/ActiveSync or if
the
> WiFi service is on and a network connection is established that way.


Connectivity is determined by the network settings in
Start/Settings/Connections(Tab)/Connections/Advanced(Tab)Select Networks.

The "network" in the top or bottom dialog box contains a defined dialup
connection that is tried if no other connectivity is present. To get rid
of your dialup connection, select "Edit" then tap-n-hold on the connection
and select "delete."

Of course, this being Windows Mobile, you can't get rid of dialog boxes!
Instead of a box popping up showing the dialup attempt, you'll get a dialog
box telling you no data connection method is available, instead! ;-)

> Now, thinking about this, how can I get the PDA to ActiveSync wirelessly?
Can it
> be done, I suppose is the first question that needs to be asked?


Not these days. That was disabled for "security reasons" (the Activesync
over IP data was unencrypted, apparently.) The feature was removed in
WM5/Activesync 4.x.


> If I can use WiFi and a network connection to my home LAN to activesync
then I
> could dispense with USB connections other than to charge the battery.


Instead, you'll have to settle for sync over bluetooth, but it has far less
range.


> Failing that, any tips on tracing down this problem that I'm having and
how to
> force the PDA to only try to connect when there is a network connection?


Generally that needs to be configured in each app if possible, since it's
the app calling for the connection, not the device. For example, QMail, an
RSS, e-mail, NNTP program (that I'm pecking this reply on) has a "never
dial a conection" checkbox that limits the program to using active network
connections only.

Todd Allcock wrote...

> Not these days. That was disabled for "security reasons" (the Activesync

How patronising of Microsoft.

> Instead, you'll have to settle for sync over bluetooth, but it has far less
> range.

I've already tried. I failed miserably to get it to work. I could not get the
PC, or laptop, actually, to see or recognise the PDA during the setup phase.

I gave up in the end.

At 08 Jul 2008 19:48:15 +1000 Snapper wrote:


> > Instead, you'll have to settle for sync over bluetooth, but it has far
less
> > range.
>
> I've already tried. I failed miserably to get it to work. I could not get
the
> PC, or laptop, actually, to see or recognise the PDA during the setup
phase.
>
> I gave up in the end.

If your main concern is syncronizing PIM data (rather than files) you could
look at Funambol, a SyncML client. (Sort of a do-it-yourself open source
Exchange server.) You install the Funambol client on your device, then
install an Outlook plug-in on your PC and the devicessync over the internet-
wiFi, GSM, whatever.

You can sync to 3rd-party servers like scheduleworld.com or
my.funambol.com, or install the Funambol server software on your own PC and
sync to the PC directly.

I use Funambol to keep 3 PCs running Outlook and three mobiles in sync. It
works pretty well, although it likes creating duplicate Contacts/Calendar
entries if you try syncing with multiple methods (i.e. sync with Activesync
and Funambol.)

"Snapper" <snapper1@y7mail.com.invalid> wrote in message
news:hsd6749ncojpthr9o7ese1tk733vq2i8bc@yarwho.com ...
> Todd Allcock wrote...
>> Instead, you'll have to settle for sync over bluetooth, but it has far
>> less
>> range.
>
> I've already tried. I failed miserably to get it to work. I could not get
> the
> PC, or laptop, actually, to see or recognise the PDA during the setup
> phase.

As long as you make your PC or Laptop Bluetooth 'visible' to other bluetooth
devices, you should be able to connect the PDA to that Laptop/PC from your
*PDA*. It's not the most automatic of processes and when I first attempted a
Bluetooth connection via Activesync, I too failed. The key is to make most
of the configuration and connection effort via the PDA not the Laptop or PC.
You will need to have your Laptop/PCs active sync setup with a tick in the
connection settings box of 'allow connections to one of the following' and
choose the com port you want your bluetooth to use (I have mine set to
com4). The rest is just about enabling bluetooth on the PDA then using the
PDAs Activesync and choosing to connect with bluetooth.
>
> I gave up in the end.

Where did it go wrong Snapper? It's a bit like riding a bicycle in that once
you've got it working the first time, it doesn't seem that daunting
thereafter!

Paul Murphy wrote...

> > I gave up in the end.
>
> Where did it go wrong Snapper? It's a bit like riding a bicycle in that once
> you've got it working the first time, it doesn't seem that daunting
> thereafter!

I could not get either PC or device to see each other, despite me trying various
combos of setups.

I'll have another play when I get time. I'll go back through this newsgroup and
print out those who have posted suggestions.

Thanks for your time. It's appreciated.

"Snapper" <snapper1@y7mail.com.invalid> wrote in message
news:rtud74deppus3h7778hefio11lldijeq2k@yarwho.com ...
> Paul Murphy wrote...
>
>> > I gave up in the end.
>>
>> Where did it go wrong Snapper? It's a bit like riding a bicycle in that
>> once
>> you've got it working the first time, it doesn't seem that daunting
>> thereafter!
>
> I could not get either PC or device to see each other, despite me trying
> various
> combos of setups.

What message did you get? When you have time it would be helpful if you
document exactly and fully what occurred.

> I'll have another play when I get time. I'll go back through this
> newsgroup and
> print out those who have posted suggestions.

Just remember that most of the sequential actions of connecting a bluetooth
PPC or PDA are initiated through the handheld device and you cant go wrong
(well, in the end anyway).