Welcome to Mobility Client Version 5.1.1.2 for Windows(R) and Windows CE, a component of IBM(R) WebSphere(R) Everyplace(R) Connection Manager This README file contains information you need for installing and running the Mobility Client. It also contains information that was not available for our publications. ___________________________________________________________________________ Table of contents 1.0 Software requirements 2.0 Hardware requirements 3.0 Getting help 4.0 Installing from CD 5.0 New features 6.0 Product information 7.0 Fixed Authorized Problem Analysis Reports (APARs) 8.0 Late-breaking information 9.0 Trademarks and Copyright ___________________________________________________________________________ 1.0 Software requirements One of the following operating systems is required: - Microsoft(R) Windows 2000 - Microsoft Windows XP - Microsoft Pocket PC 2002 - Microsoft Windows Mobile 2003 - Microsoft Windows Mobile 2003 Second Edition - Microsoft Windows CE .NET 4.2 For Mobility Clients on Windows CE only, use Microsoft ActiveSync. ___________________________________________________________________________ 2.0 Hardware requirements The Mobility Client for Windows CE provides support for the following devices: Pocket PC 2002, Windows Mobiles 2003-based Pocket PC, Windows Mobile 2003 Second Edition, and selected Windows CE .NET 4.2 devices. ___________________________________________________________________________ 3.0 Getting help Online help is available in the Mobility Client product. See the IBM WebSphere Everyplace Mobility Client User's Guide for more information about the types of help that are available and instructions on how to access help. The guide is in portable document format (PDF) and you will need Adobe Acrobat Reader Version 5.0 or greater to display or print it. This guide is located on the web at http://publib.boulder.ibm.com/pvc/wecm/511/ ___________________________________________________________________________ 4.0 Installing from CD If your workstation has a CD drive, you can install the Mobility Client on Windows and Windows CE directly from CD. Follow the instructions in "Installing and configuring the Mobility Client" in the WebSphere Everyplace Mobility Client for Windows User's Guide to install from CD. For instructions on downloading the Mobility Client code for all platforms, see "Applying Maintenance" in the WebSphere Everyplace Mobility Client for Windows User's Guide. __________________________________________________________________________ 5.0 New features for version 5.1 -- Added support for Windows Mobile 2003 Second Edition -- Removed support for Microsoft Windows 98, Windows Me, Windows NT(R), and Handheld Pocket PC -- The Mobility Client can be configured to check that certain programs are running, like antivirus or personal firewall software, before allowing the connection to start. -- The Mobility Client can be configured to automatically start one or more programs after the initial connection successfully completes. -- Mobility Client configuration files can be exported and imported which gives an administrator the ability to set or change Mobility Client options, and then distribute the new configuration to the client. The user imports the new configuration and accepts the changes. -- An aid in problem determination, the Mobility Client trace viewer is a facility the user can use for first failure data capture, especially useful during a connection attempt. -- Removed support for wireless transport layer security (WTLS) encryption. -- The Mobility Client now receives most network tuning parameters from the Connection Manager at connect time which eliminates configuration tasks on the Mobility Client. The client transmits characteristics of the connection to the Connection Manager so the configuration data is appropriate for the type of connection being used. -- The Mobility Client automatically adjusts network and IP stack maximum transmission unit (MTU) sizes based on the type of IP interface used to communicate to the Connection Manager. -- The Mobility Client automatically adjusts the network MTU size to avoid network black holes. 5.1 New feature for version 5.1.0.1 -- Added support for limiting the Mobility Clients that are permitted to log on to the Connection Manager by device class. This capability is a security feature of the connection profile that is assigned to the mobile network connection (MNC) to which the client logs in. 5.2 New feature for version 5.1.0.2 -- Added support for the Mobility Clients on the CE .NET operating system using Psion 7535 devices. 5.3 New features for version 5.1.1 -- Added support for the Mobility Clients on the CE .NET operating system using Psion 7525 and Fujitsu TeamPad 500 devices. -- Added support for the ASTRO network on desktop Windows only. See the Gatekeeper online help for information on how to configure ASTRO support. See the Windows online help for information on configuring an ASTRO network type on the Mobility Client. See the Mobility Client for Windows User's Guide for information on the available configuration parameters. -- Enhanced the IP-based network support when using a Dial-up Networking connection so you can place it in short-hold mode to Suspend the connection, then choose when to Resume the connection. There is new online help available for the Network Properties Suspend tab. -- Enhanced the installation to add an automatic digital signature. -- Added TCP-Lite and HTTP codec support for the Mobility Client on Windows Mobile 2003 and selected Windows CE .NET devices 5.4 New features for version 5.1.1.1 -- Added support for smart card authentication on the Windows XP and Windows 2000. 5.5 New features for version 5.1.1.2 -- The data compression libraries based on the Lempel-Ziv-Welch algorithm as provided by ZLib are used by the Mobility Client for Windows. __________________________________________________________________________ 6.0 Product information Windows Platforms ----------------- -- If you are installing a modem driver for the first time on Windows 2000 or Windows XP, you may be prompted to enter a country code and area code for your computer. This is normal, even if the modem is a wireless modem that does not make use of this information. Enter the information when prompted. -- When installing the Mobility Client on Windows XP, an "IKernel.exe - Application Error" might be encountered. This error is associated with InstallShield's kernel engine. Try re-installing the Mobility Client. If the error persists, refer to InstallShield's Consumer Central web-site: http://consumer.installshield.com/kb.asp?id=Q108190 for further instructions. The Document ID associated with this problem is Q108190. -- When upgrading from a version prior to 2.1.1.11, you must stop the client prior to upgrading. If you do not, you may leave the client in a corrupted state. Should this happen, contact IBM support for recovery directions. Windows CE Platforms -------------------- -- If you are using any of the Socket Communications Serial I/O Cards (Serial I/O, Dual Serial I/O) on Windows CE to connect to a Mobitex, DataTAC, or Dataradio serial modem, the Mobility Client cannot accurately detect when the modem is not responding or is disconnected because the I/O card does not always report write failures. As a result, the client may display timeout error messages, but might not shut down as it would normally do when unable to write to a modem. -- If you are using the built-in serial port on a Windows CE device to connect to a modem, be sure to choose the modem named "Hayes Compatible on COM1:" when setting up your Mobility Client connection. Do not choose "Serial Cable on COM1:" since the Mobility Client will not work in this case. Also, be aware that when using the built-in serial port, you will need to use a NULL modem adapter or cable to connect to your external modem. _________________________________________________________________________ 7.0 Fixed Authorized Problem Analysis Reports (APARs) For more information, see the product Support web site at: http://www.ibm.com/software/pervasive/ws_everyplace_connection_manager/support Problems resolved with version 5.1.0.1: IY63649 eMsg_Shutdown not always sent to API clients IY63883 Reqesting Motorola PMR modem status during initialization leads to ab end IY64191 Some messages are being displayed even when they are not in ARTPOPUP.TXT Problems resolved with version 5.1.0.2: IY59204 When 5.1.0.1 Client connects to 5.1.0.0 Gateway, secondary auth may abend IY65254 Context help not displayed for the Japanese Mobility Client IY65633 When WiFi is set at a lower priority than GPRS, GPRS suspends IY65644 Default route is not restored after Mobility Client disconnects IY66034 Mobility does not recognize RF MODEM902M IY66338 Mobility Client not using proper interface for logins. IY66121 Buffer overrun while roaming using Mobility Client IY67098 Client does not properly reset an interface that has been excluded, then included, in the roaming GUI Problems resolved with version 5.1.1: IY59818 Intermitttently, we are seeing RADIUS authentication failures with no return error code other than AuthenticationFailed IY67025 Mobility Client not resuming top priority RAS connection IY68563 Initialization timer needed in Mobility Client IY68768 Problems connecting to Motorola PMR network with the vrm 850 - added vrm 650 and vrm 850 profiles IY69045 DMS packages for PPC installed twice with WEA 5.0.1, 5.0.2 IY69049 Device ID is not enabled on newer Win32 platforms IY69080 Mobility Client stops transmitting or receving packets once the PDA falls into the standby mode IY69398 WECM issue where you cannot build preconfigred install using "Default Local IP" for multiple languages IY69459 The pre-configured installation is not working correctly when prereq checking is configured IY70199 Advanced IP Network connections are not migrated from 5.0.1 Mobility Client on Pocket PC IY70228 There is a need to increase the routing table entries IY70253 Mobility Client does not read ports to filter at roam time IY70379 Default route not restored on WM2003 after disconnect IY70980 WECM client incorrectly in and out of range IY71210 Import feature does not honor desktop shortcut links IY71783 Korean language pack does not install on PocketPC IY71787 When installing Mobility Client on Korean device the client GUI does not fit screen IY71827 Customer unsuccessful with using the artdial /d command to end the Mobility Client session IY72121 Mobility Client may hang if adapter's NDIS driver does not respond to protocol stack send of UDP packet IY72194 Mobility Client routes removed IY72379 Mobility Client for Microsoft Windows CE.NET displays only English messages even for translated clients. IY72578 Device ID fails when userPassword attribute is SHA or SSHA encoded in DSS Problems resolved with version 5.1.1.1: IY72691 Backup connections not retained when less than 3 chars (actually when sharing leading characters with another backup connection name) IY74434 Access violation in artcore.exe at address 0X10445E94 when attempting to log in IY74547 WECM Client's connection dropped when using Verizon software IY74614 Update Mobility Client to work around when applications do not process API messages sent by the client in a timely manner IY74917 Increased potential for packet loss when roaming between networks IY76053 Mobility Client hangs when disconnecting from Dataradio network IY76061 Mobility Client may lose packets when roaming between networks IY76484 Failure to roam using default IP interface and default route IY76531 TCP-Lite fails to decompress PDUs when the uncompressed size is larger than 4096. This affects sessions that use the zlib compression algorithms (Pocket PC). Problems resolved with version 5.1.1.2: IY77385 Default route removed from Mobility Client routing table IY77545 Queued IP packets are lost before roam completes IY77546 Deadlock in Mobility Client when roaming IY77548 Mobility Client exception when shutting down IY78117 Interace name not being returned on eMsg_OpenInterface API IY78776 Roam across networks fails when using TPKDP and no encryption IY78777 Default routes from other adapters not always deleted IY78804 Mobility Client does not format the header correctly for DataTAC network version 5000 (Australia). Applies to Mototola PMR IY79307 Modem profiles for VRM 650 and VRM 850 for Motorola PMR are missing from install image IY79555 Enable configuration to specify adapters to exclude IY79596 Enable an option where the client will treat unrecognized PDUs as broadcast messages IY79991 First LCP packet on Dataradio is fragmented _______________________________________________________________________ 8.0 Late-breaking information 8.1 The Sierra Wireless AirCard 555 for Verizon creates two network connections on a Pocket PC: "-Express Network" is a connection which should be able to be driven by the Mobility Client as well as Pocket IE. However, neither application is able to use this connection. The second connection called "Sierra Aircard" is an NDIS interface. This connection can only be connected using the Sierra Wireless Watcher program. Therefore, when using the Mobility Client for Pocket PC with the Aircard 555, specify either "Sierra Aircard" or "Default Local IP Interface" when you define your connection and use the Sierra Wireless Watcher program to start and stop the 1xRTT connection. 8.2 For the Intermec WiFi adapter and the Symbol WiFi adapter, the Mobility Client installs two status DLL files in the installation directory which enables client roaming when using these interfaces on Pocket PC 2002 and Windows Mobile 2003. Because the files are hidden, view them from File Explorer by tapping and holding in a blank part of the window until a message displays to view all files. The files are named IntermecWiFiStatus.dll and Symbol8056WiFiStatus.dll. The Mobility Client can have knowledge of network connectivity events for these adapters because the DLL can retrieve modem-specific information and pass it to the Mobility Client. For example, the Mobility Client can be aware when a given network is no longer available. Edit the artour.ini file and in the Interface section associated with your adapter, set StatusDLL=dllname.dll, where dllname is one of the two files in the installation directory. 8.3 On the Psion 7535 CE .NET device, clicking the question mark (?) in the title bar of a dialog box, then clicking an item in the the dialog box does not display the What's This help for the item. Instead, the browser displays the top of the Help topics file. 8.4 IY79596 enables the Mobility Client to be configured to forward inbound packets for which the protocol is unrecognized to the UDP broadcast port. To enable this function set PDU2Bcast=1 in the connection section of artour.ini. 8.5 IY79555 enables the Mobility Client to be configured to exclude specific adapters. For example, a connection that is defined to use the "Default Local IP Interface" can be configured to ignore a specific WiFi adapter. To enable this function, set ExcludeAdapters= in the interface section of artour.ini to a list of comma-separated adapter names. The names can be either a full adapter name, or the first few characters of a name. Spaces are not allowed after the comma (,) separator. For example, to exclude two adapters, one named "Intel(R) PRO/Wireless 2200BG Network Connection" and one named "Sprint PCS Vision - Novatel Wireless", configure ExcludeAdapters=Intel(R) PRO/Wireless 2200BG Network Connection,Sprint PCS Vision This could be alternativly configured as ExcludeAdapters=Intel,Sprint which would exclude any adapters starting with the characters "Intel" or "Sprint". ________________________________________________________________________ 9.0 Trademarks and Copyright Everyplace, IBM, and WebSphere, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. Copyright International Business Machines and others, 1994, 2006. All rights reserved.