Request A Quote

Iron Networks Blog

why choose iron Software Define Data Center Hnv Hybrid Cloud Gateway MCE Cloud Edge Gateway Cloudboxx, branch-in-a-box Wss, windows storage systems

DirectAccess

DirectAccess Deep Dive Training at TechMentor 2014

It is with great pleasure that I announce that I’ll be delivering a comprehensive, three-hour deep-dive training session at the TechMentor 2014 conference this year. The conference will be held August 11-15, 2014 in Redmond, WA. During the session you’ll learn how to design, plan, implement, and support DirectAccess running on Windows Server 2012 R2. If you’re considering deploying DirectAccess this year, you won’t want to miss out on this event. If you register before June 4 you can save $300.00, so register today!

DirectAccess Network Deployment Scenarios

When DirectAccess was first introduced in Windows Server 2008 R2, and continuing with Forefront Unified Access Gateway (UAG) 2010 DirectAccess, there was a hard requirement for the DirectAccess server to be configured with two network interfaces; one internal, and one external. The external network interface also required two consecutive public IPv4 addresses and did not support placement behind a Network Address Translation (NAT) device.


DirectAccess Network Location Server Considerations

When deploying DirectAccess, a critical infrastructure component is the Network Location Server (NLS). The NLS is used by DirectAccess clients to determine if they are inside or outside of the corporate network. Based on NLS reachability, the DirectAccess client will decide if it should attempt to establish DirectAccess connectivity to the tunnel endpoints specified by the DirectAccess configuration. If the DirectAccess client can connect to the NLS, it assumes it is inside the corporate network and does not establish DirectAccess connectivity. If it cannot connect to the NLS, the DirectAccess client assumes it is outside of the corporate network and attempts to establish DirectAccess connectivity.

Common DirectAccess Implementation Mistakes

Here at Iron Networks we deploy Microsoft DirectAccess on a near daily basis for companies all over the world. We’ve gained a tremendous amount of experience doing this, and much of what we’ve learned over the years is baked in to our DirectAccess hardware appliance platform. Although you may be deploying DirectAccess for the first time, leveraging Iron Networks' solutions and services can ensure that you don’t make mistakes that others are prone to.

DirectAccess Webinar on October 3 2013

Are you interested in learning about Microsoft DirectAccess, the always-on, seamless and transparent remote access feature in Windows Server 2012? Then join me on Thursday, October 3, 2013 for a webinar where I’ll describe in detail what DirectAccess is, how it functions, what the benefits are for deploying DirectAccess in terms of security and ease of use, and much more. I’ll also provide you with information about how Iron Networks can assist you with deploying DirectAccess quickly and effectively by leveraging our advanced hardware appliance platform and professional services. You can register for the webinar here: http://www.ironnetworks.com/DAWebinar/.

Windows Server 2012 DirectAccess and Forefront UAG 2010 - Better Together

When DirectAccess was first introduced as a feature of Windows Server 2008 R2, many considered the concept of always-on, secure remote access a natural evolution of traditional Virtual Private Networking (VPN) technologies. VPN had gone from being something that only IT administrators needed to provide remote support for their systems to an essential productivity tool for the modern, mobile workforce. Unfortunately, DirectAccess in Windows Server 2008 R2 was a bit ahead of its time. The idea was an excellent one, but in practice it was difficult to implement and carried steep infrastructure requirements, the most challenging of those being the requirement to deploy IPv6 on the internal network.

Secure Remote Access to On-Premises Private Cloud Resources with Microsoft Windows DirectAccess

Here on the Iron Networks Cloud Infrastructure Blog we talk quite a bit about the Microsoft private cloud with Hyper-V and System Center. We’ve extolled the virtues of the Microsoft Private Cloud stack with Windows Server 2012 R2 Hyper-V and System Center 2012, the building blocks for deploying scalable, highly available systems to support agile and dynamic workloads. The vision of the modern datacenter is at the heart of some very exciting technology and solutions, such as the Iron Networks IronPOD.

Disabling Unused IPv6 Transition Technologies for DirectAccess

For providing secure remote access to on-premises data and applications, there’s no question that DirectAccess is the best solution. If you’ve deployed DirectAccess using Windows Server 2012 behind a Network Address Translation (NAT) device, it’s a good idea to disable any unused IPv6 transition protocols. For more information, click here.

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:

Syndicate content
 

Copyright © 2019 Iron Networks, Inc. All Rights Reserved.