Cannot Find API getnamebyaddr Referred to in TN3270 Event 203

Last reviewed: April 17, 1997
Article ID: Q138390

The information in this article applies to:

Microsoft SNA Server version 2.11

SYMPTOMS

You cannot find the getnamebyaddr application programming interface (API) after you configure TN3270 Server to resolve IP addresses to NetBIOS names and this process fails causing the following event in the system log:

   Event 203: TN3270 server

   Description:
   Windows Sockets API call getnamebyaddr(xxx.xxx.xxx.xxx) failed in
   function TCPSessionInitialize with return code WSANO_DATA.

   EXPLANATION
   An unexpected error was encountered on a Windows Sockets API call.

   ACTION
   Record message and contact technical support.

NOTE: xxx.xxx.xxx.xxx in the description above represents the IP address.

CAUSE

The API getnamebyaddr does not exist. Instead, Event 203 should refer to the API call gethostbyaddr.

WORKAROUND

To work around this problem, evaluate the problem as if the API call gethostbyaddr is referenced in Event 203.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 2.11. This problem was corrected in the latest Microsoft SNA Server 2.11 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

Additional query words: prodsna
Keywords : kbbug2.11 kbfix2.11.sp2 kbinterop kbnetwork ntnetserv ntprotocol
Version : 2.11
Platform : WINDOWS

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