+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 60
Windows 7 Thread, Win 7 - DHCP/Netlogon/Firewall - Microsoft Confirm a Bug in Technical; Are you experienceing the NETLOGON problem on a wired or wireless connection? We were able to stop it occurring on ...
  1. #31

    Join Date
    Mar 2011
    Posts
    29
    Thank Post
    0
    Thanked 3 Times in 3 Posts
    Rep Power
    8
    Are you experienceing the NETLOGON problem on a wired or wireless connection? We were able to stop it occurring on wired only. On wireless it still persists.

    I have found the global DHCPConnForceBroadcastFlag setting to be rather useless, seeing as you should set DhcpConnEnableBcastFlagToggle as well, which you can only do per interface GUID.

    It's a hard problem to manage. I've written a bit about it here, in my blog. I might have a followup soon with some similar issues we're seeing at boot on wireless PC's (however we still haven't fixed those problems completely).

    Quote Originally Posted by TimmG6376 View Post
    I have mitigated the Group Policy processing issues by tweaking the following GPO settings:

    • Computer Configuration/Administrative Templates/System/Group Policy/Startup policy processing wait time
    • Computer Configuration/Administrative Templates/System/Logon/Always wait for the network at computer startup and logon
    • Computer Configuration/Administrative Templates/System/Net Logon/Expected dial-up delay on logon


    None of the suggested workarounds for the NetLogon errors have worked. Disabling the firewall did nothing. The DHCPConnForceBroadcastFlag can be implemented but the global setting only applies if the entry under
    Code:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\<GUID>
    is deleted.

  2. #32

    Join Date
    May 2011
    Location
    Alexandria, VA
    Posts
    8
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by Speculator View Post
    Are you experienceing the NETLOGON problem on a wired or wireless connection? We were able to stop it occurring on wired only. On wireless it still persists.

    I have found the global DHCPConnForceBroadcastFlag setting to be rather useless, seeing as you should set DhcpConnEnableBcastFlagToggle as well, which you can only do per interface GUID.

    It's a hard problem to manage. I've written a bit about it here, in my blog. I might have a followup soon with some similar issues we're seeing at boot on wireless PC's (however we still haven't fixed those problems completely).
    Wired gigabit. Not too concerned about the wireless connections as everyone with a laptop docks when at their desks so wireless is only used occasionally or for guests. I've tried the DHCPConnForceBroadcastFlag and DhcpConnEnableBcastFlagToggle to no avail. If it is working for you though I will submit this Powershell script that will allow you to push these entries out to multiple machines. As with any script use at your own risk and test before using in production
    Code:
    # Replace with your subnet
    $IpSubnet = "10.1.1."
    
    # Use WMI query to get GUID for network adapter with IP address matching the IP subnet configured above
    $NIC = Get-WmiObject -query "select settingid, ipaddress from win32_networkadapterconfiguration WHERE IPEnabled = 'True'"  | ? { $_.IpAddress -match $IpSubnet }
    
    $GUID = $NIC.SettingID.ToString()
    
    #Use GUID to set registry path to interface key
    $RegPath = "HKLM:\System\CurrentControlSet\services\TCPIP\Parameters\Interfaces\" + $GUID 
    
    $RegKey = Get-Item $RegPath
    
    # Sets DhcpConnForceBroadcastFlag property value to 1
    Set-ItemProperty $RegKey.PSPath -name DhcpConnForceBroadcastFlag -Value 1
    
    # Checks for existence of DhcpConnEnableBcastFlagToggle property
    # If it does not exist create the property with value 0
    # If it does exist set the value to 0
    If ((Get-ItemProperty $RegKey.PSPath -Name DhcpConnEnableBcastFlagToggle -ErrorAction SilentlyContinue) -eq $null ) {
    	New-ItemProperty $RegKey.PSPath -Name DhcpConnEnableBcastFlagToggle -Value 0 -PropertyType DWORD
    } Else { Set-ItemProperty $RegKey.PSPath -Name DhcpConnEnableBcastFlagToggle -Value 0 }
    I created a GPO on a test OU and configured this script as a Shutdown script. It configures the registry as desired, however, I'm still getting the NetLogon errors with my test machine.

  3. #33

    Join Date
    May 2011
    Location
    Alexandria, VA
    Posts
    8
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Ok I had completely ignored Windows 7 SP1 because I had read in multiple threads that it had no effect on this issue. We have not deployed SP1 as of yet, but unrelated to this issue I decided that it was time to install it on my PC and see if any issues arise. Incredibly after rebooting the NetLogon errors stopped. Disabled my GPO that modifies the registry. Set the registry back to defaults (DhcpConnForceBroadcastFlag = 0; deleted DhcpConnEnableBcastFlagToggle ). Cleared my System log. After another reboot still no NetLogon errors. I do still have the firewall disabled so that is my next test.

    CORRECTION:

    Seems to be a combination of SP1, completely the disabling firewall (domain,private,public), and the forcing broadcast flag via the registry. With all three of those I no longer get NetLogon errors on a wired connection. Will have to check wireless tomorrow.
    Last edited by TimmG6376; 18th May 2011 at 10:17 PM.

  4. #34
    Oops_my_bad's Avatar
    Join Date
    Jan 2007
    Location
    Man chest hair
    Posts
    1,738
    Thank Post
    438
    Thanked 53 Times in 50 Posts
    Rep Power
    30
    Could I be affected by this as well? I am seeing the same errors and inconsistent GP application, but we are a single broadcast domain and DHCP server is 2008 :/ No DHCP helpers in use..

    WOrkstations are not SP1'd yet.. just gonna try one now and see how that goes

  5. #35
    Oops_my_bad's Avatar
    Join Date
    Jan 2007
    Location
    Man chest hair
    Posts
    1,738
    Thank Post
    438
    Thanked 53 Times in 50 Posts
    Rep Power
    30
    Seems like a pretty fundamental flaw... how about we just don't pay our annual MS subs? If enough of us do that it might make M$ sit up and take notice.

  6. #36

    Join Date
    May 2011
    Location
    Alexandria, VA
    Posts
    8
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by Oops_my_bad View Post
    Could I be affected by this as well? I am seeing the same errors and inconsistent GP application, but we are a single broadcast domain and DHCP server is 2008 :/ No DHCP helpers in use..

    WOrkstations are not SP1'd yet.. just gonna try one now and see how that goes
    There are a few NICs that can also exhibit this behaviour due to GP trying to process before link negotiation has completed. See the post from Brent Hu at the link below (about 11 posts down the page).

    Windows 7 Slow to Log on with Re-Directed Folders - Windows Server 2008

  7. Thanks to TimmG6376 from:

    Oops_my_bad (23rd May 2011)

  8. #37
    Oops_my_bad's Avatar
    Join Date
    Jan 2007
    Location
    Man chest hair
    Posts
    1,738
    Thank Post
    438
    Thanked 53 Times in 50 Posts
    Rep Power
    30
    Hmm interesting. It seems this is only happening to some of our wireless laptops - atheros WIFI cards seem fine, I am only seeing this error on intel WIFI laptops. Maybe my issue is unrelated to this topic.. sorry.

  9. #38

    Join Date
    Dec 2007
    Posts
    48
    Thank Post
    0
    Thanked 26 Times in 5 Posts
    Rep Power
    25
    Hi,

    Microsoft have now released a KB article with a work around, they are still looking into the possibility of releasing a hotfix. The KB is 2459530

    Hope this helps,

    Edd
    Last edited by teckedd; 27th May 2011 at 09:45 AM.

  10. Thanks to teckedd from:

    Oops_my_bad (28th May 2011)

  11. #39

    Join Date
    Dec 2007
    Posts
    48
    Thank Post
    0
    Thanked 26 Times in 5 Posts
    Rep Power
    25
    Hi,

    I have some possible good news regarding the hotfix; I have received a beta fix that I hope to test very shortly. Microsoft are hoping to release the public fix in August. Before anyone asks I cannot redistribute the fix as it’s a beta and Microsoft will hunt me down however, once tested I will let you know if there is light at the end of the tunnel!

    Edd

  12. #40

    Join Date
    Dec 2007
    Posts
    48
    Thank Post
    0
    Thanked 26 Times in 5 Posts
    Rep Power
    25
    Hi All,

    Well some good news! I tested the hotfix today and it looks like it resolves the problem so I now need to continue the waiting game and wait for the public release before I can roll it out! I will post the link to the hotfix when it’s released.

    Edd

  13. #41

    russdev's Avatar
    Join Date
    Jun 2005
    Location
    Leicestershire
    Posts
    6,954
    Thank Post
    722
    Thanked 553 Times in 368 Posts
    Blog Entries
    3
    Rep Power
    205
    I love this 12 month turn around on a fix . However at least light for people who are having the issue.

  14. #42

    Join Date
    Dec 2010
    Location
    Swindon, UK
    Posts
    39
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    so is there a fix for this yet?

  15. #43

    Join Date
    Aug 2011
    Location
    Rotterdam
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    .. in the meantime ..

    Hi all,

    It has been several months.. I experience the same problem.

    Has Microsoft created a hotfix yet?

    Greets Jasper

  16. #44

    Join Date
    Jan 2007
    Posts
    993
    Thank Post
    15
    Thanked 48 Times in 28 Posts
    Rep Power
    25
    Getting similar errors on our workstations but not using Windows Firewall...when a static IP is set everything works great. Just when using DHCP?

    Any ideas...

  17. #45

    Join Date
    Sep 2011
    Location
    Morgantown, WV
    Posts
    3
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Is my case similar to yours?

    I've been running into a case I think might be related to this issue. Win7 SP1 x64 machines joined to a domain, get their IPs through a Cisco helper. On system wake (seen it from sleep, not sure from full boot) have intermittent issues with "no log on servers" error. NIC shows it has a connection, but if I log in with a local account Windows tries to get an IP then gives up and actually tells me the network connection is unplugged. Reboot generally solves the problem.

    I went through the directions in the MSKB article and on my systems at least, the TCP-IP interface already had the force broadcast flag set to 1. I've tried different drivers and autonegotiation settings without luck. Trying now to disable the public-profile firewall in case that's the isuse.

    Any word on when Microsoft might make this hotfix available so I can test that? Trying to track down these issues in two computer labs is driving me crazy.



SHARE:
+ Post New Thread
Page 3 of 4 FirstFirst 1234 LastLast

Similar Threads

  1. Replies: 4
    Last Post: 9th July 2010, 05:35 PM
  2. Replies: 5
    Last Post: 6th February 2010, 12:51 PM
  3. Replies: 63
    Last Post: 2nd December 2009, 05:50 PM
  4. Just to confirm that Jeff Goldblum is NOT dead
    By mattx in forum General Chat
    Replies: 1
    Last Post: 26th June 2009, 03:44 PM
  5. First Windows 7 bug discovered
    By FN-GM in forum Windows 7
    Replies: 1
    Last Post: 9th May 2009, 06:28 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •