Details Tab
There are no user-configurable settings on this tab.
Review Session Status information (when the Mobility client is disconnected, the status is described as Session not connected):
• User authentication only—The client connects after user authentication succeeds. The client does not attempt device authentication.
• User required / Device optional—The client attempts device authentication, but proceeds to user authentication if device authentication fails.
• Multi-factor—The client connects after both device and user authentication succeed.
• Unattended—The client connects after device authentication succeeds, and user authentication follows. When the user logs off from the client device, the connection between the client and server remains. Indicates whether the data transmitted between the Mobility server and the Mobility client is compressed. Compression is specified on the Mobility server. Compression may be on, off, or set to automatically detect the speed of a connection, enabling compression when the connection is slow and disabling it when the connection is fast. If compression is set to Auto, this is displayed here as Auto-on or Auto-off, depending on connection speed.Review Active Interface information:
Other options in the NetMotion Mobility Client dialog box:
All network application requests are processed directly by the embedded Microsoft TCP/IP stack; Mobility data encryption, compression, session persistence, and subnet roaming capabilities are not available. You are not required to authenticate to the Mobility server before network communication is allowed. See Disconnecting Mobility for more information. When you click Connect, the Mobility client attempts to connect to the Mobility server specified in the Configuration dialog box. By default, the Mobility client connects to a Mobility server at startup. See Connecting with Mobility for more information.
©2013 NetMotion Wireless, Inc. | Mobility v10.10 |