Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You cannot connect to corporate IPv4 resources by using DirectAccess after Forefront Unified Access Gateway 2010 Service Pack 3 is installed

You cannot connect to corporate IPv4 resources by using DirectAccess after Forefront Unified Access Gateway 2010 Service Pack 3 is installed

Symptoms

You install Microsoft Forefront Unified Access Gateway (UAG) 2010 Service Pack 3. When you try to connect to corporate resources by using DirectAccess, the connection is unsuccessful if the internal resources on the corporate network only use IP version 4 (IPv4), and clients rely on the Forefront UAG DNS64 service functionality.

↑ Back to the top

Cause

This problem occurs because, after the installation of UAG Service Pack 3, the Forefront UAG DNS64 service startup type is set to Manual. In this case, the service does not start when the UAG server is restarted.

↑ Back to the top

Resolution

To resolve this problem, install Service Pack 4 for Microsoft Forefront Unified Access Gateway 2010.

↑ Back to the top

Workaround

To work around this problem on a Forefront UAG server that is acting as a Forefront UAG DirectAccess server, manually set the DNS64 service startup type to Automatic, and then start the service.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

See the terminology Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbfix, kbexpertiseinter, kbsurveynew, kbbug, kbnotautohotfix, kb

↑ Back to the top

Article Info
Article ID : 2909191
Revision : 1
Created on : 1/7/2017
Published on : 11/27/2013
Exists online : False
Views : 167