DHCP-Enabled MS-DOS Clients Do Not Resolve Host Names

 Last reviewed: September 9, 1996
Article ID: Q130538
The information in this article applies to:
  • Microsoft LAN Manager for MS-DOS, version 2.2c
  • Microsoft Network Client for MS-DOS, version 3.0

SYMPTOMS

When you ping a host name from a Dynamic Host Configuration Protocol (DHCP) enabled LAN Manager for MS-DOS version 2.2c or Network Client for MS-DOS version 3.0 client computer, the following error message may appear: 

   DGN0217: Remote name cannot be resolved
NOTE: IPCONFIG returns the current configuration including the WINS server. If you ping a valid IP address, or use the NET VIEW or NET USE command, the operation is successful.

CAUSE

This problem occurs if the entry for the host name does not exist in the HOSTS file. LAN Manager for MS-DOS version 2.2c client and Network Client for MS-DOS version 3.0 can be WINS-enabled. When you ping a host name from a DHCP-enabled client, the order of name resolution should be as follows: 

   1. Local host name
   2. HOSTS file
   3. DNS
   4. Local NetBIOS cache
   5. WINS server
   6. Broadcast
However, NMTSR.EXE, which handles ping requests, is only using the HOSTS file. It does not check the local host name. A protocol trace may reveal that nothing was sent out on the network.

WORKAROUND

To work around this problem, enter the host names, including the local host name, in the HOSTS file.

STATUS

Microsoft has confirmed this to be a problem in LAN Manager for MS-DOS version 2.2c and Network Client version 3.0 for MS-DOS.

KBCategory: kbnetwork kbbug2.20c kbbug3.00
KBSubcategory: nttcp ntconfig
Additional reference words: prodlm 2.20 3.00



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