The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SYMPTOMSAfter you apply Windows NT Service Pack 4 to the Windows NT DNS server, clients that try to access a UNIX computer receive the following error message:
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or
the individual software update. For information on obtaining the
latest service pack, please go to:
-or- http://www.microsoft.com/support/supportnet/overview/overview.asp NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support. For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If You Are Eligible for No-Charge Technical Support STATUSMicrosoft has confirmed this to be a problem in Windows NT 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5. MORE INFORMATION
The UNIX computer can use Reverse Lookup against the Windows NT DNS server to identify and validate its clients. For additional information about Reverse Lookup, please see the following
article(s) in the Microsoft Knowledge Base: Q164213 Description of DNS Reverse Lookups Windows NT SP3 Dns.exe maintained mixed case host names. The list of names on the UNIX machine that is used to validate clients against was held using mixed case names also. Doing a Reverse Lookup, the names returned from the DNS server matched the names on the UNIX side and the clients were granted access. Windows NT SP4 Dns.exe, however, converts all names to lowercase. As lowercase names are returned upon Reverse Lookup requests, the names returned do not match the names on the UNIX side and, therefore, "access denied" is returned. To resolve this problem, a new Dns.exe now has a registry entry that makes uppercase and lowercase handling configurable. WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD). HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters CasePreservation (REG_DWORD) Setting this to 1 will turn on case preservation. This has been resolved because of compatibility reasons. Please note, however, that RFC 952 describes that there should be no code and functionality depending on uppercase or lowercase of a DNS response. Therefore, maintaining a mixed case host list is not according RFC. Additional query words: 4.00
Keywords : kbbug4.00 kbfix4.00 nt4sp5fix |
|
Last Reviewed: November 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |