88 lines
6.4 KiB
HTML
88 lines
6.4 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Problem: Clients are not receiving an IP address or their configuration information" />
|
|
<meta name="abstract" content="Problems might occur if the clients cannot receive an IP address or the configuration information. An IP address is leased to a client through a four-step process between the client and the DHCP server." />
|
|
<meta name="description" content="Problems might occur if the clients cannot receive an IP address or the configuration information. An IP address is leased to a client through a four-step process between the client and the DHCP server." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgtroubleshooting.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptinteract.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgplanningdemands.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptrelayrouter.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgscenario3.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgmanaging.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzakgproblemnoip" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Problem: Clients are not receiving an IP address or their configuration
|
|
information</title>
|
|
</head>
|
|
<body id="rzakgproblemnoip"><a name="rzakgproblemnoip"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Problem: Clients are not receiving an IP address or their configuration
|
|
information</h1>
|
|
<div><p>Problems might occur if the clients cannot receive an IP address
|
|
or the configuration information. An IP address is leased to a client through
|
|
a four-step process between the client and the DHCP server.</p>
|
|
<p>All four steps must take place before the client receives an IP address.
|
|
Refer to DHCP client-server interaction for details about the four-step process.</p>
|
|
<p>Here are some common reasons for this problem.</p>
|
|
<dl><dt class="dlterm">The client is connected to a subnet that is not configured in the DHCP
|
|
server.</dt>
|
|
<dd> Check the DHCP configuration and verify that all subnets managed by the
|
|
DHCP server are listed in the configuration. If you are unsure about which
|
|
subnets should be managed by the DHCP server, refer to Network topology considerations.</dd>
|
|
</dl>
|
|
<dl><dt class="dlterm">The DHCP DISCOVER message from the client cannot reach the DHCP server.</dt>
|
|
<dd>If the DHCP server does not have an IP address on the client's subnet,
|
|
there must be a router or DHCP/BOOTP relay agent that can forward the client's
|
|
DHCP DISCOVER message to the DHCP server. For more information, refer to Relay
|
|
agents and routers. In addition to receiving the broadcast message, the server
|
|
needs to be able to send reply packets back to the client's subnet.</dd>
|
|
<dd class="ddexpand">If your iSeries™ server
|
|
is multihomed, you might need to add a Subnet Group to the DHCP
|
|
configuration. For more detail on configuring DHCP for a multihomed server,
|
|
see Example: DHCP and multihoming. This example describes what needs to be
|
|
done to the DHCP configuration so that the client's broadcast message is received
|
|
by the server.</dd>
|
|
</dl>
|
|
<dl><dt class="dlterm">The DHCP server does not have any available addresses for the client in
|
|
the address pool.</dt>
|
|
<dd>You can use the DHCP Server Monitor to see which addresses are currently
|
|
being used by the DHCP server. Managing leased IP addresses provides more
|
|
details about using the DHCP Server Monitor. If the DHCP server has run out
|
|
of available addresses, you might need to add more IP addresses to the address
|
|
pool, shorten the lease time, or delete permanent leases that are no longer
|
|
required.</dd>
|
|
</dl>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakgtroubleshooting.htm" title="You can view job log and trace data, as well as use troubleshooting lists for common problems.">Troubleshoot DHCP</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakgplanningdemands.htm" title="You can plan for most of the DHCP setup by looking at your network topology, the devices on the network (for example, routers), and how you want to support your clients in DHCP.">Network topology considerations</a></div>
|
|
<div><a href="rzakgconceptrelayrouter.htm" title="You might need to use a DHCP relay agent in your network; sometimes a router is sufficient. You can use both a DHCP relay agent and a router to efficiently and securely transfer data throughout the network.">Relay agents and routers</a></div>
|
|
<div><a href="rzakgmanaging.htm" title="The DHCP Server Monitor can help you to monitor and manage leases.">Manage leased IP addresses</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rzakgconceptinteract.htm" title="A client gets the DHCP information from the server, and specific messages are sent between the client and the server. DHCP obtains and returns leases.">DHCP client-server interaction</a></div>
|
|
<div><a href="rzakgscenario3.htm" title="You can learn how to set up the iSeries server as a DHCP server for a LAN that is connected to the Internet by an Internet router.">Example: DHCP and multihoming</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |