An error occurred while renewing interface Ethernet : unable to contact your DHCP server. Request has timed out<\/strong>.<\/em><\/p>","upvoteCount":10,"datePublished":"2021-10-05T18:21:44.000Z","url":"https://community.spiceworks.com/t/having-issues-with-new-dhcp-server/813151/1","author":{"@type":"Person","name":"buffalowingz","url":"https://community.spiceworks.com/u/buffalowingz"}},{"@type":"Answer","text":"Did you restart the client machine just to see if that would pull a new lease?<\/p>","upvoteCount":0,"datePublished":"2021-10-05T18:59:46.000Z","url":"https://community.spiceworks.com/t/having-issues-with-new-dhcp-server/813151/2","author":{"@type":"Person","name":"johnrobertson5580","url":"https://community.spiceworks.com/u/johnrobertson5580"}},{"@type":"Answer","text":"
No I am remote working on all this and am afraid I might lose my client machine if it reboots and doesnt get an IP.
The new dhcp server should have a static address. It’s showing APIPA because it was getting its own address from DHCP.<\/p>","upvoteCount":0,"datePublished":"2021-10-05T19:49:50.000Z","url":"https://community.spiceworks.com/t/having-issues-with-new-dhcp-server/813151/4","author":{"@type":"Person","name":"kevinhughes2","url":"https://community.spiceworks.com/u/kevinhughes2"}},{"@type":"Answer","text":"
Both servers have Static IPs.<\/p>\n
Check that…<\/p>\n
Actually the old server the Statics are blank? Never seen this before. I place them in and 10 seconds later they are blank again…<\/p>\n
I can still ping the correct IP and the name resolves when I ping it as well.<\/p>","upvoteCount":0,"datePublished":"2021-10-05T20:03:24.000Z","url":"https://community.spiceworks.com/t/having-issues-with-new-dhcp-server/813151/5","author":{"@type":"Person","name":"buffalowingz","url":"https://community.spiceworks.com/u/buffalowingz"}},{"@type":"Answer","text":"
Well crap I just found out another guy ran a IP Reset. This is fun…<\/p>","upvoteCount":1,"datePublished":"2021-10-05T20:08:36.000Z","url":"https://community.spiceworks.com/t/having-issues-with-new-dhcp-server/813151/6","author":{"@type":"Person","name":"buffalowingz","url":"https://community.spiceworks.com/u/buffalowingz"}},{"@type":"Answer","text":"
Ok I am ret*****ed… Never did a reboot like October suggested…
I had the same error after I migrated our DHCP server from 2008 to 2019.<\/p>\n
A reboot cleared things up.<\/p>\n
It seems like I am not the only one that had the issue. I’ve read a dozen or so posts on Spiceworks with users having the same issue.<\/p>\n
All-
Moving to a new server and having a hard time getting the new server to hand out address… Multiple DHCP Server Service restarts, even reboots.
When building the new DHCP server I tried the standard Export\Import of DHCP server and received an error. Used the Powershell commands and it worked perfectly… or so I thought.
Confirmed first server was unauthorized and used a dummy machine to /renew and says DHCP server is unavailable.
Farted around with this for way too long and no progress… So back to original server and everything is correct… however when I look for all DHCP server now my original server, the one thats working is showing a 169 address. Ive confirmed bindings are correct. Secondary NIC full disabled.
As much as I dont care about this 169 address, Im having a B**** of time getting the new server to work and hand out addresses. The new server is showing all current leases and reservations like the old server but when I /renew on a client machine it gives me:Windows IP Configuration An error occurred while renewing interface Ethernet : unable to contact your DHCP server. Request has timed out .
10 Spice ups
Did you restart the client machine just to see if that would pull a new lease?
No I am remote working on all this and am afraid I might lose my client machine if it reboots and doesnt get an IP.
The new dhcp server should have a static address. It’s showing APIPA because it was getting its own address from DHCP.
Both servers have Static IPs.
Check that…
Actually the old server the Statics are blank? Never seen this before. I place them in and 10 seconds later they are blank again…
I can still ping the correct IP and the name resolves when I ping it as well.
Well crap I just found out another guy ran a IP Reset. This is fun…
1 Spice up
Ok I am ret*****ed… Never did a reboot like October suggested…
I had the same error after I migrated our DHCP server from 2008 to 2019.
A reboot cleared things up.
It seems like I am not the only one that had the issue. I’ve read a dozen or so posts on Spiceworks with users having the same issue.
![\"913d32f3-8b77-4032-8c54-c61067eed487-2021-10-05_13_07_01-DC1-Onsite-S_-_TeamViewer.png\"](\"https://us1.discourse-cdn.com/spiceworks/original/4X/e/6/6/e66552f649dc3f59f6a8925ed1bf485eda1f968f.png\")