Welcome to Mobility Client Version 5.0.1.4 for Windows 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. This product contains RSA encryption code. ___________________________________________________________________________ Table of contents 1.0 Software requirements 2.0 Hardware requirements 3.0 Getting help 4.0 Installing from CD 5.0 Installing from diskettes 6.0 New features 7.0 Product information 8.0 Fixed Authorized Problem Analysis Reports (APARs) 9.0 Late-breaking information 10.0 Trademarks and Copyright ___________________________________________________________________________ 1.0 Software requirements One of the following operating systems is required: - Microsoft(R) Windows(R) 98 (SE recommended) - Microsoft Windows Millenium - Microsoft Windows NT(R) Version 4.0 - Service Pack 4 or later - Microsoft Windows 2000 - Microsoft Windows XP - Microsoft Handheld PC 2000 - Microsoft Pocket PC 2002 - Microsoft Windows Mobile 2003 Also required is Microsoft ActiveSync Version 3.1 or later (for Mobility Client for Windows CE only) ___________________________________________________________________________ 2.0 Hardware requirements The Mobility Client for Windows CE provides support for the following devices: Handheld PC 2000, Pocket PC 2002, and Windows Mobile 2003. ___________________________________________________________________________ 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 3.0 or greater to display or print it. This guide is located on the web at http://publib.boulder.ibm.com/pvc/wecm/501/ ___________________________________________________________________________ 4.0 Installing from CD If your workstation has a CD drive, you can install the Mobility Client on Windows and Windows CE Handheld PC 2000 directly from CD. Follow the instructions in "Installing and configuring the Mobility Client" in the WebSphere Everyplace Mobility Client 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 User's Guide. The guide is in portable document format (PDF) and you will need Adobe Acrobat Reader Version 3.0 or greater to display or print it. This guide is located on the web at http://publib.boulder.ibm.com/pvc/wecm/501/ 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. ___________________________________________________________________________ 5.0 Installing from diskettes From any workstation that has a CD drive, you can create diskettes of the Mobility Client for Windows to install on a client system. You will need three high-density, formatted diskettes. Use a utility that can split a large file into smaller files that fit onto multiple diskettes, such as the IBM-created utility CHOPPER. Follow the instructions for CHOPPER at http://www.pc.ibm.com/qtechinfo/DSHY-44QSCB.html These diskettes can then be taken to a target system and using the same CHOPPER utility, recombined into the original single file. When CHOPPER splits a file into smaller files, it will copy itself onto the first diskette as UNCHOP.EXE. The filename_to_be_transferred is the package-for- the-web file in the Win32 or WinCE directories on the installation CD. To install Mobility Client from diskettes: Recombine the single package file onto the client system or a desktop system, then click Start --> Run and specify the package file to extract the files and install the Mobility Client. __________________________________________________________________________ 6.0 New features for version 5.0 Enhancements for the Mobility Client on the Windows operating systems that include seamless cross-network roaming. Windows 95 support withdrawn for the Mobility Client FIPS 140-2 certification for the Mobility Client for Windows 6.1 New features for version 5.0.0.2 Pocket PC 2000 support withdrawn for the Mobility Client Mobility Client support added for Windows Mobile 2003-based Pocket PC For Pocket PC devices, the base code, by default, includes encryption and IP network connectivity. FIPS 140-2 certified encryption, WTLS encryption, and additional network support are separately installable. 6.2 New features for version 5.0.1 Support for Microsoft Connection Manager for Windows Pocket PC 2002 and Windows Mobile 2003 - If you are migrating from a previous version to this version and want to use the Microsoft Connection Manager support, either define a new connection or edit the properties of your existing connection to delete the current network interface and add a new one using all default settings. Additionally, for previous releases if you configured Microsoft Connection Manager to automatically connect to the Internet using Work Settings, then change that to automatically connect to the Internet using Internet Settings. __________________________________________________________________________ 7.0 Product information Windows Platforms ----------------- -- IBM's testing has found that the Mobility Client works better on Windows 98 SE than on earlier versions of Windows 98. If your computer supports advanced power management, Windows 98 SE makes it possible to suspend your computer without breaking the network TCP/IP connections. -- For IBM PCMCIA DataTAC and IBM PCMCIA CDPD modem users: If you are using Microsoft Windows 98, power management on the PCMCIA modem slot can interfere with the correct operation of these modems. You must disable power management on the PC card slots by installing a registry patch. To install the patch, run the program regedit.exe from the Start menu, Run... prompt. Select the menu item Registry, Import registry file. When prompted, select the file name \clients\Win32\en\misc\fixes\power.reg. You should see an indication that the registry information was successfully entered into the registry. Restart your computer. -- If you are installing a modem driver for the first time on Windows 98, Windows NT, Windows 2000, Windows XP, or Windows Me, 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" may be encountered. This error is associated with InstallShield's kernel engine. Try re-installing the Mobility Client. If the error persists, please 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 ActiveSync 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. -- On Handheld PC 2000 devices, a default gateway is not supported for CDPD and other IP-based networks. If you run the Mobility Client over CDPD or other IP-based networks, do not configure the IBM Mobility Interface as the default interface. See "Limitations of Mobility Client on Windows CE" in the Mobility Client for Windows User's Guide for more information on default gateway support. -- On Pocket PC 2002 and Windows Mobile 2003 devices, the "missed call" or "notification" LED will blink when the Mobility Client changes connectivity states, such as moving in and out of range of a wireless network, suspending or resuming a connection, encountering network congestion, etc. To clear the blinking LED, tap the Mobility Client icon in the top navigation bar to review status, then tap it again to close the status pop-up balloon. On some Pocket PC 2002 and Windows Mobile 2003 devices, if you do not open the Mobility Client navigation icon, the LED will continue to blink even after the Mobility Client has disconnected and exited. _________________________________________________________________________ 8.0 Fixed Authorized Problem Analysis Reports (APARs) Problems resolved with version 5.0.0.2: IY43753 Client gets 10.150.1.3 address first time logging in after laptop suspended IY46795 Status DLL interface not working. IY46894 Roaming not enabled when using secondary auth IY47033 WECM 5.0 client on PPC is autocompleting password IY47127 RADIUS Dialog does not give focus to Userid field IY47158 RADIUS popup window does not have the keyboard icon IY47202 WECM 5.0 client never times out when it cannot initiate a RAS connection IY47347 WECM 5.0 client exits when receiving joined packets from the Connection Manager IY47530 Unable to use CDPD SLIP connection IY47544 PocketPC shows defunct compression checkbox on general properties tab IY47547 Automatically re-establish GPRS connection when lost due to out-of-range IY47582 When installing Mobility Client over Wireless Client user is told 2 resets required IY47649 Can't erase fields for RasUserid and RasPassword IY47910 Error in Win32 client online help for TCP/UDP filtering lists IY48027 Port filtering failing on client due to how ports are stored in list IY48129 NAT and TCP-Lite do not work together IY48237 Client sends data packets before authentication has completed IY48238 Authentication dialog box shows up with incorrect title IY48434 0 length RADIUS userid or password should not be allowed IY48469 Roaming with Publick Key exchange causes artcore.exe to abend IY48471 artcore.exe uses 98% cpu when connection configured using multiple PPP networks IY48527 Memory leak - inbound LCP packets (including Keepalives) not freed IY48567 LCP packets held for "joining" cause roaming delays IY48577 User is told the password is incorrect if 2 instances of the dialer are started IY49018 Client left in bad state if user reponds NO to driver signing during install IY49235 Win32 client fails to drive up Sierra Wireless 555 card IY49292 Connections folder hangs when disconnecting 1xRTT connection IY49557 Autostart app field obscurred on PPC devices IY49579 WECM client doesn't exit after repeated DMS syncs IY49609 NDIS driver cannot be loaded on first logon attempt IY49613 Packets fragmented into three or more parts are malformed and discarded by the gateway Problems resolved with version 5.0.0.3: IY50154 Client not recovering after roam with Sierra Wireless SB300 IY50286 Client unreadable in Japanese Problems resolved with version 5.0.1: IY49452 Client unable to redrive CDPD Aircard 300 after suspend on IPAQ IY50163 Rename "Maximum RTT" on client to "TCP retransmit time to live" IY50164 Change Maximum RTT to milliseconds IY50338 DOC error for API toolkit. Java not supported for CE IY50641 Client unable to communicate with modem on MIPS processor devices IY50834 WECM client connections not redriven after a suspend on a PocketPC 2002 device IY50705 Mobility Client unable to reconnect over GPRS after good connection Problems resolved with version 5.0.1.1: IY51644 Blue Screen in ARTNDINT.SYS IY51997 Failure to connect when physical IP address contains 0 in 2nd or 3rd octet. Has been seen on GPRS and UMTS networks. IY52352 Client may hang up and not recover if gateway is down. IY52579 IPAQ 2210 hangs on disconnect using the Mobility Client. IY52260 Connection fails to start when configured to "Start connection when Windows starts" IY53026 The popup keyboard on a Microsoft Windows Mobile 2003 device does not go away automatically when using the Mobility Client Problems resolved with version 5.0.1.2: IY49353 When a Mobility Client has already negotiated to a weaker encryption setting and the gateway is then changed to a stronger setting, the client will not login, even if the stronger setting is supported, without user intervention IY53401 Mobility Client fails to drive up underlying IP connection on WIN98SE IY53567 KeepAlive firestorm on roam to interface with KeepAlive=0 IY53708 Change Mobility Client to issue a message allowing the user to stop a login attempt when no interfaces are available IY53818 Mobility Client fails to reestablish a PPP/SLIP connection after it drops IY54145 Mobility Client short hold mode problens. Client appears to stop responding IY54350 eOpenApi() on Windows CE causes exception after installing 5.0.1.0. IY54396 Mobility Client causes exception on WIN98SE when trying to redrive PPP/SLIP connection. Additionally, if "Default Route" used the default route is not reset after the connection is reestablished. IY54425 Secondary RADIUS authentication is failing repeatedly when the WECM virtual network adapter fails to initialize properly the first time and then takes a long time to reinitialize IY54537 LCPKeepAlive should be set to zero (turned off) by default for dial connections IY54555 Mobility Client is not allowing LCPKeepAlive values larger than 255 IY54723 Network roam causes file transfer to abort IY54889 Only first three interfaces of a connection are used. The fourth and beyond are ignored IY55023 Connection Manager deadlock if user logs in on already logged in user ID and using TCP-Lite IY55421 Mobility Client hangs if user tries to disconnect while MC is trying to establish a RAS connection IY55517 Mobility Client Mobitex-based connections on a Pocket PC will fail IY55836 Mobility Client abnormally terminates when receiving IP fragment Problems resolved with version 5.0.1.3: none Problems resolved with version 5.0.1.4: IY54819 When WECM Mobility Client disconnects, it is stopping RAS connections that it did not start IY56368 Mobility Client connect fails if multiple cert authentication based connect attempts occur within short time period IY56627 Mobility Client is unable to connect over certain network cards when using "Default Local IP Interface". Trace shows "Can't find route to gw". IY56842 The Mobility Client does not complete its login to the Connection Manager IY57136 Memory leak in AES encryption routines may lead to a deadlock in the Connection Manager IY57357 The Mobility Client does not restore the default route or gateway defined routes if they are deleted outside of the client IY57651 The Mobility Client can cause a PocketPC device to hang when sending traffic. This was experienced on the XDA/2 device. IY57652 After connecting the Mobility Client the first time on a Windows Mobile 2003 device the user must select whether the client interface is for Work or the Internet. If the user chooses incorrectly it can disable the connection. The client will now configure itself automatically for Work. IY57974 The Italian Mobility Client for PocketPC cannot make a connection with the default "Automatically Connect" interface IY60293 Incorrect user ID over dial-up causes Gateway to disconnect IY60299 eGetInterfaceNames not returning list of interfaces configured for a connection IY60558 Mobility Client message 855 is displayed despite not being included in the ARTPOPUP.TXT file IY61018 artcore.exe goes to 100% CPU utilization IY61187 Windows/PPC Mobility Client not sending interface name in eMsg_OpenInterface event IY61204 artcore.exe application exception pop-up IY61277 artapij.dll incorrectly requires artsfc.dll to be in the path IY61744 When using RADIUS as secondary logon, and RADIUS logon packets are lost, the successful logon takes a very long time IY62544 Problems with routing after mobile device is powered off and then on again IY63095 Not receiving events from WECM client Java API for Pocket PC using WSDD IY63325 PPC Wecm client displays the notification icon even if DisableTrayIcon=1 - As part of this fix, there are now two configuration file settings: DisableTrayIcon - hides the tray icon (bottom right) when = 1 DisableNotificationIcon - hides notification icon (top) when = 1 (PPC only) IY63645 eGetNetworkCapabilities() function generates asynchronous events IY63649 eMsg_Shutdown not always sent to API clients IY63883 Reqesting Motorola PMR modem status during initialization leads to abend IY64191 Some messages are being displayed even when they are not in ARTPOPUP.TXT IY65644 DEFAULT ROUTE IS NOT RESTORED AFTER MOBILITY CLIENT DISCONNECTS IY62526 ARTDHCP MUST BE MANUALLY UNINSTALLED IN SOME CASES _______________________________________________________________________ 9.0 Late-breaking information 9.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. 9.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. 9.3 On the Siemens SX56 PocketPC 2002 device you must disable the AT&T Wireless Tools optimizations in order for the Mobility Client to automatically connect to the GPRS network. Click Start -> Wireless Tools -> Optimization Settings and clear the Use Optimization box. 9.4 On the Siemens SX56 PocketPC 2002 device, the operating system may not have enough free driver memory to load the Mobility Client's NDIS driver. This problem can be worked around by configuring the NDIS to load statically. To do this, from the Mobility Client Connections window, tap Connections -> NDIS Driver... -> Statically Load. Then, create a new Mobility Client connection. In the Create Connection wizard after providing the Connection Manager address, tap Advanced... and select "GPRS Connection" as the interface. This configuration may also require you to change the Microsoft Connection Manager applet settings. To do this, tap Start -> Settings -> Connections -> Connections. In this applet, make sure that the device connects to the Internet with "Work Settings" and that the network card connects to "Work". Also, make sure that the "This network connects to the Internet" check box is selected under the Proxy tab of "Work Settings". 9.5 On some devices and laptops, if the Ethernet cable is unplugged, it may be incorrectly reported to the Mobility Client that the adapter is available, with an IP address in the range of 169.254.0.0 - 169.254.255.255. The Mobility Client will attempt to open, activate, and use this adapter for communication with the Connection Manager, and the login attempt will time out. If this occurs, remove the adapter from the system and attempt to log in again. Intermec 700 series devices, when plugged into the Intermec docking station with the Ethernet cable unplugged, can experience this behavior. ________________________________________________________________________ 10.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, 2004. All rights reserved.