Welcome to Mobility Client for Windows and Windows CE Version 4.2.3, a component of IBM(R) WebSphere(R) Everyplace(R) Connection Manager Version 4.2.3. 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 Trademarks and copyright ___________________________________________________________________________ 1.0 Software requirements One of the following operating systems is required: - Microsoft Windows 98 (SE recommended) - Microsoft Windows Millenium - Microsoft Windows NT Version 4.0 - Service Pack 4 or later - Microsoft Windows 2000 - Microsoft Windows XP - Microsoft Windows CE V3.0 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 systems: Handheld PC 2000, Pocket PC, and Pocket PC 2002. ___________________________________________________________________________ 3.0 Getting help Online help is available in the Mobility Client product. See the IBM WebSphere Everyplace Connection Manager Administrator's Guide for more information about the types of help that are available and instructions on how to access help. ___________________________________________________________________________ 4.0 Installing from CD If your workstation has a CD drive, you can install the Mobility Client directly from CD. Follow the instructions in "Installing and configuring the Mobility Client on Windows and Windows CE" in the Mobility Client User's Guide to install from CD. If you have previously installed, see the Administrator's Guide for information about applying maintenance. 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://www-1.ibm.com/support/search.wss?rs=804&tc=SSZQDW&dc=DA400. ___________________________________________________________________________ 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 None at this time. __________________________________________________________________________ 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 95 Version 4.00.950B or 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 95, 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. 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. -- DHCP is not supported for the IBM Mobility Client Interface on Handheld PC Professional or Pocket PC devices. It is supported on Handheld PC 2000 and Pocket PC 2002 devices. The IBM Mobility Client Interface must be configured with a static IP address. This address must match the IP address configured for the user at the Connection Manager. See "Limitations of Mobility Client on Windows CE" in the of the Mobility Client Users's Guide for more information on DHCP support. -- On all Windows CE devices except Pocket PC 2002 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 Client Interface as the default interface. See "Limitations of Mobility Client on Windows CE" in the of the Mobility Client Users's Guide for more information on DHCP support. _________________________________________________________________________ 8.0 Fixed Authorized Problem Analysis Reports (APARs) Problems resolved with version 4.2.3: IY39419 NDIS Driver fails to load on Windows CE IY40531 CE client not displaying autostart portion of GUI on backup tab IY40888 Printing on HPC when EWC is loaded causes device to lock up IY41098 Client fails to connect when on same LAN segment as Gateway IY42363 Buffer too small when receiving RADIUS messages with text IY47347 (PocketPC) WECM V5.0 Client Disappearing (client exits abnormally during data transfer) IY49579 (PocketPC) WECM client doesn't exit after repeated failed Device Manager synch attempts IY49609 (PocketPC) NDIS driver cannot be loaded on first logon attempt after soft reset IY46929 Login delay using DH key exchange and secondary authentication IY49018 client left in bad state if user reponds NO to driver signing 20263 MEMORY LEAK: leak on PocketPC when compression uncompressible packets IY50630 Client will not run on Windows 95. Problems resolved with version 4.2.3.1: IY43785 Memory leak causes windows CE clients to terminate Problems resolved with version 4.2.3.2: IY43968 Change DataTAC (motient) client to stop sending data packets when out of range. IY44433 Slow recover from dead spot on DataTAC (motient) network. This fix includes serializing the writing of data packets to the modem, the addition of a rim802d.pro modem profile, user control over modem shutdown commands (via ini setting NCLInitSteps), and change to load TCP opt retry timeout value (ALPMaximumRTT) from the interface section of the ini file before defaulting to the value in the connection section of the ini. IY44338 In-Range message sent before network available. IY42176 Limitation on OU field to 32 characters presently IY45020 SetActiveInterface returning a false already active status IY45023 Out of range indicator is not always accurate for network state IY45558 Client thrashing between PPP/WAN and 802.11b doing roaming IY46093 Windows App Log cluttered with warning messages from client IY46098 Intermittent WECM client dialer failure Problems resolved with version 4.2.3.3: IY46929 Login delay using DH key exchange and secondary authentication IY47105 Client does not switch to backup gateway in HACMP environment IY47105f_1 Client does not switch to backup gateway in HACMP env IY47347 Hill AFB - WECM V5.0 client disappearing IY48027 Filtering fails for some ports IY48129 NAT and TCP-Lite do not work together IY49018 Client is left in a bad state if NDIS driver is not installed IY49579 PMR 22261-033 Qualex - WECM client doesn't exit after repeated IY49609 NDIS driver cannot be loaded on first logon attempt IY50422 Client fails to start on MIPS processor H/PC Pro devices IY50630 Client cannot talk to modem on Windows 95 Problems resolved with version 4.2.3.4 IY53482 Client cannot initialize modem on Cyrix processor computer IY54796 Connection Manager deadlock if user logs in on already logged in user ID and using TCP-Lite IY57655 Corruption of the Mobility Client's artour.ini file _________________________________________________________________________ 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, 2004. All rights reserved.