nAppliance Networks Blog

UAG DirectAccess

Adding OTP AUthentication to the UAG DirectAccess Deployment

DirectAccess is a seamless way to connect to company resources without dialing or logging into any other server. The default configuration of the DirectAccess uses Kerberos and certificates to create IPsec tunnels for a secure connection. So, how does it work? Well, the user connects their Windows 7 machine to the internet and machine creates the first IPsec tunnel, called the “Infrastructure Tunnel,” with the DirectAccess server.

We aren’t IPv6-ready yet, what do we need to deploy DirectAccess?

Every IT manager, when deciding on a strategy for deploying DirectAccess for their corporate users, has the following questions on their mind about IPv6:

When you have no excuse to not deploy Microsoft DirectAccess

As we have described in a previous blog post, Microsoft DirectAccess has many benefits over traditional VPN: http://www.nappliance.com/blog/nappliance-nuag-and-directaccess-better-together.

What role does DNS64 and NAT64 play in UAG Direct Access?

By now, most of us know what DirectAccess is. For those who don’t, Direct Access is a revolutionary VPN technology which was introduced in Windows Server 2008 R2. It provides seamless connectivity to corporate resources without requiring any dial-up or VPN. DirectAccess connectivity is based on IPsec, IPV6, and transition technologies like Teredo, 6to4, IP-HTTPS, and ISATAP. In DirectAccess, the IPv6 traffic is encapsulated in an IPv4 packet and is then sent across the internet, after which the DirectAccess server reads the IPv6 headers and executes it.

Best practices when deploying TMG URL Filtering

Microsoft Threat Management Gateway 2010 brings a lot of new and enhanced features to edge network security. Ever since Microsoft started with Proxy Server 2.0, and then ISA Server, URL filtering has always been something which administrators have wanted. Every company has their own IT policies and most companies want to restrict their users from visiting inappropriate or unsafe websites during their office hours from company-owned machines.

Why is UAG DirectAccess better than traditional VPN?

In our previous post at http://www.nappliance.com/blog/nappliance-nuag-and-directaccess-better-together we highlighted how UAG and DirectAccess are better together and the benefits of connecting through the DirectAccess. In this post we will concentrate on the advantages DirectAccess has over the traditional VPN connectivity and why companies would want to move away from the VPN infrastructure.

UAG 2010 RTM: Configuring UAG DirectAccess

Here's a colleaction of videos I created sometime back. It still applies to the UAG without SP1 (still in RC).

Part I

Part II

Part III

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