Share via


DHCP PC's are not getting an IP unless i release/renew

Question

Wednesday, December 7, 2016 9:10 AM

Several of the PC's in my network are showing limited connectivity and will not grab an IP address unless i release/renew. A restart does not resolve either. Here is a txt output from one of the PC's. The address are all correct.

Windows IP Configuration

   Host Name . . . . . . . . . . . . : f7k853j-PC
   Primary Dns Suffix  . . . . . . . : OurDomain.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : OurDomain.local

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-1A-A0-C4-4F-7A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b572:41b4:427d:3acf%11(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.58.207(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 192.168.0.210
   DHCP Server . . . . . . . . . . . : 192.168.0.10
   DHCPv6 IAID . . . . . . . . . . . : 234887840
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0E-4E-3D-8A-00-1A-A0-C4-4F-7A
   DNS Servers . . . . . . . . . . . : 192.168.0.10
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{D27324AF-5DA2-4595-B88D-C817210D57D1}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Conrad Ryan

All replies (10)

Wednesday, December 7, 2016 1:26 PM

This can happen if you re-configured your DHCP Scope (or Server) and cleaned the DHCP lease database. Then the DHCP Client will try to re-use its previous IP Address, but it can conflict with another lease. You check this issue by changing the DHCP Scope to another IP range in the same subnet.

I am not sure if this is your issue as well, but just to make sure check it.

Boudewijn Plomp | Conclusion FIT

Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer". This posting is provided "AS IS" with no warranties, and confers no rights.


Wednesday, December 7, 2016 1:47 PM

Do you need to release and renew every time your reboot?

Do you have any of the ip information hard coded like DNS?

Had DHCP been restarted or Server rebooted?

Are you using 1 or more dhcp servers with DHCP failover?


Thursday, December 8, 2016 3:19 AM

Yeah we've seen dozens of people wiht this, today. Every one of them got a Windows Update last night (you know, the new Windows 10 one's you cannot say no to?). All the guys who did not get an update yet are fine.


Thursday, December 8, 2016 6:20 AM

Hi Conrad,

As Darren mentioned, If client need to renew its address after it reboot, please catch packet to check if client has sent discover to request IP address.

Please ensure DHCP addresses pool is not expended.

When client lease expired, will it renew IP address for DHCP server?

Best Regards

John

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Thursday, December 8, 2016 9:30 AM

This can happen if you re-configured your DHCP Scope (or Server) and cleaned the DHCP lease database. Then the DHCP Client will try to re-use its previous IP Address, but it can conflict with another lease. You check this issue by changing the DHCP Scope to another IP range in the same subnet.

I am not sure if this is your issue as well, but just to make sure check it.

Boudewijn Plomp | Conclusion FIT

Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer". This posting is provided "AS IS" with no warranties, and confers no rights.

This has not been the case, the only dhcp change i have made recently was to drop the lease time to 24Hrs.

Conrad Ryan


Thursday, December 8, 2016 9:33 AM

Do you need to release and renew every time your reboot?

# For Several PC's yes a reboot has been required each morning

Do you have any of the ip information hard coded like DNS?

# DNS is harcoded yes

Had DHCP been restarted or Server rebooted?

# DNS has been restarted, server has not been rebooted

Are you using 1 or more dhcp servers with DHCP failover?

#1 DHCP Server

Conrad Ryan


Thursday, December 8, 2016 9:33 AM

any resolve?

Conrad Ryan


Thursday, December 8, 2016 9:36 AM

Hi Conrad,

As Darren mentioned, If client need to renew its address after it reboot, please catch packet to check if client has sent discover to request IP address.

Please ensure DHCP addresses pool is not expended.

When client lease expired, will it renew IP address for DHCP server?

Best Regards

John

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

The DHCP pool is not expended, the lease is 24 hrs and has been working successfully until now.

Conrad Ryan


Friday, December 9, 2016 9:18 AM

Hi Conrad,

Please catch DHCP packet to check if client has sent discover to request address.

Best Regards

John

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Friday, December 9, 2016 11:09 AM

Hi Conrad,

Please catch DHCP packet to check if client has sent discover to request address.

Best Regards

John

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

I am unaware of the method to do this

Conrad Ryan