The TN3270 Server Does Not Check for a Best LU to IP Match

Last reviewed: July 18, 1996
Article ID: Q148966
The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.11 and 2.11.sp1

SYMPTOMS

The TN3270E server does not do any checking of which LU to IP matches are better than others.

WORKAROUND

One possible workaround is to reorder the pools in the configuration. Place the pool with the pool you want the user to use first last in the list.

MORE INFORMATION

The following example shows where the TN3270 Server Service may allocate an user's session to a pool that the administrator did not expect:

Pool Configuration

  • Pool_A is configured to allow any workstation access. To do this, assign the IP Address to 0.0.0.0 and the subnet mask to 255.255.255.255 in the Edit Configuration for <pool_name> dialog box.
  • Pool_B is configured to only allow users on subnet 130.1.x.x. To do this, assign the IP Address to 130.1.x.x and the subnet mask to 255.255.0.0 in the Edit Configuration for <pool_name> dialog box.

The Administrator's Preference

   The Administrator's preference is for users to get a session through
   Pool_B first, and then Pool_A second.

The Result

If a workstation from the 130.1.x.x subnet tries to make a connection to the TN3270E Server, the TN3270E Server will not check for the best LU to IP match causing the workstation to potentially get an LU from Pool_A.


KBCategory: kbnetwork
KBSubcategory: snageneral
Additional reference words: 2.11 prodsna sp1 service pack 1


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 18, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.