Beruflich Dokumente
Kultur Dokumente
Server 2003
Copyright
19992006byNetMotionWireless,Inc.Allrightsreserved.Nopartofthispublicationmaybereproduced, transmitted,transcribed,storedinaretrievalsystem,ortranslatedintoanylanguage,inanyformbyany means,withoutthewrittenpermissionofNetMotionWireless,Inc. NetMotionMobilityXEQuickStartGuide Version6.70 April2006 Portions2000,2001,2002,2003SunMicrosystems,Inc.Somepreexistingportions. Someportions2000,2001NetscapeCommunicationCorp.Allrightsreserved. ThisproductincludescodelicensedfromRSASecurity,Inc. SomeportionslicensedfromIBMareavailableathttp://oss.software.ibm.com/icu4j/ Portions1999,2002TheApacheSoftwareFoundation.AllRightsReserved. Portions1998,1999,2000ThaiOpenSourceSoftwareCenterLtd.andClarkCooper. Portions2001,2002Expatmaintainers. Portions19952002JeanloupGaillyandMarkAdler Portions1996,1999InternationalBusinessMachinesCorporationandothers.Allrightsreserved. Portions19951998EricYoung(eay@cryptosoft.com).Allrightsreserved. ThisproductincludescryptographicsoftwarewrittenbyEricYoung(eay@cryptsoft.com). Portions19902,RSADataSecurity,Inc.Allrightsreserved. TheportionsderivedfromtheRSADataSecurity,Inc.MD4MessageDigestAlgorithm. ThissoftwareisbasedinpartontheworkofIndependentJPEGgroup ThisproductincludescodelicensedundertheApacheLicense,Version2.0(ApacheLicense);youmaynot usesuchfilesexceptincompliancewiththeApacheLicense.YoumayobtainacoyoftheApacheLicenseat http://www.apache.org/licenses/LICENSE2.0. ThisproductincludesFSecureCryptographicLibraryCopyright20002004FSecureCorporation,http:// www.fsecure.com/.AllRightsReserved.ThisproductmaybecoveredbyoneormoreFSecurepatents, includingthefollowing:GB2353372,GB2366691,GB2366692,GB2366693,GB2367933,GB2368233.FSecure andthetrianglesymbolareregisteredtrademarksofFSecureCorporationandFSecureproductnamesand symbols/logosareeithertrademarksorregisteredtrademarksofFSecureCorporation.
Installation Roadmap
Thesearethebasicstepsforintegrating MobilityXEintoyournetwork environment: 1. BeforeyouinstallMobilityXE,confirm thatyouhaveconnectivityonyour wirelessnetwork,andthatamobile deviceconnectedtothenetworkcan successfullypingnetworkresources. IftheMobilityserverwilluseDHCP forclientIPaddressallocation,verify thatDHCPservicesareavailableonall subnetswhereMobilityclientsand serverswilloperate,andthatthereare enoughIPaddressesforclientvirtual andpointofpresenceaddresses. InstallaMobilitywarehouseand Mobilityserver(seepage3fordetails). InstalltheMobilityclientononeor moresupportedmobiledevices(see page5).
A PC with an x86-compatible Pentium III processor or better. Microsoft Windows 2000 Server (Service Pack 3 or later required, Service Pack 4 recommended), or Microsoft Windows Server 2003. Minimum 512 MB RAM. 2GB recommended for heavily loaded servers. About 60 MB of disk space for program files, plus additional temporary disk space needed during setup. Internet Explorer version 6.x or similarly capable browser with JavaScript enabled, for access to the Mobility console. See Chapter 3 of the NetMotion Mobility XE System Administrator Guide for more detailed server hardware guidelines.
The Mobility warehouse requires:
2.
Hardware as specified for the Sun ONE Directory Server (http://docs.sun.com/source/816-6697-10/hardware.html), with minimum 300 MB of disk space. Recommend 500 MB, of which directory server log files may require 400 MB.
The Mobility XE client for Windows 2000, Windows XP, or Windows XP Tablet requires:
3. 4.
A PC with about 3 MB of disk space, plus additional temporary disk space needed during setup.
The Mobility XE client for Windows CE requires:
A Windows CE device with a StrongARM 1100 or compatible processor (e.g., XScale). For a list of supported devices, see Technical Note 1515 at www.netmotionwireless.com. Microsoft Windows Mobile 2003 for Pocket PC, Microsoft Windows CE version 4.2 and above, or Microsoft Windows Mobile 5.0 for Pocket PC. Approximately 1 MB of storage memory.
To integrate Mobility XE into a wireless network environment, you must have at least one of the following:
A wireless LAN adapter installed on a mobile device and wireless access points installed on the wired network. A wireless WAN device installed on the mobile system and available wireless WAN service (for example, an account with a service provider). A mobile device with a network adapter that provides NDIS and IP support.
Windows CE
TherearetwowaystoinstalltheMobilityclientsoftwareonadevicerunning WindowsCE: InstallfromapartnerPC,usingActiveSync.Thisoptionrequiresthata partnershipbeestablishedbetweentheCEdeviceandadesktopmachine. Installfroma.cabfilewithoutusingActiveSync.
1.
2. 3.
Copythe.cabfiletoafolderontheWindowsCEdevice,ortoamemorycardyou caninsertintothedevice. OntheCEdevice,runthe.cabfiletoinstalltheMobilityclient.TheSetup programwillpromptyoutoenteranameorIPaddressforyourMobilityserver (thisisthedefault),ortochoosetoacquiretheserversIPaddressfromDHCP.If youselecttheDHCPoption,theDHCPservermustbeconfiguredtoprovidethis information.Youwillseeaconfirmationdialogboxwhensetupisfinished. ResettheCEdevicewhenpromptedtodoso.Ifyoursystemdoesnotsupport autoreset,resetthedevicemanuallytomakethenecessarychangestoyour Windowsconfiguration.
4.
Upgrading Mobility XE
ToupgradeanexistingMobilityXEinstallation,choosetheMobilityXEServeronly setupoptiondonotreinstalltheMobilitywarehouse.TheMobilityservermust haveaccesstotheprimarywarehousebothduringthesoftwareupgradeandafterthe upgradedserverisrestarted,tosuccessfullycompletetheupgradeprocess. Itisgoodpracticetoperformasystembackupbeforeinstallingnewsoftware.Ifyou reverttoNetMotionMobilityversion5.xorearlierafterupgradingtoMobilityXE, settingsconfiguredfortheearlierversionarenotrestored.ForupgradestoMobility XEversion6.5fromversion6.0or6.01,theNetMotionMobilityXESystemAdminis tratorGuidedescribesproceduresforbackinguptheMobilitywarehouse. Duringtheupgrade,theSetupprogramstopstheserviceandclientsthatwere connectedtotheservercontinuetotrytoconnect.Whentheupgradeiscompleteand yourestarttheMobilityserver,theclientswillconnectautomaticallyiftherearesuffi cientlicenses.
Note:ThesecurityandfeatureenhancementsinMobilityXEaffectthecompatibility ofthisversionwithearlierreleases.SeeUpgradingMobilityXEinChapter4ofthe NetMotionMobilitySystemAdministratorGuideformoreinformation.
OnWindows2000orWindowsXP,theMobilityclientlogonisintegratedintothe Windowsloginprocedure.YouwillonlyseeaMobilityLogondialogboxifMobility XErequiresdifferentcredentialsthanyourWindowslogin,oriftheusernameor passwordyouenteredareinvalid. WhentheMobilityserverisconfiguredtousetheSecurIDprotocolforRADIUSuser authentication,theuserentersWindowscredentialsintheLogOntoWindows dialogbox,andthenenterstheSecurIDusernameandpasscodeintheMobility Logondialogboxthatfollows. ForinformationaboutotherMobilityclientconnectionoptions,seetheonlinehelpor theNetMotionMobilityXESystemAdministratorGuide.
OntheMobilityclient,theMobilityXEiconinthesystemtrayreflectsthestatusof theconnectionbetweentheclientandtheMobilityserver.
When the icon is: The client is:
Green
Yellow
Establishing a Mobility server connection. The Mobility clients IP address or network adapter has changed. The client may be roaming to a new subnet, or returning from out of range. Unable to reach the server. Disconnected from the server.
11
Technical Support
TheNetMotionwebsite(www.netmotionwireless.com)hasTechnicalNotes, answerstofrequentlyaskedquestions,troubleshootingtips,andlinkstoother MobilityXEtechnicalinformation. Ifyouneedfurthertechnicalassistance,contactyourNetMotionMobilityXEreseller orsolutionprovider.Pleasebepreparedtoprovidethefollowinginformation: Exacterrormessageand/orsymptomsyouobserved VersionofMobilityserverandMobilityclientsoftware Operatingsystemversions,includingOSRorservicepacklevel Wirelessnetworkhardwarevendorandmodel MobilityXEeventlogsand/orSetuplog.txtfilesonclientandserver