UP1

Problem:

When trying to activate the configuration on a UAG server, you might find that the activation failed and you can see the following error messages in the status window:

Error: Applying Network Access Protection configuration failed.

Microsoft UAG 2010 can be integrated with Windows NAP (Network Access Protection) to make sure that the computers comply with the IT policies before user’s login into the UAG portal. Windows Network Access Protection is part of Windows 2008 and 2008 R2 servers. No extra hardware or licensing is required to implement Microsoft NAP in an environment. Moreover, there are simple settings in UAG for integrating NAP to do policy enforcement.

Open the Microsoft Threat Management Console and right click on the Firewall Policy and select "Non-web Server Protocol Publishing Rule". A new server publishing rule wizard will appear. Give a name for the publishing rule and click next.

This is a very common situation which people might face when deploying Microsoft DirectAccess technology. Before going into how to work around this we need to know why the applications which work in internal network would fail to work on DirectAccess connectivity.

Let’s go through few types of applications and the reasons why they might fail to connect

Client/Server Applications