PSS ID Number: 119496
Article Last Modified on 9/30/2003
The information in this article applies to:
- Microsoft LAN Manager 2.2
- Microsoft LAN Manager 2.2b
- Microsoft LAN Manager 2.2c
This article was previously published under Q119496
SUMMARY
The LAN Manager NMTSR.EXE and NMDRV.OS2 drivers demand an authoritative
Domain Name Resolution (DNR) response for cnames, and this can cause Domain
Name Service (DNS) lookups to fail.
SYMPTOMS
Attempting to ping another host by name from an OS/2 or MS-DOS LAN Manager
machine using DNR may return the message:
DGN0217 - Remote name cannot be resolved
In some instances of this problem, Windows for Workgroups 3.1 workstations
received this error when they attempted to ping a remote node by using its
alias; Windows NT computers did not.
CAUSE
When LAN Manager's NMTSR.EXE and NMDRV.OS2 drivers call the DNR server,
they explicitly demand an authoritative response for a cname.
If a DNR request is sent from a system in another
domain and that request hasn't been performed previously, the local DNR
contacts the authoritative DNS server, and receives
an authoritative cname reply, showing the cname and the actual name (and IP
address) of the target system. This case succeeds.
However, if another request is sent for the same cname afterwards, the
local DNS server replies with the same answer from cache, this time marking
it as non-authoritative. This lookup fails, returning an error message
such as "unable to resolve host" or "unknown hostname."
RESOLUTION
A fix is available that modifies the NMTSR.EXE and NMDRV.OS2 drivers so
that they do not demand authoritative responses. Contact Microsoft Product
Support Services to obtain the fix or more information.
STATUS
Fixed.
Additional query words: wfw wfwg 2.20 2.2 2.2b 2.2c
Keywords: KB119496
Technology: kbAudDeveloper kbLanMan220 kbLanMan220b kbLanMan220c kbLanManSearch