TCP/IP Best Practices
This section provides general best practices for TCP/IP. For security-specific best practices, see TCP/IP Security.
When a device resumes from a suspended state, the network adapters are unloaded and then reloaded. The multicast membership is preserved for PCI adapters. However, for PCMCIA adapters, you must set ResetOnResume in the registry to preserve the multicast membership. For more information about this registry setting, see TCP/IPv4 and TCP/IPv6 Common Registry Settings.
By default, the following conditions prevent a Windows Mobile device from automatic suspension due to inactivity:
Connected TCP sockets, including loopback
Connected IR sockets
Active network adapters
An established PPP connection
You can use the NoIdleIfAdapter and NoIdleIfConnected registry values to configure a device to suspend automatically after a certain period of inactivity. For more information, see TCP/IPv4 Configurable Registry Settings.
You can also use the following registry values to configure a device to suspend automatically after an inactive period:
Default setting is 0 (False). Setting this value to 1 (True) allows the device to auto-suspend while a PPP section is active.
Default setting is 0 (False). Setting this value to 1 allows the device to idle-suspend when active IR sockets are open.
Note: The registry settings that affect device suspension are global and are read when the device is initialized. If you change these settings, you must reset the device before the new settings take effect.
For more information, see: