SNA Client Loses One TCP/IP Address on a Multihomed Server

 Last reviewed: February 3, 1998
Article ID: Q177579
The information in this article applies to:
  • Microsoft SNA Server, versions 3.0 Service Pack 2 (SP2) and 4.0

SYMPTOMS

If a client connects to a multihomed server with an IP address that is not the first one, it loses the server's first IP address. For example, a server has two addresses, 128.207.141.82 and 157.54.165.222. If the client connects to that server using the second address, the first address is lost and the second address is duplicated. In effect, the client now has two identical addresses in its service table.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0 SP2 and 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. 

Keywords          : kbbug3.00.sp2 kbbug4.00
Version           : WINDOWS:3.0SP2,4.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: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.