nAppliance Networks Blog

Can I use the Mac OS to create a Remote Desktop connection published through the UAG?

Most of our customers who have UAG appliances deployed also have a few Mac machines in their organizations and the issue of whether remote desktop connections can be used is something which comes up frequently on sales or technical calls.

Hotfix available for the Remote Desktop Services’ ‘Maximum Connections Reached’ error in UAG


Your computer can't connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance

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.

Application Publishing in TMG

One of many good features in Microsoft TMG is the ability to publish internal web based and non-web based applications on the internet for corporate users to access remotely. Users can access applications such as Outlook Web Access, SharePoint, CRM, RDP, and Citrix as they are published through the Microsoft TMG server. There are two types of publishing in the TMG:

SharePoint publishing through TMG vs. UAG: Capabilities and Benefits

Many of our customers wonder if it is better to use TMG or UAG for Sharepoint publishing, or whether either should be used at all. The answer, while not complex, involves some consideration of the relative capabilities and benefits of both pieces of software. In this post we will try to outline the key differences which will answer these questions. This post will give you a high level overview of the basic differences between the two.

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.

Syndicate content