Odyssey Client for Windows 
Mobile version 4.51
(C) Copyright 2007
Juniper Networks, Inc.
All rights reserved.


***************************
README.TXT    Jan 12, 2007

  This file contains 
  important information
  about system require-
  ments, known problems,
  and late-breaking items
  that could not be 
  covered in the manual.


***************************
Contact information

  Juniper Networks, Inc.
  1194 North Mathilda Ave
  Sunnyvale, CA 94089

  (408) 745-2000
  (Main number)

  (408) 936-1576     
  (Technical support phone)  

  http://www.juniper.net
  (web home page)


***************************
Operating System
Requirements

 Odyssey Client runs on 
 the following operating
 systems:
  
 * Windows Mobile 2005
 * Windows Mobile 2003
 * Windows Mobile 2003 
    Second Edition
 * CE .NET 
 * CE 5.0

***************************

 New Features in version
 4.51:

  * xSec/FIPS (license
    required). See User 
    Notes for further details.
  * Auto-Scan Lists
  * IP Address display
  * DSA certificate import

****************************

Resolved Issues in version 4.51

  The following issues reported 
  in previous releases of Odyssey 
  Client for Windows Mobile are 
  resolved in Version 4.51. The 
  identifier following the 
  description is the bug tracking 
  number.

  1. Leaving the 'Detailed Status' 
     dialog open causes OAC to hang.    
     (BUG008761)

  2. OAC quarantines the adapter and 
     keeps the adapter locked down. 
     (BUG008667)

  3. EAP-FAST phase 0 fails when 
     attempting to use a "saved" 
     password. (BUG008265)
 

***************************
Known Issues in version 4.51

  1. EAP-TLS in FIPS mode 
     requires a FIPS-compliant 
     CSP (Cryptographic Service 
     Provider).  Currently 
     Microsoft only provides 
     such a CSP for RSA 
     certificates and only on 
     Windows Mobile 5 devices.


***************************
Known Issues in version 4.50

  1. On some devices,
  it is possible to getinto
  a mode where the device
  will fail to associate 
  with any AP. Your AP will
  show up in a scan, but the
  device status remains
  indefinitely in 
  "searching for access point" 
  until you soft 
  reset the device.

  2. On some devices, 
  WPA may not work.

  3. On some devices, 
  after NIC soft off, 
  Odyssey reports 
  'disconnected',
  instead of 
  'adapter not present'.

  4. Uninstall may result
  in a notification error. 
  You can avoid this problem
  by turning off the device 
  after uninstall.


Previous Known Issues


  1. If you are using the 
  HP iPaq 545x series 
  devices, you must update
  the driver for the 
  built-in WLAN NIC to 
  version number 3.2.4.133
  or later. The driver 
  update is available from
  the HP website under 
  "HP iPAQ Pocket PC 
  h5400 WLAN driver 
  Update".

  2. If you use the
  Dell Axim series devices,
  if you do not reboot the
  device before you first
  use Odyssey, Odyssey 
  does not show up in the
  Start Menu. Instead, it
  shows up in the Programs
  folder. You may see
  multiple links to 
  Odyssey in the Programs
  folder.

  3. If you use the
  Agere 1401 CF card, after
  Power off-on, Odyssey 
  continues to say "Open
  and authenticated", when
  it is actually 
  disconnected.

  4. If you use the Agere
  1401 CF card with driver
  version 7.82, install 
  the drivers before 
  installing Odyssey. 

  5. In order to use 
  Wireless Zero Config, 
  you need to either exit
  or disable Odyssey 
  Client. 

  6. If your adapter
  is configured to use 
  a static IP address, 
  you must reconfigure 
  the static IP 
  information after
  installing Odyssey 
  Client.

  7. Certicom MovianVPN
  (3.x series) is in-
  compatible with Odyssey
  Client. The 4.x series 
  is compatible, but you 
  may have to reboot your 
  device after you install
  Odyssey.

  8. Do not install 
  Odyssey 4.0 on an 
  iPaq 4150/4350 running
  Windows Mobile 2003 
  with Wireless LAN
  driver version 2.0.53A.

  10. If you eject and 
  re-insert an Omnikey 
  Cardman SIM card reader,
  you may have to reboot 
  the device for Odyssey 
  to recognize it.

  11. If you eject/
  deactivate the WLAN card
  in use and insert/
  activate another WLAN 
  card, you have to reboot
  the device for Odyssey 
  to recognize the new WLAN 
  card.

  12. If you use the 
  Socket SDIO WLAN card, 
  you might need to apply a
  ROM update to an iPaq 
  device to avoid the SDIO
  from not working after a
  Suspend/Resume or Soft 
  Reset. Please refer to 
  the Socket and HP 
  websites for more details
  on this.

  13. iPaq Wireless utility 
  shows "amber" color and 
  Manager says "Driver not
  loaded" when Odyssey is 
  installed.