Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, July 16, 2018 6:19 PM
Hey!
I have a really wierd problem and i have not been able to find a solution for it and i hope that someone can help. I have a few windows 10 clients that doesent accept DHCP-offers coming from DHCP-servers. I have tried with wired and wireless but same issue. It works perfectly fine with Apple/Android. They get the offers but ignores them and uses APIPA addresses instead.
Static configuration works just fine.
With wireshark i can see DHCP-discover going out and DHCP-offers coming in to the clients but no DHCP-request is sent from client. I configured a DHCP-server on my MAC so now i have 2 DHCP-servers in the same broadcast domain and i can see 2 DHCP-offers coming in.
When i do ipconfig /renew i get the following
An error occurred while renewing interface Ethernet : invalid data
If i connect the client to a hotspot on my phone it works fine, can't see any differences comparing the DHCP-offers apart from subnet information.
Sadly i couldnt add any pictures to this post
If i activate DHCP-logging in eventviewer i can see*** rows with exclamation marks!***
Looking at the rows with exclamation marks i can read the following(translated from swedish).
Something failed during extraction of options with errorcode 0xD
***OPCode: ***FelVidExtraheraAlternativ
and that
Offer is ignored, same errorcode 0xD
***OPCode: ***ErbjudandeIgnorerat
And in one of the information events(i) i see the following
Timeout for ProcessDhcpRequestForever.
**OPCode: Timeout för ProcessDHCPRequestForever
The rest of the information events just tells me that the DHCP ports are excempted from the firewall and that broadcastbit is true or false depending on what i have configured via registry. And that the DHCP ports are closed again in the firewall.
I have tried the following
- resetting ip and winsock with netsh
- disable firewall/antivirus
- booting in safe mode
- tried with wired and wireless
- tried 2 different DHCP-servers in the same broadcast domaion
- Changed DhcpConnForceBroadcastFlag to 1 to get DHCP-offers via broadcast instead of unicast
- Changed DhcpConnEnableBcastFlagToggle to prevent Windows from changning DhcpConnForceBroadcastFlag back to 0
Had an image from wireshark when i have the BroadcastFlag set to 1.
1 DHCP-discover is sent via broadcast and 2 offers is received also via broadcast but none is used or ignored.
Can anyone help me with this or have any suggestion on how to fix it.
All replies (3)
Tuesday, July 17, 2018 7:29 AM
Hi,
From the error *** 0xD,*** we can see that it may be related to KDC cannot accommodate requested option. Make sure that SPN to which the client is attempting to delegate credentials is not in its Allowed-to-delegate-to list. Please refer to
In addition, try to restart the DHCP service. It is suggested that you can eenable only one DHCP server in domain and try again.
If nothing helps, you can use Network Monitor to capture the network trace, save it as an .etl file and upload it to a network drive. Make sure that there is only one DHCP server exists. You can also upload the kerbose log.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, July 18, 2018 2:16 AM
Hi,
Here are some updates for this issue.
After installing these updates, some devices running network monitoring workloads may receive the 0xD1 Stop error because of a race condition. Please install the hotfix, then re-run the network monitor to capture the network trace again.
In addition, I wander if the problem happens after you install the update? Have you recently install windows updates?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, July 20, 2018 11:41 AM
Hey!
We dont have any Active Directory domain or kerberos. So i'm not sure the first alternative is something to look at.
When it comes to DHCP-servers, the only reason i implemented the second one is because i wanted to try with another DHCP-server to limit the scope of troubleshooting. Since i get this issue with two completly different DHCP-servers i dont think this is a DHCP-server issue and can drop that for now.
I will try to install the update in your second response to see if it solves the issue.
Thank you for trying to help.