Dhcp; Troubleshooting Checkpoints - Novell NETWARE 6-DOCUMENTATION Manual

DHCP

Troubleshooting Checkpoints

DHCP Locator object to obtain a copy of any global configuration from the
object. The DHCP server saves a copy of the global configuration in
SYS:\ETC\DHCP\DHCPLOC.TAB.
In subsequent loads, the DHCP server will try to obtain the global
configuration information from the DNS/DHCP Locator object. If the
information is not available, the DHCP server will read the information from
the last saved copy of SYS:\ETC\DHCP\DHCPLOC.TAB. Each time the
DHCP server loads and the DNS/DHCP Locator object is available, the
DHCP server updates the DHCPLOC.TAB file.
The DNS server also does not require access to the DNS/DHCP Locator
object. It has been enhanced to require access to the DNS/DHCP Locator
object only if the NAMED command line arguments are specified to create
zones in eDirectory. The DNS server no longer requires access to the
RootSrvrInfo zone stored in eDirectory. The DNS server now first tries to find
the RootSrvrInfo zone in eDirectory, but if it is not available, the DNS server
uses the copy of the information found in SYS:\ETC\DNS\ROOTSRVR.DAT.
This section provides the following troubleshooting information for DHCP:
"Troubleshooting Checkpoints" on page 135
"Common Operational Problems" on page 136
"Releasing and Renewing DHCP Addresses" on page 139
1. Verify that IP hosts with DHCP-assigned parameters operate the same as
when you manually configured them.
If an IP host does not operate the same as when it was manually
configured, verify that the parameters assigned by DHCP are the same as
those when the host was manually configured.
If a node is intermittently inoperable, verify that the node is not using the
same IP address as another IP host. If a duplicate IP address exists, verify
that there is only one DHCP server for the subnet. Also verify that the IP
addresses assigned by the DHCP server are not being used by manual
nodes.
2. Verify that all DHCP hosts can obtain a DHCP lease when required.
Troubleshooting 135