Export (0) Print
Expand All

Step 4: Verify DirectAccess with OTP

Updated: August 15, 2012

Applies To: Windows Server 2012, Windows Server 2012 R2

This topic describes how to verify that you have correctly configured your DirectAccess with OTP deployment.

  1. On the Remote Access server open the Remote Access Management console.

  2. Under Remote Access Servers click the Remote Access server that has been configured for OTP support.

  3. Click Operations Status.

  4. Verify that the status of OTP displays the green icon and is Working.

    The health status update interval will be a maximum of the sum of the values from the registry key HKLM\SYSTEM\CCS\Services\Ramgmtsvc\parameters\HealthRefreshTimeout and the Time interval for server activity that was set in the Remote Access configuration.

  1. Connect a DirectAccess client computer to the corporate network and run gpupdate /force from the command prompt to obtain the group policy.

  2. Disconnect the client computer from the corporate network, connect to the external network, and attempt to access internal resources. You should not have access to the internal resources.

  3. In the case of a software token, access the OTP client token using the vendor instructions, and note the current token code. When a hardware token is used, follow the vendor instructions for authentication.

  4. Click the Network connections icon in the notification area to access the DA Media Manager.

  5. Click the DirectAccess Connection, and click Continue.

  6. Enter the token code noted previously, and click OK. Wait for authentication to complete. The DirectAccess Workplace Connection status will now be Connected.

  7. Attempt to access internal resources. You should be able to access all corporate resources.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft