Use the following procedure to troubleshoot IPv6 DHCP Relay on
the server side.
Procedure
- Enable the services
on the server side, and then create an IP pool.
The IP pool must contain the range of addresses that you want to
assign to the clients.
Configure the IP pool with the same network subnet as that of the
relay agent.
- When the configuration
is complete, initiate a DHCP request from a client.
- Check the log file
available on the server to verify the reason for packet drop.
- Capture the packets
on the server side using Ethereal.
- From the server side,
use ping to verify that the relay agent address is reachable.
Ensure that a route to the relay is configured.
- For more configuration
aspects, see the Microsoft webpage for troubleshooting and configuration
issues.
Note
You can receive some log messages that indicate the system cannot forward
packets. However, certain situations are not DHCP failures.
Example 1: if you receive the message 0x00108796
(relayMsgSend): cannot find route entry for destination
on the console, you must ping the server. If the server
is not reachable, the system cannot forward the packet. This is not a
DHCP issue.
Example 2: if you receive the message 0x00108705 this indicates a problem at the
transmission level. Check the server reachability and ensure that MAC
learning is correct before you pursue DHCP issues.
