FIX: IPv6 implementation is broken between the SNA client and the SNA Server in a Host Integration Server 2010 environment

Article translations Article translations
Article ID: 2739304 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
Expand all | Collapse all

On This Page

Symptoms

In a Microsoft Host Integration Server 2010 environment, you use IP version 6 (IPv6). However, the IPv6 implementation is broken between the SNA client and the SNA Server.

Resolution

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, install cumulative update package 6 for Host Integration Server 2010 on all servers in the Host Integration Server subdomain. Make sure that all servers are also configured to support IPv6.

Additionally, this cumulative update must be installed on all clients that use IPv6. After this update is installed on a client, you must add the following registry value, depending on whether the client is configured to run the Resource Location component as an application or as a service.
  • If you run the Resource Location component as an application, you must add the SNAIP6.DLL value to the following registry entry:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Services\SnaBase\Parameters\Transports

    The current transports should already be listed. These include transports such as SNALM.DLL and SNAIP.DLL. Add the SNAIP6.DLL value according to the order in which you want the client to use the transports.

  • If you run the Resource Location component as a service, you must add the SNAIP6.DLL value to the following registry entry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Snabase\Parameters\Transports

    Note This entry will be removed every time that you make modifications by using the Host Integration Server 2010 Configuration Utility, and the entry must then be reapplied.

Cumulative update information

The fix that resolves this issue is included in cumulative update package 6 for Host Integration Server 2010. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2752426 Cumulative update package 6 for Host Integration Server 2010

Status

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

Properties

Article ID: 2739304 - Last Review: November 28, 2012 - Revision: 1.0
Applies to
  • Microsoft Host Integration Server 2010
Keywords: 
kbqfe kbfix kbexpertiseinter kbbug kbsurveynew KB2739304

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com