Please see Cisco's release notes for more information. This issue is resolved in Cisco An圜onnect Secure Mobility Client version 2. Just as an authenticated wireless client must submit a set of credentials to be validated before being allowed to send wireless frames to the intranet, an IEEE 802.1X wired client must also perform authentication prior to being able to send traffic over its switch port. This issue is specific to the wireless NAM component of the Cisco An圜onnect Secure Mobility Client. The Wireless > Configure > Access Control page is used to configure per-SSID Access Control settings such as association security settings, splash page settings, and client addressing options.This article is designed to mirror the Access Control page and goes into detail about every option available from top to bottom. Note This issue is unrelated to the VPN features of the Cisco An圜onnect software. Older versions of the NAM component of the Cisco An圜onnect Secure Mobility Client will not work when you try to connect to a wireless network on a Surface Pro 3. If you use the Windows 8.1 Networks interface to connect to the wireless network, you can connect to the wireless network. However, you cannot use the Cisco NAM to connect to a wireless network that requires a password or other authentication. You can connect to an open (that is, unsecured) wireless network by using the Cisco Network Access Manager (NAM). If you try to connect to a wireless network by using the Cisco Network Access Manager (NAM), you cannot connect to the wireless network. The wired guest client receives an IP address from the egress VLAN but cannot pass any traffic until it completes the web authentication process. When you have the Cisco An圜onnect Secure Mobility Client installed on a Surface Pro 3, you may experience one of the following symptoms:
0 Comments
Leave a Reply. |