Windows Update causing DHCP to fail?

[Dunney]

Is anybody aware of a Windows Update that is causing DHCP to fail?

There have been 2 cases in recent weeks and there is no obvious reason.

[Dos_Box]

What errors are you getting in the logs? Or is the service just crashing?
Also, what version of server are you using (I know it's in the 2000/2003 thread but we have to check)?

[edutech4schools]

I had this. I found that after the update the dhcp bindings had been removed. I re-ticked the bindings (in DHCP) and bingo all working.

[edutech4schools]

Did you fix the issue?

[Andie]

Quick query about your issue, as we have a batch of Windows 7 machines that have just started failing to connect to the Internet. They can see the server (2003) but can't get out beyond. Strange IP address on wireless network connection, starting with 169 that I've been told is a default Windows 7 address, used when the network fails to get an address using DHCP. We appear to have enough free IP leases. The affected machines were fine up until a week ago. XP clients don't have the same problem. Wouldn't be a server update issue here though....? Is this similar to your problem...?

[Dunney]

The issue has been fixed. After some investigating we found that for some reason the firewall decided to block 2 ports that were blocking DHCP, no idea why? Once we set up some exclusions for the firewall, ip address started to be leased out.

Any idea why this could happen?

[Dos_Box]

What make/model of firewall is it, and why is the internal network going via a firewall?

[Dunney]

Sorry my mistake, i meant Windows Firewall. Do you think this could have been by a windows update?