bhamacher

New Member
Joined
Jan 12, 2012
Messages
2
I am trying to setup my windows 7 client to recieve an IPv6 Address from my DHCPv6 server. I am running my DHCPv6 server on Centos 6.2 and my config file is quite simple. I can wireshark the interface on my computer and see that the server is responding with all the information I have configured on it however my client never sets the ip address. Here is what my client is sending in the Solicit message. Domain Search List (24)DNS Recursive name Server (23)Vendor-specific Information (17)Fully Qualified Domain Name (39) The Server is responding with (23) and (24). Would the client keep sending a Solicit if it does not recieve the (17) & (39)? Is there anyway that I can stop my client from requesting these options from the server? I have also tried configuring my client to do no Router Discovery and set the Managed and OtherStateful flags but I can't seem to get anything to work properly. Any help would be greatly appreciated. Thank You
 


Solution
It seems like you are encountering issues with setting up IPv6 address assignment on Windows 7 using a DHCPv6 server running on CentOS 6.2. The behavior you described indicates that your client is sending a Solicit message but not properly receiving and setting the IPv6 address from the server. Here are some insights and potential solutions to address your concerns: 1. Client Behavior: - Requesting Specific Options: The client may keep sending a Solicit message if it does not receive the expected Vendor-specific Information (option 17) and Fully Qualified Domain Name (option 39) it is requesting. - Server Response: The server responding with options 23 and 24 but not 17 and 39 might cause the client to continue...
It seems like you are encountering issues with setting up IPv6 address assignment on Windows 7 using a DHCPv6 server running on CentOS 6.2. The behavior you described indicates that your client is sending a Solicit message but not properly receiving and setting the IPv6 address from the server. Here are some insights and potential solutions to address your concerns: 1. Client Behavior: - Requesting Specific Options: The client may keep sending a Solicit message if it does not receive the expected Vendor-specific Information (option 17) and Fully Qualified Domain Name (option 39) it is requesting. - Server Response: The server responding with options 23 and 24 but not 17 and 39 might cause the client to continue requesting these missing options. 2. Configuration Options: - Client Configuration: - Disabling Specific Requests: To stop your client from requesting specific options from the server, you may need to adjust the configuration on the client side. - Router Discovery: Disabling Router Discovery and setting the Managed and OtherStateful flags can be a valid approach. Ensure that these settings are properly configured on the client. 3. Troubleshooting Steps: - Debugging: Consider logging messages on both the client and server sides to identify any potential errors or mismatches in the configuration. - Network Connectivity: Ensure that there are no network connectivity issues preventing proper communication between the client and the DHCPv6 server. 4. Additional Considerations: - Firewall Settings: Check firewall settings on both the client and server side to ensure that they are not blocking any necessary traffic. - Compatibility: Verify the compatibility of DHCPv6 options between the client and server to ensure they are interpreting the information correctly. 5. Further Assistance: - If the issue persists, you may need to delve deeper into the configuration and logs to pinpoint the exact reason for the failure. - Consulting IPv6 documentation specific to Windows 7 and CentOS can provide additional insights into troubleshooting IPv6 address assignment. By addressing these points and ensuring proper configuration alignment between your Windows 7 client and CentOS DHCPv6 server, you can troubleshoot and potentially resolve the issue of IPv6 address assignment.
 


Solution
Back
Top