nAppliance Networks Blog

UAG & DirectAccess: Some of my applications don’t work on DirectAccess, what should I do?

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

nAppliance nUAG and DirectAccess, Better Together !!

nAppliance nUAG remote access appliance platform is a next generation, high-performance application access and security solution which unifies a Web application firewall, SSL VPN, endpoint security to enable secure application access, access control and content inspection for a wide variety of line-of-business applications. Together these technologies provide mobile and remote workers with easy and flexible secure application access from a broad range of devices and locations including both managed and unmanaged PCs, mobile devices and kiosks.

Why use Microsoft Unified Access Gateway (UAG) for DirectAccess?

Microsoft introduced DirectAccess technology in Windows server 2008R2 wherein we can connect directly to our corporate resources without the need of any VPN software. Particularly, DirectAccess configuration is pushed to the client machines through a set of group policies. Once these group policies have been applied on all Windows 7 domain joined machines, these machines can then connect remotely to the corporate network without dialing in to any VPN server.
Although, it sounds a great solution from the description it’s not easy to deploy though. The major requirement for DirectAccess is the IPv6 connectivity within the internal network.
Syndicate content