3270 LUs May Now Be Assigned to TCP/IP Addresses

Last reviewed: March 11, 1998
Article ID: Q165939

The information in this article applies to:

Microsoft SNA Server version 3.0

SYMPTOMS

In previous versions of SNA Server, 3270 LUs could not be assigned to IP addresses. This feature will be available in the next Service Pack for SNA Server version 3.0.

CAUSE

Microsoft SNA Server was not originally designed to support assigning IP addresses to 3270 LUs.

RESOLUTION

The option to assign LUs and LU Pools to the following address types will be supported in the next Service Pack for SNA Server version 3.0: IP, IPX, Vines IP, and AppleTalk. The workstation property page allows a choice from three types of Workstation IDs: a name, an address (IP, IPX, AppleTalk, Banyan Vines), or an IP subnet. If an IP subnet is entered, an IP subnet mask is also required.

IP Address

The IP address is specified in the familiar dotted decimal format. An example of the dotted decimal address is:

   157.57.122.19

IPX Address

The IPX address is the MAC address of the client's network adapter. An example of this address is:

000A00605CC7

Vines IP Address

The Vines IP address is specified in the format

   <network_number>.<subnetwork_number>

where both are in hexadecimal format. The network_number length is 4 bytes and the subnetwork_number length is 2 bytes. An example of this address is:

   0027E3CA.801E

AppleTalk Address

The AppleTalk address is specified in the format

   <network>.<node>

where both are in decimal format. The network length is 2 bytes (0 - 65535) and the node length is 1 byte (0 - 255). An example of this address is:

   5.37

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0. This problem was corrected in the latest Microsoft SNA Server 3.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Keywords          : kbbug3.00 kbfix3.00.sp1 prodsna snamanager kbnetwork
Version           : 3.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

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: March 11, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.