Updated server and now dhcp not working

[Sonic007]

Did updates on an old win2008r2 server and this morning getting no dhcp.

All devices defaulting to 169 address as can be expected but everything looks fine on dhcp and dns.

 

Any ideas?

 

Thanks.

[SpaceInvader83]

Firewall issue? NLA (Network Location Awareness) changed?

[Sonic007]

Firewall disabled.

[snagrat]

Check the DHCP bindings?

[Sonic007]

Still nothing.

 

Ipconfig on client machine just times out when trying to get an ip via dhcp server.

Unable to contact dhcp setver

[HPlum78]

Have you checked as per @snagtat suggestion no info about what updates you have taken so have you checked that the nic(s) look right? Would concentrate on what has changed on the sever and forget about diagnosing this from a client perspective right now.

[3s-gtech]

DHCP server on static IP? All looking okay in the network card settings? No other device suddenly started broadcasting DHCP? DHCP event logs clear?

[msi_school]

Do you have an IP helper on your core switch, this always catches me out when i spin up a new DHCP server.

[Sonic007]

NIC looks fine. No changes and I can access network shares from a client so can communicate with server.

 

Bindings haven’t changed. All looks ok here and displays server address.

 

Server is on static ip.

Dhcp just not wanting to work even though dhcp services all day running ok.

[fordea]

Is the DHCP server still authorized in AD?

[smoothwall]

have you tried to remove the updates that went on ? also like someone mentioned are other devices giving out DHCP address.

[Sonic007]

Im up and running again but still trying to work out what fix I did actually sorted it out. It was very odd as I had checked all the things it really should be.

Going to try and make some sense over it and then get out of here and get myself a cold drink.

 

Thanks everyone for your help along the way. Much appreciated.

[AlanD]

Do you have WDS (Windows Deployment Service) running on this server? And if so - check it does not start automatically.

 

WDS potentially shared the same ports as DHCP and if it grabs them first DHCP will not work. DWS should always be manually started later.

[Sonic007]

UPDATE: Sollution

 

So I just had the same thing happen on my other Win2008 Server after updates and have now worked out the sollution that worked.

 

Firstly make sure you know your static IP details for your Servers NIC connection.

 

You then need to turn off your VM's in HyperV Manager and then remove your virtual network card/switch.

 

Then go back to your physical hosts NIC and re-enter the static IP details. (They seem to dissapear).

 

Then Restart dhcp server. (net stop dhcp and net start dhcp).

 

Finally after you've got your Internet back go and re-create your HyperV network connection and point it at your NIC.

 

All should be well again.