Common Configuration Problems - Novell NETWARE 6-DOCUMENTATION Manual

Common Configuration Problems

124 Novell DNS/DHCP Management Utility Administration Guide
The IP address is already in use by another client.
2. Ping an IP address on your local network.
If this approach fails, one of the following conditions might be the cause:
The client you pinged is not operational.
The LAN is experiencing problems.
Your client's TCP/IP stack is experiencing problems.
3. Ping an address on a different network or on the internet.
If this approach fails but the preceding steps were successful, the problem
is probably related to your router or your client's default router. If you are
using DHCP, the default router configured for the DHCP server for each
client is probably incorrectly configured.
4. Verify name resolution within your network. Ping a domain name within
your company's network.
If this approach fails, the default DNS server configured for your TCP/IP
stack is invalid, or the DNS server is not functioning. If you are using
DHCP, the DNS server that is configured on the DHCP server is not
properly configured.
5. Verify name resolution through the internet. Ping a host on the internet,
such as novell.com.
If this approach fails, your company's DNS server (that forwards DNS
requests to the Internet) is not functioning, or the Internet DNS server to
which your DNS server forwards requests is not functioning.
If you experience problems with DNS, check the following configuration
problems.
1. Check the consistency of glue records that are shared between parent and
child zones. Make sure that Name Server (NS) and Address (A) records
within the parent zone match those in the child zone.
2. Keep the IP addresses of the root name servers configured in the
RootServerInfo zone updated. Changes to this information are not
automatically propagated through a domain; you must enter them
manually. The most recent update of root name server information is
available through FTP at ftp://rzs.internic.net/domain/named/root.