Win 7 - DHCP/Netlogon/Firewall - Microsoft Confirm a Bug

[freeman2000]

Is the hotfix already public?

[freeman2000]

The RegKey "DhcpConnForceBroadcastFlag" works for me.

But i need a hotfix :-(

[saerom]

Also having problems with running GPO's on startup caused by this bug.

We disabled the firewall for the public profile as workaround in PC rooms and fixed desktop computers, but for laptops we don't like to do this.

A hotfix would be great to have!

[freeman2000]

Try this Hotfix:

http://hotfix.chris123nt.com/Windows.7/Hotfixes/x86/Windows6.1-KB2459530-v3-x86.msu

 

It will fix the problem!

[stuartp44]

Try this Hotfix:

http://hotfix.chris123nt.com/Windows.7/Hotfixes/x86/Windows6.1-KB2459530-v3-x86.msu

 

It will fix the problem!

 

I have run this with no sucess, is there any update on this matter or has it gone sour like most of microsofts mishaps?

[teckedd]

Hi,

 

Microsoft have now finically release the hotfix The KB number is 2459530 hope this helps everyone, its been a long time coming.

 

Edd

[BooBoo]

Hi,

 

Microsoft have now finically release the hotfix The KB number is 2459530 hope this helps everyone, its been a long time coming.

 

Edd

 

And it WORKS!!

 

Thanks to Teckedd and all those who have badgered Microsoft for this hot patch. Today was the first time a whole set of laptops connected since upgrading to Windows 7. All on in under 1minute. Result.

[Michael]

Roll on Windows 7 SP2. I think it's going to address a lot of issues when it's released next year!

[mradel]

First of all thanks for that bunch of information on that nasty 5719 Errors!

We're also seeing these errors (along with some others related to Group-Policy (Computer-part) and time-service) in the eventlog of every Windows 7 computer we have in our environment.

These computers are connected to the LAN (they're lenovo notebooks with embedded Intel NICs) and everything works quite normal from the user's perspective, but the errormessages do not stop to show up on every reboot of the machine.

 

I was very glad when I saw that there is a hotfix available and quite curious if it would help in our environment, but unfortunately it doesn't fix our issues.

 

What I tried up to now beside of the hotfix installation:

- Used a PC without virus scanning software and without local firewall (we're not using windows firewall but Mcafee HIPS)

- Set the parameter "wait for link" to enabled on the NIC advanced settings (no changement)

- checked switch port settings (Cisco environment, spanning tree "portfast" option is enabled)

- played around with dependencies of the netlogon service

 

What else could I do now to stop this annoying messages?

Edited December 20, 2011 by mradel

[sonofsanta]

At first I read this thread and I was like

Then I checked my event viewer and I was like

Then I spent ages working out how to deploy an MSU with SCCM, finally managed it and I was like

 

(and then the machine I was testing on never seemed to have the issue resolved and I was all but then I checked it on a couple of others and they were fine, so I think this testbed is messing with me. It even broke a Scratch deployment yesterday. You have to work hard to mess that install up)

 

Cheers, anyway! (and apologies for the necroing, but maybe the reappearance of this thread will get a couple of other folks to check and spot the problem in their new Win7 install)

[jonspurs]

Sorry to bring up an old thread but that hotfix has 2 files - which one do I download? The 2011 or 2013 one?

[psydii]

I would suggest that if you have the updates from 2775511 installed (and you really should, as that is basically SP2), then you should install the 2013 version.

 

I not that recent updates delivered via WU / WSUS actually include even later versions of some of the system files than those included in 245930.

 

However in the last month we have started seeing issues relating to DHCP, and the only thing we can see that has changed are the tcp/IP stack.

 

Additionally you may want to try https://support.microsoft.com/en-us/kb/3063060 (in addition to, rather than instead of).

[smounche]

Thank you !

[jonspurs]

I would suggest that if you have the updates from 2775511 installed (and you really should, as that is basically SP2), then you should install the 2013 version.

 

I not that recent updates delivered via WU / WSUS actually include even later versions of some of the system files than those included in 245930.

 

However in the last month we have started seeing issues relating to DHCP, and the only thing we can see that has changed are the tcp/IP stack.

 

Additionally you may want to try https://support.microsoft.com/en-us/kb/3063060 (in addition to, rather than instead of).

 

Cheers for your help.

Yes we've got 2775511 deployed. If WSUS has later versions of system files than 245930 then I'll leave it for now.

I've followed https://support.microsoft.com/en-us/kb/2421599 which does ensure GP processes, but NETLOGON errors sometimes still happen.

Will monitor it...