Microsoft KB Archive/224303

From BetaArchive Wiki
Knowledge Base


Host Integration Server allows range of IP ports with distributed link service

Article ID: 224303

Article Last Modified on 12/4/2007



APPLIES TO

  • Microsoft Host Integration Server 2000 Standard Edition
  • Microsoft Host Integration Server 2000 Service Pack 1
  • Microsoft Host Integration Server 2000 Standard Edition
  • Microsoft Host Integration Server 2004 Standard Edition



This article was previously published under Q224303

Important This article contains information about how to modify the registry. Make sure to 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:

256986 Description of the Microsoft Windows registry


SUMMARY

If a connection is configured to activate "On Demand" or "By Administrator," the node will issue an initial Open Link request. When the connection is activated, the SNA Server service (node) issues a Close Link request and then an Open Link request for the actual connection. If a distributed link service (DLS) is configured to use a fixed IP port number through the LocalIPport registry entry, the second Open Link request will fail because the port will be in a Time_Wait state from the first Open/Close Link request.

A registry entry is available to allow a range of IP ports. This registry entry is necessary to allow the connection to recover or be recycled in a timely fashion. The remote link service will cycle through the range of ports specified in LocalIPPortRange until it either finds a free port or has exhausted all ports in the specified range. To add this registry key, perform the following steps:

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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

  1. Start Registry Editor (Regedt32.exe).
  2. Locate the following key in the registry:'

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SnaRemx\Parameters\SnaTCP

  3. On the Edit menu, click Add Value, and then add the following registry value:

    Value Name: LocalIPPortRange
    Data Type: REG_DWORD
    Value: 1 (The default value is 1.)

  4. Quit Registry Editor.


MORE INFORMATION

The LocalIPPortRange registry setting is configured on the branch/remote server. This server is the server that runs the SnaRemX link service. The value that you enter indicates the range of ports.

For example, if the LocalIPPort registry setting is set to 5000 and the LocalIPPortRange registry setting is set to 5, the range of ports that will be used is 5000 through 5004. For example, if port 5000 is being used, 5001 will be used. The LocalIPPort registry setting is also configured on the branch/remote server to indicate the static port that must be used. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

164590 Branch servers using DLS cannot communicate through firewalls


REFERENCES

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

276446 Branch servers that use DLS use dynamic port for SnaBase connection


164590 Branch servers using DLS cannot communicate through firewalls


139508 Internet Firewall support in SNA Server


Keywords: kbinfo kbqfe kbfea kbsnaonly KB224303