If you are running Windows 98 Second Edition, your system may have a problem dynamically updating Domain Name System (DNS) clients. This problem is described in the Microsoft Knowledge Base Article, "Windows 98 Clients Not Registered with Dynamic DNS [Q242000]."
Computers running Windows 98 Second Edition, and participating in a Windows 2000 domain, may not have their host names registered with the DNS server.
When requesting an Internet Protocol (IP) address from the Dynamic Host Configuration Protocol (DHCP) server, Windows 98 clients send the Fully Qualified Domain Name (FQDN) option (code 81), which indicates that the client registers itself with the dynamic DNS server. Windows 98 Second Edition clients, however, do not actually register their host names with the dynamic DNS server. Instead, they depend on the DHCP server to register their host name information with the dynamic DNS server.
The information in this article applies to:
Cisco Network Registrar (CNR) 5.0 and later versions have the command policy allow-client-a-record-update enabled by default, which allows the client to update the DNS A record. If the client sets the flags in the FQDN option to indicate an A record upate in the request, and if this feature is enabled, the server allows the client to perform the A record update. Windows 98 SE, with this bug, does not perform the update. Thus, the DNS does not get a fully updated record for that client. The result is that you may not be able to do either a forward or reverse lookup on that client.
As a workaround you can disable allow-client-a-record-update, forcing the DNS updates to come from the CNR DHCP server. You should also set up the DHCP server to update the DNS server, and set the DNS updates to come from the DHCP server.
To disable allow-client-a-record-update, type the following command line:
nrcmd> policy policy_name disable allow-client-a-record-update
Specify the name of the policy that applies to the particular client. You may have a client-policy, a client-class-policy, a scope-policy, a named policy referred to by the client-entry, client-class, or scope, and finally the system-default policy. Which of those seven possibilities apply is entirely dependent on your situation. The configuration in a more-specific policy always takes precedence over a less-specific policy.To obtain the fix, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services Telephone numbers and information on support costs, go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
The English version of this fix should have the following file attributes or
later:
| Date | Time | Version | Size | Filename | Platform |
| 9/8/99 | 4:00pm | 4.10.2223 | 65,279 | Vdhcp.386 | Windows 98 Second Edition |
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.
| Updated: Apr 08, 2004 | Document ID: 19054 |