The Internet Connection Sharing area does not appear in the properties of the active network connection after you install Active Directory to configure a computer that is running Windows Server 2003 with SP1 as a domain controller

After you install Active Directory to configure a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) as a domain controller, the Internet Connection Sharing area does not appear in the properties of the active network connection. You expect the Internet Connection Sharing area to appear on the Advanced tab of the Properties dialog box for the network connection.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Download information

The following files are available for download from the Microsoft Download Center:

Windows Server 2003, x86-based versions:

Download the 897616 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=25C9C9DF-BA0E-4B1C-B6CC-21CFEADBEDD0)

Windows Server 2003, x64-based versions:

Download the 897616 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=B68BE69E-99BE-43AA-BC79-27626830DEB2)

Windows Server 2003, Itanium-based versions:

Download the 897616 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=A97AA21A-B77D-4A8C-A525-7BB2E3C2321D)

Release Date: October 17, 2005

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

To work around this problem, configure Routing and Remote Access to use Network Address Translation (NAT). This configuration provides the same capabilities as Internet Connection Sharing. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.