User's Manual

-76-
Allow unauthenticated provision mode: During the PAC can be provisioned
(distributed one time) to the client automatically. It only supported "Allow
unauthenticated provision mode" and use "EAP-MSCHAP v2" authentication to
authenticate now. It causes to continue with the establishment of the inner tunnel
even though it is made with an unknown server.
Use protected authentication credential: Using PAC, the certificate can be
provided to the client manually via disk or a secured network distribution method.
Server Certification
Certificate issuer: Select the server that issues the certificate.
Allow intermediate certificates: It must be in the server certificate chain between
the server certificate and the server specified in the "certificate issuer must be" field.
Server name: Enter an authentication sever root.
4.3.3 Example to Reconnect 802.1x Authenticated Connection after 802.1x
Authenticated connection Is Failed in Profile
There are two situations where a user is able to reconnect an 802.1x authenticated
connection and authenticate successfully after an 802.1x authenticated connection
has failed on the profile page. They are as follows:
When keying in an identity, password or domain name error:
Authentication type chooses "PEAP", key identity into test. Tunnel Protocol is
"EAP-MSCHAP-v2, the tunnel identity and tunnel password are tested. Those
settings are the same as our intended AP's setting.