network session persistence-how to disable it?

[Jason]

My HTC6800 mogul connects to network share through a wi-fi router. No matter
what brands of router I used, network connection will die after 12 to 16
hours. To resume the connection, it is required to do a manual power off
and on again, or putting into sleep and wakeup again.

Later on I noticed that the wireless network session is always on, while the
wired ones are not. The persistent session is cheating and troublesome. It
stays on even after the network connection turns bad (cannot do a ping or
folder scan).

I tried killing the session periodically, the network connection then stays
alive longer for about 72 hours.

Are there any registry settings in windows mobile to disable network session
persistence?

Is there better way to connect windows mobile to LAN? Blue tooth better?
ActiveSync is horrible, can't be used for this purpose.

Is it possible to resume a network connection programmatically?

 

[Paul G. Tobey [eMVP]]

Define "die".

What do you mean by "session is always on"? Or "stays on even after the
network connection turns bad"? My network card never turns off, regardless
of whether it is in active contact with an access point or not. That's
completely unrelated to whether the card is active.

Again, defined "session"? You've tried calling WNetCancelConnection() or
what?

And, one more time "resume a network connection"? You can tell the network
adapter to rebind itself, which should break any active connection to an
access point, try to establish a connection to a preferred SSID/access
point, get an IP address from DHCP, if you've configured it that way. That
won't reestablish, necessarily, a mapped network folder on a remote server,
but I think that any access to that folder should still work, although it
might take a little longer to, say, open the folder, after rebinding the
network adapter. The rebind operation is supported by OpenNETCF's Smart
Device Framework (and there are old messages in the archives about how to
P/Invoke the right calls yourself; search for IOCTL_NDIS_REBIND_ADAPTER).

As for the actual problem, it sounds to me like your DHCP lease is expiring
and your DHCP server is deciding that you should not get a new lease, or
something. If you are using DHCP, have you tried using a
statically-assigned address?

Paul T.